codexguajil / frogger Goto Github PK

the Game object should keep track of points, TIME (!), number of lives, maybe even the number of frogs in the end row?

Make game fill whole screen.

Make the froggy cube move on arrow button.

every other log should move in opposite directions across the x-axis of the canvas.

enter from both sides of the screen?

frog, car, log are each subclasses.

Only one frog. Not scalable.

Frog1

Indicate When the game is over, won, or lost.

Build our first gamepiece class.

need another condition?

low priority

The frogs x.value increases at twice the rate when it lands on stacked logs.

15 rows:
row 1: (at the top) score and lives
row 2: safe area for frogs, win condition
row 3: logs
row 4: turtles (in a perfect world)
row 5: logs
row 6: turtles (same)
row 7: logs
row 8: safe row
row 9: cars
row 10: cars
row 11: cars
row 12: cars
row 13: cars
row 14: safe area
row 15: timer

cars should get more frequent, logs less frequent. ideally this would happen each time a player lands a frog in the end row.

frog needs to stand on obstacle and travel with it. start with only logs, then look at making the logs dip under the surface of the moat, then look at turtles and/or crocodiles

in the regular game, the frog scores when it advances to the next row, but not when back tracking.

Allow the user to start a new game.

need to build a function that checks for a game state to be true or false. For one, the game continues--for the other, the game animation stops. This is also how lives can be instated.

Add a second class or a subclass.

Redundant.

Too hard to see.

Get a block on the screen.

Can cause memory leak. Use let or const instead of var. "Garbage collecting". Global can slow things down.

To make space for levels and lives potentially.

cars should stay in lanes, logs in moat

Turn if statement in frog.js file into a switch.

"Game" instantiates on click

safe spaces at the end of the game board. frog should stay on the safe space and a new frog should start back at the beginning. (a new Game state).

collision with the moat causes death of the frog. moat should persist.

Add some color to the game.

bottom border should not allow the frog travel below. in the water area, going off of the edge of the game board should kill the frog.

Three lives then game over

car colliding with frog = death; frog colliding with car = death; frog colliding with moat = death--

frog colliding with crocodile = death.

Edgar finished - start game over or return to "click" screen?

Get an empty canvas on the screen.