This suggestion is ONLY intended for Speed Builders and Build Battle, not other games. This is not intended to be implemented into any other game on The Hive.
TL;DR:
People leaving early means less exp in a game that gives little exp. A temp. ban for people who requeue after the game has started (1-3 minute ban) should fix this. It will not go up in time the more times somebody requeues. Also, people who decide they want to play another game beforehand aren’t caught in the crossfire.
People leaving early in speed builders and build battle matter a lot. With how sparse exp is, this is a big problem for people trying to level up. Sweats will tryhard right off the bat and half the lobby will leave. Since you can’t be banned for tryharding (Unfortunately), let’s tackle those leaving early. There should be a temp. ban for requeueing when in the game. Probably 1-3 minutes. It would not increase in time no matter how many infractions. This is because the people doing this are kids who know they don’t stand a chance, so increasing the punishment would only frustrate them more and cause them to stop playing instead of the desired effect.
A crucial thing to note is this would only affect you after game has started. If you’re still waiting in the lobby for the game to start, you’re free to requeue. I take issue with people leaving when the game has started, and people who decide they don’t want to play BB or SB anymore whilst in the lobby won’t be punished for it.
Maybe this could take place in the form of some kind of limit to requeueing - maybe 5 requeues in an hour leads to a 10 minute ban only from the mode you requeued out of, with the duration increasing with multiple infractions
Getting timed out from the server wouldn’t get you banned. Alternatively, don’t play another round if you know you have to go somewhere. If you have to go away for a few minutes, there’s no afk kick so you’ll be fine.
For the lag, watch the game or do something outside of the game in the meantime. Alternatively, the code for this would check if you were teleported to your starting location for the game, and if you weren’t then it wouldn’t issue a ban if you tried to requeue or go to the hub. I’m assuming your talking about the nether glitch here, and that check would happen right after everybody is tp’d.
If a device crashes when loading into a game several times in a row, then you just need to stop trying to play on servers since it’s not going to be playable.
That’s fine and all, but people could work around that easily by hopscotching between the two gamemodes, assuming the idea is mode selective. A way to fix it could be to have the server log how many req’s for that game mode on a streak regardless of if they detour and go to other games. Basically, this is just an example, if I req SB 5 times, then hop over to MM for a bit, then req SB mid game AGAIN, then it would count that as 6 and give the infraction. If you were implying that, then mb, it’s like 1 am rn lol
The only issue is it’s hard to tell the difference between someone that requeues in 2mins by exiting the server and coming back with someone that genuinely lagged out and requeues.
Probably one of the most absurd things I’ve heard.
Ok anyways, I think this makes since espescially with how the do works. And yes it’s only for people req, so not leaving or smth else. So yeah i like this. Voted.
