-
Notifications
You must be signed in to change notification settings - Fork 1
Village user test
In sprint 3, we were mainly aimed to designing the scenarios of village on the basis of storyline designed before and the gameplay mode.During the design, we also have some middle versions to meet the users' satisfactions.The purpose of this user test was to deplore a more appropriate scene for the village, making the whole game more consistentand improve the design for users' experience and acceptance being taken into account.
- to ensure whether the present version of design can be accpeted by users and attain some advice from them for further polishment
The user test is designed for collecting effective feedbacks and suggestions to make a balance between user experience and degree of design adaptation with other scenarios.Thus, we use several methods to achieve this goal.
-
Hypothesis:to confirm there is a sufficient number of potential players who are willing to help us finish the test, since it's important to meet their expectations.
-
Design:to evaluate the continuity of the consistency in the game's graphic design when players are moving from one scene to another scene, avoiding too much contrast.Then we make some imporvement by virtue of the feedbacks collected.
-
Evaluation: based on the feedbacks received to change some details and make the design look more comfortable.
Our team have had a discussion about the test target and finally determined to conduct internal tests to test the acceptance of users and whether the village design fit with the rest scenarios of the game.
The general feeling about the village design
Details in design (from aspects like color,scene layout, design style, etc.)
The continuity of the whole game design
Degree of satisfaction with the quality of the picture
Other advice(like adding some components or anything else)
Collect feedbacks from the questionnaire above
Analyze the result of questionnaire filled by users and make conclusions
Test among internal studio students and other random passerby at school
From the comments and scores we received from questionnaire, it is easy to see that users are basically satisfied with our overall design evalution. However, we still have several aspects to modify.For example, the layout of the whole village, continuity of the whole game design and the quality of the picture, all of which need to be improved. We will discuss about the next step to improve user experience mechanics and game experience.
In addition, we actually had considered whether to design the specific scene of the opera and come to an conclusion that only the exterior is enough because opera just appeared once in the storyline and we would elaborate the design of village cuz players need to stir about it than to spend much time designing the interior details of the opera.
- 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