-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint 4: Improvement of Collection Game (Team 9)
In this sprint, we want to implement the game functions that have not yet been implemented in sprint3, which can be roughly divided into the following steps:
- Conduct user testing
- Write code requirements and basic structure document
- Design pictures according to the game background
- Write code with the code requirements document
- Do unit test according to the finished code
All the above steps also need to be established in active communication with other groups, discuss the game progress with the npc interaction group, discuss the placement of the design pictures with the scene group, and actively communicate with the props group about the inplement of the inventory in order to debug.
In the process of making the basic framework of the code, we often need to face many different choices. We hope that our design can meet the needs of most players, so the first step of this sprint work is to develop a questionnaire to understand the current players' needs, and the preference of players when it comes some of the choices we will encounter in design in the future.
The link to the questionnaire is following: Collection Game Improvement Questionnaire
Through the results generated by the questionnaire, our team will analyze the results so that we can design game requirements and design required pictures in the future.
Following is a link to the results of the analysis: User Testing Result and Analyze
After the questionnaire survey, through the analysis of the results, we have learned the current preference of most players, and we will try our best to realize the game content required by the players under the condition of technical support.
Specific documentation are as follows: Improvement of Code Requirements for Collection Game in Chapter 1 to 3
The graphic designs for this sprint is to help complete the game process. They are mainly the pop-up pictures of announcement boards and some supplementary icons to consummate the game logic.
Here shows the complete process of Graphic Designs for the Improvement of Collecting Games
The link to the textual description of the process of collecting the task: Process of collecting the task
- 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