-
Notifications
You must be signed in to change notification settings - Fork 1
Team7:User Survery Improve features based on the win lose logic and eviction menu ( Polishing tasks)
Sprint 4 - Team 7 Feature ticket: Improve features based on the win/lose logic and eviction menu ( Polishing tasks)
Players in Atlantis sinking! need to players must collect the information about the traitor who would cause the continent's sinking via the adventure, and then evict them from the continent after validating the information to rescue Atlantis. By progressive working on the eviction menu during the previous 3 sprints, our team completed almost all the essential features. The game now features a full eviction menu function and win-lose condition for selecting and evicting traitors. Based on this, In order to raise the attractiveness of the game and enable players to experience the game plot more immersively, we need to include some intriguing changes to make the game more "juicy", such as transition animations, special effects, sound effects, etc..
Conducting this predesign user survey will help us make foundational decisions about how to improve our feature.
Imagine how the user would interact with the eviction function throughout the game, and consider how to tweak our menu to make our feature juicer, based on the results of the previous three sprints. These feature-related questions were prepared for a Google form and a Tencent survey. The questionnaire inquires about the players' anticipations towards the completion of the game and the interactivity of the win/lose prompt box.
Multiple individuals will be requested to complete and submit the questionnaire. There was no time limit for completing the questionnaire. Only the replies will be utilized to build visual representations as raw data, and all comments will remain anonymous.
Google forms (Polishing tasks) link
Tencent Questionnaire (Polishing tasks) link
In user testing in sprint3, the final question of the questionnaire also gathered ideas on how to improve the expulsion menu. By analyzing this collected data: add proper special effect to the win/loss popup, add transition interface (animation) after triggering select action
and add sound effects to the corresponding parts were expected to be implemented in the eviction menu.
During the following investigation, we obtained the desired feedback about how and where to implement transition animation and sound effects.
According to the result of Q1
The purpose of this question is to investigate where and when appropriate sound effects can be added to make players more engaged in the game and thus have a better experience. By analysing the collected responses, Most users want to hear the sound effect when the win/LOSE window pops up, followed by when the user clicks on the NPC card to open the information cue box. The number of users who want to add sound effects to the select button is minimal, this may because the sound of "select action" is not the main point of the interaction,too many sound effects can have a negative effect. Therefore, our team might add appropriate sound effects when the win/lose prompt windows and the information/clues prompt window pop up.
According to the result of Q2
It is mainly for deciding the method of how to implement different transition animations when users selected different NPCs on the eviction menu. According to the collected data, more users (60%) expect the transition animation to be designed according to the different NPC characters so that it is more reasonable and meets users' expectations. Depending on different times of selection to design the transition animation makes some sense, but it seems cannot give the players a smoother transition with the action of selecting the traitor. Therefore, designers in our team will prioritize the design of transition animations based on different NPCs' profiles.
According to the result of Q3
The question is to investigate whether the current design of the eviction menu can be adapted to a variety of screen sizes. From this result, the majority of users are relatively satisfied with the current menu picture text display results. But there may still be some issues because just a few people marked it as 5, such as some parts of content being slightly elongated.... Therefore, our team will improve and fix these deficiencies in this final phase.
![Suvery1](https://user-images.githubusercontent.com/109838814/195223541-c49293d5-693f-4ffe-b38d-2106661d71c7.png)
![Suvery2](https://user-images.githubusercontent.com/109838814/195226972-492867b1-34f2-4cec-8e23-eead88f497bc.png)
![Suvery3](https://user-images.githubusercontent.com/109838814/195223559-89683324-316e-4e7b-8546-fb36c71b1bba.png)
- 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