kittenatheart / 06-juicy-breakout

A Godot-implementation of the GDC presentation, "Juice it or Lose it"

06-Juicy-Breakout

Brick Breaker game implementing "juicy" features to make the game more interesting.

Background photo by Paweł Czerwiński on Unsplash Music and sound effects by Shannon Master

1. back ground image
2. win screen backrouns image
3. lose screen background image
4. comet trail on ball
5. bricks color change
6. background music
7. lose life sound effect
8. brick break sound effect
9. lose life animation
10. eyes on paddle
11. mouth on paddle
12. eyes moving
13. mouth moving
14. lose screen animation - maybe
15. lose screen sound effect
16. win screen animation

This is an opportunity for you to implement some of the "juicy" features as demonstrated in the 2012 GDC presentation, "Juice it or Lose it."

I have provided a simple, generic brick breaker game, built in Godot. You can use the presentation as a guide or use your own imagination, but your assignment is to make the game feel more "juicy": kinetic, reactive, physical.

Please list the features you add in the README.md. You will be awarded one point per feature you add (including a soundtrack and sound effects). Some of the features demonstrated in the presentation include:

• Changing the color of the paddle, ball, and blocks
• Animate how the blocks and the paddle appear on the screen
• Squeeze and stretch the paddle
• Animate the size of the ball when it hits something
• Wobble the ball after it hits something
• Animate the color of the ball after it hits something
• Shake the blocks or the paddle when the ball hits something
• Add sound effects
• Add music
• Add particles when a block is hit
• Add particles when the paddle is hit
• Make the blocks fall off the screen when they are hit
• Make the blocks rotate as they are hit
• Break the blocks when they are hit
• Add a comet trail to the ball
• Add screen shake
• Add eyes to the paddle
• Make the eyes blink
• Make the eyes follow the ball
• Add a smile to the paddle and animate it based on the location of the ball
• Add a background to the game
• etc.

When you are done, update the LICENSE and README.md, commit and push your code to GitHub, and turn in the URL for your repository on Canvas.

---

The grading criteria will be as follows:

• [1 point] Assignment turned in on time
• [1] Repository contains a descriptive README.md
• [1] No (script) syntax errors
• [1] No other runtime errors
• [16] Features to make the game more "juicy"