Team 3 (Puzzles) #3
Description
Description
This should be roughly a one paragraph description of the features / ideas on which your team plans to work. It should very briefly touch on why you think it should be in the game (e.g. "Adds an extra layer of depth to game play"). It should also describe how it will appear or be used in the final product (e.g. "On starting a level, the game will generate a random, procedurally-generated map").
This feature ticket focuses on implementing different types of puzzles that provide interactive challenges to the player whilst controlling progression through the game. Puzzles may involve moving objects, pressing buttons, activating triggers, stepping on pressure plates etc. that allow the player to receive rewards or enter different areas of the game map.
SubFeature/component (optional)
If the ticket contains multiple components, you should explain them in more detail here.
Moveable objects: boxes or other objects can be pushed/pulled/liffed by player from one location to another.
Button presses: player presses button to interact with another game object, such as raising or lowering a platform.
Pressure plates: player steps on pressure plate (or moves object onto it) to affect a change, such as opening a door.
Light sensors: player has to avoid entering a lit area that otherwise triggers a negative effect.
Examples (optional)
- Part/Feature: Depending on the ticket, you will often want to provide some examples of how it would play out in the game. See next point for example...
- map seed: maps can be generated from a "seed" where there may be different attributes, e.g. island, mainland, etc.
Dependencies
List any features on which this ticket relies. If there is already an existing ticket, reference it using #xx. If a feature needs to be implemented and the issue does not already exist... make a new ticket and leave it unassigned for someone else to take on.
e.g. Random game mode relies on random map seed generation(#xx).
Milestones
List of sub-features you intend to have done and in Master by the end of the sprint.
- Goal 1 (Aug. 20)
- Goal 2 (Aug. 23)
- Goal 3 (Aug. 26)
- Goal 4 (Aug. 28)
Completion Deadline: Aug. 30
Extras (optional)
- Extra components that you may implement if you get time.
- ...
Documentation
Members
- Name (GitHub Username) (Slack Handle) -- only one is needed if they are the same.
- e.g. Richard (@applebyter) (Richard Thomas)