Skip to content

Sprint 3: Collection Game in Chap 1 to 3 (Team 9)

snakefen edited this page Oct 4, 2022 · 18 revisions

Introduction

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.

Task arrangement

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.

Code design

This is the first step of our sprint3 task, we query the story background in chap1 to 3 as follows:

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:

Testing plan

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.

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

Graphic design

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.

Table of Contents

Home

Game Design

User survey

Sprint 4

Eviction Menu and Win/lose Logic: Polishing tasks (Team 7)

Button Sounds and Ending Menu improve (Team 3)

Sound effect and Fixing the clue bug (Team 6)

Improvement of Enemy and Attack (Team 1)

Add Features When The Player Get Attacked and Overall UI Improvement (Team 8)

Sprint 1

Achievement System (Team 2)

Player Eviction Menu (Team 7)

Countdown Clock (Team 4)

Music (Team3)

Map (Team6)

Sprint 2

Player Eviction Menu (Team 7)

Character Design & Animation (Team 1)

Music (Team 3)

Inventory System and Consumables Items (Team 8)

Scenario design

Achievement System(team 2)

Storyline (Team 5)

Countdown Clock (Team 4)

Sprint 3

Ending Menu (Team 3)

NPC interaction (Team 2)

Win/lose Condition (Based on Eviction Menu) (Team 7)

Player Profile (Team 4)

Game Logo (Team 8)

Clue storage (Team 6)

Enemy Design and Attack (Team 1)

Scenario design for village(Team5)

Game design
Entities and Components

Service Locator

Loading Resources

Logging

Unit Testing

Debug Terminal

Input Handling

UI

Animations

Audio

AI

Physics

Game Screens and Areas

Terrain

Concurrency & Threading

Settings

Troubleshooting

MacOS Setup Guide

Clone this wiki locally