ramondelafuente/moonshot

moonshot's Issues

Bullets that exit the screen self-destruct

Once a bullet completely leaves the viewport, it destroys itsself.

Make a splash-screen with the credits

At least add some reference to the godlike creatures that have invested their precious resources into the creation of this thing...

Give a player three lives

A player should have three 3 lives when the game starts. If they are hit by an alien bullet or hit by an alien, the amount should decrease by 1. If the amount reaches 0, the game is over.

This might be a splittable story:

• Add a property on the player for the livesLeft
• Reduce the number of lives when hit by an alien bullet (requires #28)
• Add an overlay/HUD that contains the number of lives so it's visible for the player
• End the game when the lives reach 0

Compile the game to make sure we know how that works (spike)

A "play again?" button after the game is finished

Add pause button

Add Pause game as a key button "P" on the trl_game object, see GameMaker functions for inspiration:

instance_deactivate_all(true);
instance_activate_region(...);

Cleanup unused objects

• TextWindow

Add a visually attractive player

Accellerate aliens when there are fewer left

Have aliens fire bullets too

Currently the aliens only move but they should also fire bullets. This happens randomly and there should be no more than 3 aliens be firing at the same time (this is what roughly happens in the original space invaders game). If a bullet hits the player, the amount of lives a player has decreases by 1.

Rename the assets according to the rules

See README.md

Start documentation

We should start documenting decisions and adding some basics to the readme file.

• Credits for creators and content makers
• Code style and Object naming conventions
• Basic development rules
• Writing/Running tests
• The Event system

Add a visually attractive alien

Possible stories for later:

• 3 different types of alien
• animated aliens

Start the game in a main menu

The game should start in a main-menu, and have an option to start playing.

This should make it a little easier for us to code the win/loss scenario without global variables. "Restart" should then be "Reload the game room".

It also gives us some options like "run the tests" before any game-specific code has run (because everything affects everything else and we want to run tests in isolation).

Add a visual queue that you have won/lost

• A white text in the centre of the screen: You won! (blinking if you want brownie points)
• A red text in the center of the screen: You lost!

Lose the game when an alien hits the bottom row

Generate a full grid of aliens in the start position

"Aliens" are green squares called obj_alien. Generate a full grid of aliens 11 wide and 5 high in code at game/room startup.

Implement alien movement

Aliens move to the right, then down, then back left, and down again. Rinse, cycle, repeat!

When an alien hits the viewport boundary, the entire grid of aliens (the ones that are left over) go down and change direction.
So: when moving to thr right, when hitting the viewport boundary on the right, all aliens go down and start moving left.

Alien collision with the player ends the game

Allow shooting multiple times

Allow multiple shots to be fired, but always only one active (on screen) bullet at a time.
Currently, only one shot can be fired.

Add a kickass @mitchett original soundtrack!

Solve continuous looping when the game is lost.

Currently, when the game is "lost", a global variable is set that skips certain actions. But the game loop is still running and "skipping" due to if-statements in the code.

We should think more in events, and make sure we fire an event for "game end" instead of adding if-statements that check the global variable.

In the "moar sounds" PR, the player object is destroyed on loss to prevent contuous collision detection.

Rename "Dot" to bullet

Limit player to screen boundaries

Block player movement at 32 pixels from the viewport edges (left and right)

Add a visually attractive bullet

Investigate automated tests (spike)

It looks like GameMaker has an extension that allows some form of autmated testing to be done. Let's investigate!

https://gmcore.io/browse.html
https://gmcore.io/gmtest/

Add some basic sounds to the actions

• file bullet
• hit alien
• game over (win)
• game over (loss)