pkwagner / breakout Goto Github PK

• Create more default levels
• Level-Switching on level complete

• Ball
• Block
• Lives
• Stick
• Fix test errors

• fix multiplayer particle

• Handle multiple hits
• Change block image based on remaining hits

• New block images
• New stick image
• Animations?
• Game icon
• Item images (slomo, speedup, speeddown, bigger, smaller, smash, healing)
• Menu background
• Back button (arrow)

• Render component
• Adapt to the player model
• JavaDoc

Branch: show-destroyed-blocks

On the current master, closing the application causes this exception:

• Start game on key press (halt game on "new game" until key press)

Branch: game-init

• Multi-hit (smash?) ball [temporary]
• Additional balls
• Slo-Mo (ball, stick and clock speed (!) decrease)

* implementation pending until the improved collision model is implemented

• Move all static constants to that class
• Move enums (directions, blockType) to that class

• Block is hittable
• Block cannot cross broders
• Block does have actual movement.

Pressing ESC while in this state causes strange behaviour:

• block view
• block controller
• IHittable implementation
• Switch/Case for enums (BlockType)
• Correct block collision bump velocity
• Comments

• Health handling
• Ball reset

• Player name field in game over screen
• Submit/Go to menu button

I think the slow-mo powerup should slow down ram-block movement aswell.

• Nicer / Smaller buttons

Depending on how you hit the ball with the stick the ball should have a different move out angle.

Branch: stick-velocity-change

• Add highscore
• Game over state

• Load data file
• Save data file based on internal representation
• Display Menu (State)
• Write Javadoc comments
• Write Adapter code
• Unit test file loading

Branch: highscore

• Start watch
• Update ongoing time
• Display time on screen

• Background music (maybe just ambiace sounds)
  Audio-Clips:
  • Block hit
  • Stick hit
  • Item-Sound?
• Sound controller for better error management

During testing, I found out that in some cases the ball overlaps with another entity (in this case the border and the stick).

So the ball could also collide with a border and will stuck in it, because after the next tick it's not fast enough and still collides with it. Since we are only inverting the movement vector, it moves forth and back.

• Side collision with the stick
• JavaDoc BallCollideEvent
• JavaDoc onCollide
• Correctly detect collision direction with blocks
• Separate logic of block collision (block health)
• JavaDoc BlockCollideAction
• Reset position on border, stick and block collision

Branch: ball-collision

• HighScore - > Main menu
• Paused game -> Main menu
• Bring pause image to the foreground
• Credits - > Main menu
• JavaDoc

Branch: back-button

• Buttons
• Switch to state if button is pressed

• Volume
• Music checkbox
• Sound effects checkbox
• Keymap
• Fix back-button
• Change value listener
• Check for duplicate key bindings

! Please DO NOT do this before tomorrow to avoid merge conflicts with branch 'comments-and-contracts' !

• New main menu entry
• Credits-State
• Show developer information

• Pause game rendering
• Pause game updating
• Keyboard Shortcut
• Display pause text on screen
• Write Javadoc comments

Branch: pause

• Multiple balls
• Multiple controllers

• Lives handling
• Amount of destroyed blocks
• Elapsed time? -> Clock [solved]
• Game started (boolean) -> Clock [solved]

It seems that the block still move on pause (even over other blocks) and could collide with the ball.

Ball speed increases using a constant value (inside the GameParameters)

• Shorter/Bigger Stick
• Slower/Faster Ball
• Items fall
• Items pickup