Open kiki-lee opened 2 years ago
This is a candidate for extension.
Agreed, though, there's some stuff linked to internal piping. I have this (And the new countdown game over) in extensions right now, but there's a lot of duplicate code, due to the unpacking of the layer stacks that has to happen.
At the moment, we only have 2 game over options: 1) Game Over Loss
2) Game Over Win
These leave out some common game options:
A) Game Over Notification - Neither a loss, nor a win…just a notification that the game has finished and you have the score you have (Useful for clicker games or games where the goal is to see how many points you get before you die)
B) Game Over Time Elapsed - Neither a loss, nor a win, but you managed to stay alive for X amount of time (high) or you completed in a record of X time (low)
C) Game Over Player X Wins - Win state, but not showcasing the "score" variable. Instead, showcasing the largest of the player scores and declaring that player a winner
Current State
As near as I can figure, none of these are possible given what we have now unless we want to do some logic checking on game update and quickly swap time/player scores to the
score
variable before throwing the game over screen?First Step
We'll use the heck out of these for carnival games, so if they can't go in the Games category right away, I'm fine adding them to the Carnival extension for Hour of Code.