Game mode implementation #2
Description
from barry:
If you get hit, the rover does almost a complete 360 spin in place before being able to move again
There's a been_hit() function that controls what happens when you are hit... we may want different implementations depending on the game mode... someone want to look into that?
Could use help either making an easy way to swap out implementations based on some global game mode variable or just coding other fun things to happen when you get hit.
bb notes:
here are the modes we discussed before:
Mode Descriptions:
Hungry Games
In this thrilling every-shark-for-themselves mode, all players start with a cool blue glow. But beware! One wrong move and you'll be tagged, triggering a dramatic stop-motion freeze as your lights turn a menacing red. You're out of the game, but the action continues! The last shark swimming with their blue light shining emerges as the ultimate predator.
Sharkbyte
A contagious frenzy takes over the arena! One player starts infected with the Sharkbyte virus, glowing a sickly green. Their mission? Spread the infection! Every shark they tag joins the horde, turning green and helping to spread the virus. Uninfected players (glowing blue) must use their agility and cunning to avoid the infected and survive until the timer runs out.
Optional Twist: To increase the challenge, infected players could be slowed down, making it harder for them to catch their prey and spread the virus. This adds an extra layer of strategy and suspense to the game!
Saturday Bite Fever
Get ready to boogie! In this high-energy mode, getting tagged triggers a dazzling disco fever. Your shark will go into a spinning frenzy while your RGB lights erupt in a vibrant rave show. It's a party in the laser tag arena, even if you're temporarily out of the action. This mode adds a fun and exciting element to the game, encouraging players to embrace the chaos and enjoy the light show!