Auxiliary class-challenge: Improving breakout games

 

Challenge: improved breakout games

You can try to set more lifecycles for players, or add a menu as in the previous chapter to improve the game. You can also use the breakout game as a testing platform to test the auxiliary classes implemented so far. For example, each time a player completes a level or breaks a brick, a log message can be written.

The next chapter introduces the input class, which makes it easier to capture all input from the Controller. As with the rumble support of gamepad in the previous chapter, the game can make a very good improvement, shake the screen when the bricks are broken, or add simple explosion images. The sky background is a limitation. If you really like arcade games, there are many ways to improve it to make it more fun.

You may be more interested in helper classes and want to use your new knowledge to add and test your own helper classes. Now is the time to do this. The next chapter focuses on reusability. The next few chapters will only talk about creating a 3D engine, and you may forget all the useful auxiliary classes, until you miss a feature you might forget about all the useful helper classes until you miss some feature. However, the advantage of the helper class is that it is easy to improve at any time. They may become a little larger like the stringhelper class, but you can refactor it all the time ).