Team-2 Feature Ticket-Character Status/Player Status

[YuanyeZhang]

Description

This feature gives different statuses to the characters in the game. Our current concept is for the player to get different statuses as the game progresses. These states can be interpreted as an additional task like hunger means the player needs to get food; empty blood bar means the failure of the game. Additionally, players may be rewarded for random events, to get some positive/negative status.

We will define the character's own attributes, including health bar, stamina, thirst, and hunger. It may also include the player's location. And define the negative states that may occur as the game progresses, such as thirsty, hungry.

We only consider the possible state of the character affected by its own factors, which is defined as the basic state. We are responsible for defining these States and considering the impact of these States and trigger conditions. We will not consider the gain buff/debuff caused by additional items. Such as an equipment bonus. The act of obtaining food will also be considered as enhancing buff, regardless of the basic state

SubFeature/component (optional)

If the ticket contains multiple components, you should explain them in more detail here.

Examples (optional)

Character attributes：

1. Health bar -- ❤❤❤❤❤
2. Degree of thirst -- Decrease with time - 💧💧💧💧
3. Degree of hunger -- Decrease with time - 🍗🍗🍗🍗
4. Location -- (0, 0)

• future Speed -- Walking speed and running speed ---future stamina -- rises when walking and decreases when running ------future

define

• Initial state The player's initial state, including initial health, stamina, Degree of thirst, Degree of hunger

• Negative status - effect in-game - trigger condition

  1. Thirsty - continuous blood loss - 💧/15 seconds -- lose 1x❤ for each 10 second
  2. Hungry - slow down - 🍗/10 seconds -- when you have no 🍗
  3. Dead - game over - empty HP

• future:

  3. Tired - Running is not allowed - the player is limited by his stamina. When stamina is empty---future
  4. Injured - Warning signs - More than half of the HP, but not full---future
  5. Dying - Warning signs - Players have less than 1 / 4 of their HP left---future
  6. Dangerous - warning - enemy nearby---future
  7. Running - speed up - (press shift) when stamina is not empty---future

Dependencies

Status based on Buffs/Debuffs - Team 3 (the influence of different buffs/ debuffs the players got) Status based on Main Character Player - Team 4 (which status it displays depends on where and what the player is doing) Status based on Random Obstacles - Team 8 (the specific obstacles will cause the change of status) Status based on NPC, Assign missions for Storyline - Team 7 (when the player was assigned a dangerous missions, the status might be affected and changed)

Milestones

List of sub-features you intend to have done and in Master by the end of the sprint.

• [ ] Implement algorithm for status condition---e.g. Players need to eat once within 30 seconds(Aug. 20)
• [ ] Implement the effect of this status---e.g. speedup/slow down(Aug. 23)
• [ ] Implement status bar---health bar, speed, location (Aug. 26)
• [ ] Implement some basic function Character class - health reduce (Aug. 28)

Extras (optional)

• [ ] Extra components that you may implement if you get time.
• [ ] ...

Documentation

• Main description of feature
• User documentation
• ...

Members

• Name (GitLab Username) (Slack Handle) -- only one is needed if they are the same.
• Yuanye Zhang(@YuanyeZhang) (Jared Zhang)
• He Zhu(@GavintheLionHeart ) (He Zhu)
• Nathanael Peters(@nathanael-peters) (Nathanael Peters)

[lisslulay]

Hi, Do you have the intention to implement the function of reducing health? #14 would like to call reducing health and speed function.

Another question: does the position of the character is included in character status?

[uqtnieva]

Hey! Great start.

I think it would be good to start thinking about how a player can lose the game (GAME OVER) e.g. If they don't eat every 30 seconds, they might lose health (and include this in the feature ticket) AND how this will look on the game: will it be displayed as a bar or hearts?

For your feature, it would be good to communicate with team 6 #5 who are doing the world generation/ending screen and team 3 who are covering buffs/debuffs.

There seems to be some overlap with team 3 #10 as to who is implementing the buffs/debuffs (writing the code to slow the character down, etc).

Finally, events are not being implemented in Sprint 1 so remove them from this ticket and include them in a future sprint.

[uqtnieva]

On team 6's ticket #5 :

Looks good!

Double-checking: is your team covering the game over screen as well?

[YuanyeZhang]

To avoid overlapping with team3, we have made some updates