-
Notifications
You must be signed in to change notification settings - Fork 1
Stroyline user test
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.
- 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.
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?
Test among studio students and random passersby at school.
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.
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.
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."
The scoring system is divided 5 levels. 1 is the lowest and 5 is the highest.
- Uniform Pixel Grid Resolution
- Storyline
- Instruction
- NPC info
- NPC Communication Script
- Inventory-System-and-Consumables
- Storyline User Test
- Traitor Clues
- Game Characters
- Player Profile User Test
- Player Eviction Menu Sprint1: User survey (Team 7)
- Player Eviction Menu Sprint2: User survey (Team 7)
- Sprint3 - Win/lose Condition: User survey (Team 7)
- Sprint4 - Polishing-tasks: User survey (Team 7)
- Transition Animation/Special Effects/Sound Effects: Feature Overviews
- Transition Animation and Effects: Design Process & Guideline
- Sprint 4 User Testing
- Transition Animation & Effect: Code Guideline-Sprint4
- Sound effect when players complete npc tasks and hover over npc cards
- Fixing the clue bug
- Music Test
- Player Eviction Menu: Design Process & Guideline
- Player Eviction Menu (Feature Overviews)
- Player Eviction Menu: Code Guideline - Sprint1
- Sprint 1 User Testing
- Detailed Eviction Card: Design Process & Guideline
- Detailed Eviction Card: Feature Overviews
- Sprint 2 User Testing
- Player Eviction Menu: Code Guideline - Sprint2
- Sprint 2 Inventory System and Consumables Items User Testing
- Sprint 2 Inventory System and Consumables Items Functionality
- NPC interaction testing plan sprint3
- NPC interaction testing results sprint3
- NPC Dialogue Scripts
- Code Guideline
- Win/lose Condition: Design Process & Guideline
- Win/lose Condition: Feature Overviews
- Sprint 3 User Testing
- Win/lose condition: Code Guideline - Sprint3
- Enemy List
- User Testing 1: Enemy Image Filter
- User Testing 2: Enemy Animation and AI
- User Testing 3: Basic Attack