azuelle / bombescape Goto Github PK

Usage examples

• Letting the user input their name when getting a new score
• Typing in settings

Requirements

• A coordinate will be passed to the function that signifies the start of the input area
• A max length will be given, and the user cannot input more characters after reaching it
• Allow for the usage of backspace, and enter for confirmation
• Should echo back what the user has inputted onscreen (each frame)
• Should loop itself until the user has confirmed input

Compatibility with ncurses still needs to be maintained (i.e. only getch() can be used for fetching user input).

std::stringstream might help with this.

As specified in README.md.

So that frame time can be fetched for purposes like #10.

To return the corresponding Input type when the player presses certain keys.
Should be implemented in control.cpp/getInput().

In game_logic.h and .cpp, implement the actual gameplay logics and processing happening each cycle, following the description in README.

What needs to be processed

• Check if item timers have run out
  • Execute onDeath() afterwards
  • If item is bomb
    • Check if player's in range
      • Modify Health
    • Check if other items are in range
      • Execute their onDeath() and delete afterwards
      • Watch out for repeated executions (probably should have a flag for executed ones)
  • Remove item
• Respond to player action
  • Validation
  • Change position / add item / etc. if valid
• Item generation (maybe not each frame)

As this would be a pretty big task, we should probably have multiple people work on this (or split this into smaller tasks).

For convenient printing since ncurses only supports printing strings onscreen.

std::stringstream might help with this.

Enable warnings/errors and game tips to be displayed onscreen for a certain time.
Previous ones would be overwritten by new messages.

The foundations have already been laid in 71fea26.
Entities have a base class Entity which derives into Bomb, PowerUp, Traps, etc. (add more when new entity types are needed, maybe barricade?), each can be assigned to different persons if needed.
Each entity instance has a timer and a onDeath() function (differs from type to type) which determines when it "dies" and what it does then, e. g. Bombs explode and kill other entity in range.

Current Progress

• Base type Entity
• Bomb
• Barricade
• PowerUp
• Trap

Our project doesn't have a name yet