-
Notifications
You must be signed in to change notification settings - Fork 1
The dialog box is called again testing sprint4
The main purpose of this user test is to investigate and evaluate the views and feelings of the dialogs we changed on the users, and record the feelings, moods, and interactions of the users through the actual operation. This user test was very important for our project because our team's final design might have some flaws. Therefore, the test results are executed to improve the system.
Due to the current COVID-19 pandemic, user testing will be conducted through online zoom meetings. The tester will use the zoom meeting to show the user the relevant display page of the game, and let the user remotely control to try it out.
1、The tester will use zoom to display relevant game conversations.
2、The tester will ask the user some open questions.
3、The tester will record the answers, summarize them, and delve into specific reasons.
- What do you think is the first feeling of the dialog box disappearing?
- Do you think getting back to the npc is the right way for you
- Do you want to break the conversation in the middle of communicating with NPCS?
Based on our qualitative tests with three users, we found the following:
-
In response to the disappearance of the dialog box, the first reaction of the user is that he has not remembered what needs to be done, so the first reaction at the moment is to find the location to view the dialog content again. Because we think that the dialog box recall logic implementation is in line with the needs of the user in the process of the game, but the subsequent optimization can consider whether to add a task list to the user after the end of the information dialog. This will guide the user directly through the subsequent operations
-
For recalling the dialogue near the npc, the task should be triggered by the user's initiative, rather than by the distance between the characters, because it is easy to trigger the dialogue when the user is walking, and we cannot interrupt the dialogue.
Conclusion: According to the feedback content, our team quickly modified the corresponding code correspondence. According to the distance judgment, the dialogue was displayed and modified to the point that the user needed to actively press the f key to call the dialogue. But this requires educating the user at the beginning of the game. The cost is larger
- whether can interrupt the dialogue this matter, there is a big question inside itself. We wanted the user to keep receiving the message from the npc, so we didn't add a break button, but we did provide a way to restart the conversation for the user who skipped it.
- 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