Skip to content

Stroyline user test

Guanhao Qiao edited this page Sep 14, 2022 · 6 revisions

Background and Goals

The game storyline is mainly about a survivor who aimed to survive long enough to uncover the mystery of who sunk Atlantis.In this sprint,we finished the chapers 5&6,helped to decide the basic information of npcs and traitor clues according to our detailed storyline.Also we made some changes to the gameplay of storyline.This test will test the coherence of the whole storyline and the detailed characters and the user’s satisfaction with the storyline and the gameplay mode.

Aim

  • We have added new chapters to the game, and I want to confirm that the whole storyline is coherent and complete.
  • We have made new changes to the gameplay mode, and I want to make sure that the new gameplay mode fits the game and plot development is also great.

Test plan

Our team discussed this test and determined the test target. Afterwards, the team conducted internal tests to ensure that there were no fundamental problems. Question:

The general feeling about storyline.

The rationality of tasks interspersed in the plot.

The continuity of storyline.

Do you want the story to be longer or shorter?

Any suggestions?

Participation

Test among studio students and random passersby at school.

Testing

The target audience for this testing is students in this studio as well as some potential players. Since this game was set up at a background of saving Atlantis,the storyline should be tested on its competence of convincing users and justifying itself. Thus, some interviews are conducted to get enough feedback for us to make some improvements.

Methodology

The user test aims to collect effective feedbacks and suggestions to make a blance between user experience and plot development. So we design several methods to achieve it.

  • Hypothesis: to confirm there is a sufficient number of potential players, since it's important to meet their expectations.

  • Design: to evaluate the continuity of the plot and the players' experience when reading the plot. Then make some improvement according to the feedbacks received.

  • Evaluation: based on the feedbacks received in the Design part to change some details in the storyline and make the plot more readable.

Interviews

The feedbacks related to the aim:

  • "The design of storyline is good for some plot fluctuations."

  • "The datails are well handled."

  • "It should have a little more suspenseful."

  • "Good ending and does not give players too much feeling of depression."

  • "I think the plot development can be better because some characters didn't have complete introductions."

  • "Maybe the description of princess' family is nott specific enough."

Evaluation Analysis

The scoring system is divided 5 levels. 1 is the lowest and 5 is the highest.

截屏2022-09-14 11 56 52

Table of Contents

Home

Game Design

User survey

Sprint 4

Eviction Menu and Win/lose Logic: Polishing tasks (Team 7)

Button Sounds and Ending Menu improve (Team 3)

Sound effect and Fixing the clue bug (Team 6)

Improvement of Enemy and Attack (Team 1)

Add Features When The Player Get Attacked and Overall UI Improvement (Team 8)

Sprint 1

Achievement System (Team 2)

Player Eviction Menu (Team 7)

Countdown Clock (Team 4)

Music (Team3)

Map (Team6)

Sprint 2

Player Eviction Menu (Team 7)

Character Design & Animation (Team 1)

Music (Team 3)

Inventory System and Consumables Items (Team 8)

Scenario design

Achievement System(team 2)

Storyline (Team 5)

Countdown Clock (Team 4)

Sprint 3

Ending Menu (Team 3)

NPC interaction (Team 2)

Win/lose Condition (Based on Eviction Menu) (Team 7)

Player Profile (Team 4)

Game Logo (Team 8)

Clue storage (Team 6)

Enemy Design and Attack (Team 1)

Scenario design for village(Team5)

Game design
Entities and Components

Service Locator

Loading Resources

Logging

Unit Testing

Debug Terminal

Input Handling

UI

Animations

Audio

AI

Physics

Game Screens and Areas

Terrain

Concurrency & Threading

Settings

Troubleshooting

MacOS Setup Guide

Clone this wiki locally