Jump to content
  • Advertisement
Sign in to follow this  
phil67rpg

first breakout game

This topic is 1911 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Advertisement

Hello,

 

I like the charm behind the graphics and the fact that you are continuing to improve a project beyond its finish. There are a few criticisms that I would like to raise though:

 

  1. Implement Lives.
  2. There is a delay between pressing a key, to the paddle actually moving. So much so that you could miss the ball numerous times on i missing the paddle.
  3. A timer after the ball resets position, but before it starts moving again.
  4. Trajectory of the ball being affected by where it hits the paddle.
  5. Instructions need to disappear after first ball launch.
  6. End of game trigger when all bricks disappear.
  7. Ball speeds up on each successful paddle contact.

These are the first few things that come to mind, but would improve the game significantly, and give you the opportunity to think about logic that you may not have attempted yet.

 

I hope this is of help and I look forward to your next iteration.

 

Regards,

 

Stitchs.

Share this post


Link to post
Share on other sites

thanks a lot for the advice, I am glad  you liked it. my next thing I am going to implement is  a splash screen. That will help with interacting with the game.

Share this post


Link to post
Share on other sites

When you implement the Splash-Screen, try to ensure that you don't just render it over the top of the game field i.e. the actual game logic doesn't run at the same time. This could lead to the user viewing what they think is the beginning page, but then entering the game whilst the logic has been running and starting out with, for example; less lives than expected, some bricks missing, or even the Game Over message.

 

What I'm trying to get at here is, now that you are looking at another component (The Menu), try researching into State Machines to break up the code, and ensure not everything is trying to be run at once. It can be as simple as using a Switch-Case to make sure only the Menu runs until the player decides to enter the Game, then the Game runs and the Menu is only accessed again, when the user wants to quit.

 

A lot of information here, I got a bit carried away. Feel free to ask a question if there's anything unclear.

 

Regards,

 

Stitchs.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!