Most Mini Games on LVP have the same boundaries and rules. Yet, most of them use their own handler and have no communication between each one. We need to centralize Mini Games to one handler. This will improve the process, syntax, and organisation. We'll have to split it into parts:
Core
Handle signups, signouts, position saving / restore, join/leave commands and other flags to determine the player is in a minigame, and what minigame name and type it is (MINIGAME_TYPE_DM, MINIGAME_TYPE_RACE, MINIGAME_TYPE_DERBY, MINIGAME_TYPE_TEAM)
Deathmatch -> LVP Fight Games
Deathmatch is one word we can use to describe minigames like /rocket /sniper, and whatever else uses that shitty handler. But that may cause confusion when it comes to describing minigames like lyse and that walk weapon Matthias just wrote. We'll call these LVP Fight Games. This part of the handler should work just like the current one. Parent Player starts the minigame, signup process begins, it starts after 20 seconds. It should be nice and dynamic - You can add minigames with function calls like the current race and derby handlers. Below is a list of minigames which should use this part of the handler. Minigames marked with a star* are unpopular and will need some changes done to make them more interesting:
Batfight*
Chainsaw*
Dildo Spanking*
Knockout*
Grenade
Minigun
Random
Rocket
Sawnoff
ShipTDM
Sniper
WalkWeapon
Next to that, textdraws should be in place to show various statistics of the minigame (like race): The players position, how long is left (if applicable), and how many people have signed up.
Team -> LVP Games
There isn't a general name for the likes of Lyse, Rivershell, etc. I reckon we should call these LVP Games. Ths part of the handler is going to be tricky because each of these minigames have different indivdual elements boundaries and rules. For the sake of ease, there shouldn't be much to this part of what the core doesn't already offer.
Races & Derbies
Unlike LVP Fight Games, Derbies and Races have quite a lot going on and quite a few processes and calculations are constantly in place. Perhaps this part of the handler should just again just use the core.
Thoughts?
Core
Handle signups, signouts, position saving / restore, join/leave commands and other flags to determine the player is in a minigame, and what minigame name and type it is (MINIGAME_TYPE_DM, MINIGAME_TYPE_RACE, MINIGAME_TYPE_DERBY, MINIGAME_TYPE_TEAM)
Deathmatch -> LVP Fight Games
Deathmatch is one word we can use to describe minigames like /rocket /sniper, and whatever else uses that shitty handler. But that may cause confusion when it comes to describing minigames like lyse and that walk weapon Matthias just wrote. We'll call these LVP Fight Games. This part of the handler should work just like the current one. Parent Player starts the minigame, signup process begins, it starts after 20 seconds. It should be nice and dynamic - You can add minigames with function calls like the current race and derby handlers. Below is a list of minigames which should use this part of the handler. Minigames marked with a star* are unpopular and will need some changes done to make them more interesting:
Batfight*
Chainsaw*
Dildo Spanking*
Knockout*
Grenade
Minigun
Random
Rocket
Sawnoff
ShipTDM
Sniper
WalkWeapon
Next to that, textdraws should be in place to show various statistics of the minigame (like race): The players position, how long is left (if applicable), and how many people have signed up.
Team -> LVP Games
There isn't a general name for the likes of Lyse, Rivershell, etc. I reckon we should call these LVP Games. Ths part of the handler is going to be tricky because each of these minigames have different indivdual elements boundaries and rules. For the sake of ease, there shouldn't be much to this part of what the core doesn't already offer.
Races & Derbies
Unlike LVP Fight Games, Derbies and Races have quite a lot going on and quite a few processes and calculations are constantly in place. Perhaps this part of the handler should just again just use the core.
Thoughts?
