robertwetzler / zeldaremade Goto Github PK

Create all sprite classes (ISprite implementations) for all enemies

• Draw method with correct source bounding box
• If animated sprite, cycle through animation frames
  There's a lot of enemies to make for this, so we can split this up among multiple people if needed

Consider dependency graphs from class

• Each enemy has it's own movement path
• Each enemy has it's own projectile

TODO:

1. Create an Enemy Interface that includes methods that enemies share.
2. Refactor enemy classes to extend the enemy interface

NPCs: Merchant, Old man, Flame
Enemies: Bat, Skeleton, Dog, Big and small jellies, hand, trap, snake, dragon, dinosaur

Depends on Level loading

• Character moves with keys
• Character spawns items
• Character animates (walking, using items)
• Character takes damage

Likely using decorator pattern

TODO:

1. Create an Enemy Interface that includes methods that enemies share.
2. Refactor enemy classes to extend the enemy interface

NPCs: Merchant, Old man, Flame
Enemies: Bat, Skeleton, Dog, Big and small jellies, hand, trap, snake, dragon, dinosaur

https://www.spriters-resource.com/nes/legendofzelda/
Player
• Link (animated)
• Wooden Sword
• Sword beam
• Arrows
• Boomerang
• Bombs
• Blue Candle
• Blue Potion
• Blue ring
Items
• Compass
• Key
• Heart container
• Wooden boomerang
• Bow
• Heart
• Rupee
• Arrow
• Bomb
• Fairy
• Clock
Enemies and NPCs
• Bat (keese)
• Skeleton (stalfos)
• Dog-like monster (goriya)
• Jelly (gel-small and zol-big)
• Hand (wall master)
• Spike cross (trap)
• Snake (rope)
• Boss/Dragon (aquamentus)
• Boss/Dragon fireballs
• Boss/Dinosaur (Dodongo)
• Old man
• Merchant
• Flame
Environment – interactive
• Statues
• Square, sometimes movable block
• Walls
• Locked door
• Shut door
• Open door
• Bombed opening
• Gap tile
• Stairs
• Ladder tile
• Brick tile
• Fire
Environment – non-interactive
• Floor tile
• Room border

Sprites need to be created for the player, enemies, and the items (and likely the map).

Creating a sprite involves creating the sprite sheet and implementing an ISprite class for that sprite

Sprite List:
https://www.spriters-resource.com/nes/legendofzelda/
Player
• Link (animated)
• Wooden Sword
• Sword beam
• Arrows
• Boomerang
• Bombs
• Blue Candle
• Blue Potion
• Blue ring
Items
• Compass
• Key
• Heart container
• Wooden boomerang
• Bow
• Heart
• Rupee
• Arrow
• Bomb
• Fairy
• Clock
Enemies and NPCs
• Bat (keese)
• Skeleton (stalfos)
• Dog-like monster (goriya)
• Jelly (gel-small and zol-big)
• Hand (wall master)
• Spike cross (trap)
• Snake (rope)
• Boss/Dragon (aquamentus)
• Boss/Dragon fireballs
• Boss/Dinosaur (Dodongo)
• Old man
• Merchant
• Flame
Environment – interactive
• Statues
• Square, sometimes movable block
• Walls
• Locked door
• Shut door
• Open door
• Bombed opening
• Gap tile
• Stairs
• Ladder tile
• Brick tile
• Fire
Environment – non-interactive
• Floor tile
• Room border

When Link attacks with sword upwards, he should stay in the same position instead of moving downwards

I have finished when I have

1. Created command classes for getting next and previous block sprites
2. Mapped 'Get next block' command to 'y' key and 'get previous block' command to 't' key in Keyboard controller
3. When running, the game will change what block sprite is drawn when the 't' or 'y' key is pressed

Create all sprite classes (ISprite implementations) for all items

• Draw method with correct source bounding box
• If animated sprite, cycle through animation frames

Player sprites include:

• link movement animation
• link use item or weapon animation
• link pickup item animation
• link use sword animation

Solidify command interface

Should include:

• Movement
• Actions
• Damage

• Item movement
• Command to cycle through items shown
• Animation

Create all sprite classes (ISprite implementations) for the player

• Draw method with correct source bounding box
• If animated sprite, cycle through animation frames

• Draw
• Update

Knock-back and animation

Depend on Store room layout as tree/graph

Make sure all team members have been added to the project.
Enter start and end dates for Sprint 2.
Add several product backlog items (rows on the board) for the requirements for this sprint (controllers, commands, objects, sprites, etc.) and assign them to Sprint 2.
Add tasks with effort amounts and assign each to someone.
Examples could include:
Add a task for creating interfaces (or you can let the person responsible for each part of the implementation choose when to provide interfaces).
Add a task for creating a Link class.
Add a task for handling Link's state transitions.
Add a task for creating enemy classes.
Add a task for creating item classes.
Add a task for creating block class(es).
Add tasks for implementing commands and controllers.
Add a task to implement keyboard input.
Some advice: for Sprint 2 the player character logic is disproportionately larger than most of the other features, so it is recommended to split this work between at least two members.

After #5 is completed, create a class for each item

• Each item has to display/cycle through it's sprites
• Register each item class to the command that cycles through them
• No interaction with other things currently

• Implement draw and update (consider animated blocks)
• Register block classes to command that cycles through them

Create all sprite classes (ISprite implementations) for all blocks

• Draw method with correct source bounding box
• If animated sprite, cycle through animation frames

All logic for collision detection

• Cycle forward/previous for blocks, items, enemies
• Reset command
• Quit command
  Player commands
• attack using sword
• WASD walking
• Switch items (1,2,3, etc)
• Take damage

WASD controls move and animate link

Create concrete Sprite classes (derived from ISprite) for each enemy/NPC, item, player, and block

• Movement
• Animation
• Using items
• Take damage

IEntity

• Link and Enemies derive from this
• Animation, using items, (potentially) taking damage

IEnemy

• derives from IEntity
• method for automated movement

IPlayer

• derives from IEntity
• methods for movement via input (using command design pattern)

Using weapons and items