-
Notifications
You must be signed in to change notification settings - Fork 1
Sprint 3: Collection Game in Chap 1 to 3 (Team 9)
In this sprint, our team is working on implementing collection games between chapters 1 and 3:
- In chap1, the player is supposed to repairs the electric switch by collecting batteries
- In chap2, according to dialogue between the player and the npc, player will receive instructions to collect several corals for clues
- In chap3, the player collects different numbers of corals, water plants and seaweeds according to their choice
For more details about the game process: Game Process in Detail
We are not only need to draw the required props, but also communicate with the previous prop group and the group responsible for npc interaction now, in order to cooperate to implement this game.
The following shows the sequence of tasks in sprint3:
-
We need to formulate code requirements, specific to which functions are required to implement this game. Then we need to think about which existing functions need to be called, and actively communicate with other groups.
-
We need to do a post-survey questionnaire to conduct interest surveys and result analysis on the features that the game is about to present.
-
We need to study what props are needed for the three games, and then start graphic design, and constantly ask other people for their opinions to make changes.
-
We will implement these three games through code, and we need to be able to actually show our functions and gameplay in the whole game.
This is the first step of our sprint3 task, we query the story background in chap1 to 3 as follows:
- Collection game background: NPC Communication Play Script
Then we got the general game requirements, and we started working on writing the required functions and what other team functions need to be called, see the following link for details:
- Code requirements details: Code Requirements for Collection Game in Chapter 1 to 3
This test mainly adopts the form of a questionnaire. Through the questionnaire, we can learn the players' preferences for some details of the game, so as to better realize the task of collecting the game.
- The link to the questionnaire is as follows: Questionnaire on Collection Games
After the questionnaire survey, we got the corresponding results, which will be of great help to the design of our future collection game functions.
- The following is the whole process of user testing: User testing
This part is mainly presenting the design process of the object image in these collecting games. It shows the complete design idea from requirements to reference picture research.
- Here is the wiki page: Object Design for Collecting Games inside Each Chapter
- 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