phrb / brickbreaker Goto Github PK

Implement support for 2 simultaneous players.

Implement different brick types:

• Size
• Number of hits to break
• Color
• Moving? (see #14)

Select good audio samples for:

• Ball collision with walls, paddle and bricks
• Brick breaks
• Death / Victory conditions
• Player goes over a certain score
• Player performs a brick breaking combo

Implement bricks that move according to some pre-estabilished pattern.

Implement special bricks or items that appear randomly and last for a certain time.

Those collectibles can be hit for extra points or multipliers.

Implement a tutorial level, teaching the player the basic mechanics and controls.

Enable paddle control using the phone's accelerometer.

We should select a theme for the sprites and textures, and then select matching resources.

Implement power up for allowing the player to exert a field force over the ball with the slider.

Get rid of all magic numbers in the code. They could be moved to a configuration file.

Implement extra visual effects for:

• Brick breaking
• Explosion when performing combos
• Death

Implement persistent high-scores.

How to cache values in android using Godot? Configuration files?

Implement a winning condition when all bricks are destroyed, and a losing condition when the ball falls off-screen.

Implement pinball mechanics such as:

• Black holes
• Boosters

Write a README explaining how to install Godot and configure Android Exports.

The brick scenes should be generated dynamically using Godot Script.

Number and positioning of bricks should be parametrized.

Generate a randomized level according to some difficulty parameter, an int from 1 to 5 for example.

Users should be able to start, configure and select levels.

The screen size should be dynamic and handle landscape mode (or always force portrait).

Implement and ellipsoid level. The paddle must rotate around the bricks and there must be no walls.

We need at least 2 easy, 2 intermediate and 1 hard features for this assignment.

These are the issues assigned to the first due date milestone, mouseover to see issue name.

Not an assignment feature, but needs fixing:

• #1
• #18
• #19
• #20
• #21
• #22
• #25

Easy:

• #16
• #15
• #9
• #6
• #5
• #3

Intermediate:

• #14
• #13
• #10
• #4
• #2
• #26

Hard:

• #12
• #11
• #8
• #7

Implement a level-builder that enables players to generate their own levels.

Implement the power-ups and downs suggested by Lucas, and any others possible.

• #26
• #31

Single touches or clicks should create a new ball only once.