i personally think 10 mins would be perfect, 30 is def wayy too long given how fast a match can become unenjoyable on the server. 15 is also a tad bit too long i feel but acceptable. either way i think 10-15 mins would be perfect
 
Vote scramble behaves differently than other votes. Like a mute, it affects more than one person. (To ignore one person, use the ignore command; to punish one person, call a vote mute.) So, going forward with the mindset that it affects everyone on the server, not just the people causing the issue....

In practice, a vote scramble, often doesn’t even fix an imbalance. Sometimes it makes it worse. This often gets called out in chat following such a vote passing. What I see more often is it being called repeatedly, not to solve a real problem, but as spam or frustration. That alone is a strong case for some kind of cooldown.

There’s also the issue of it being weaponized. I’ve personally seen it used to end player streaks or disrupt momentum rather than genuinely balance teams. That’s understandable to some extent—some people don’t like getting rolled—but it still means the system is being used for targeted disruption rather than its intended purpose.

At the same time, one-sided matches don’t last forever by their nature, and some players actually enjoy them. So constantly forcing scrambles can take away from that experience too.

A cooldown helps address the spam and abuse side of things, but I think it should be implemented with some nuance:
  • If a scramble passes, a longer cooldown (around 30 minutes) makes sense.
  • If a scramble fails, a shorter cooldown (maybe ~15 minutes) would be more reasonable.
Treating those two cases differently would prevent spam while still allowing players to respond if conditions actually change.

Separately, there are other levers worth considering:
  • Adjusting scramble to be pseudo-random instead of fully random (more balanced if it account for things like K/D, etc.)
  • Increasing the vote percentage required (45% instead of 40%)
Overall, I don’t think cooldown alone fixes everything, but it’s a necessary step to reduce spam, prevent abuse, and make the system feel more intentional rather than reactive.
 
Ah yes one of the salty players that always votescrambles. Please continue to think this post is about me and ignore the 100s of posts complaining about vote scramble trolling. You don’t have any input on why this would be a good or bad implementation? Do you think a 15 minute time limit on vote scramble is a good idea?Or did you just need to express your frustration that you get farmed?
 
  • Like
Reactions: dunetoa2
What might be a better suggestion, in my opinion, and I've been thinking of putting this in, is to suggest a better scramble mechanism. or some kind of mechanism to ensure that people don't intentionally stack teams after a scramble . I don't think the current vote scramble works well in 2fort 64.

The reason the many scrambles are happening is more likely to be because the teams are often extremely unbalanced.
 
  • Like
Reactions: raVen52
What might be a better suggestion, in my opinion, and I've been thinking of putting this in, is to suggest a better scramble mechanism. or some kind of mechanism to ensure that people don't intentionally stack teams after a scramble . I don't think the current vote scramble works well in 2fort 64.

The reason the many scrambles are happening is more likely to be because the teams are often extremely unbalanced.
I proposed two such mechanisms related to vote scrambles already. Did you have any you wanted to contribute or comment on what was already proposed?
 
  • Like
Reactions: dunetoa2
This reads as pub stomper wants to stop scrambles, so they can stomp longer
Do you think 15 minutes is a long time for a 64 player 2fort game? Or would you rather to scramble every 5 minutes? Team stacking will always be a thing. There is no way to moderate it at all without ruining how community servers are played. If you read any of the vote abuse reports, its all the same people that just votescramble to troll. Votescramble or not whatever team im on is always referred to the "unbalanced team". Are we so out of touch with a solution where we think that a 15 minute time limit isn't a reasonable amount of time for the next scramble? People can't push or fight for control of Mid/Sewers in 5 minutes.
 
I proposed two such mechanisms related to vote scrambles already. Did you have any you wanted to contribute or comment on what was already proposed?
Ok

Vote scramble behaves differently than other votes. Like a mute, it affects more than one person. (To ignore one person, use the ignore command; to punish one person, call a vote mute.) So, going forward with the mindset that it affects everyone on the server, not just the people causing the issue....
Agreed

There’s also the issue of it being weaponized. I’ve personally seen it used to end player streaks or disrupt momentum rather than genuinely balance teams. That’s understandable to some extent—some people don’t like getting rolled—but it still means the system is being used for targeted disruption rather than its intended purpose.
You're sure that it's trolling / weaponization? Very rarely do I see votescramble votes go through when the map wasn't deadlocked and one team was being wrecked. I'm sure it happens, but it's a leap to say that it's specifically being used to end a players streak and/or disrupt momentum, you don't have evidence for that.
At the same time, one-sided matches don’t last forever by their nature, and some players actually enjoy them. So constantly forcing scrambles can take away from that experience too.
Team unbalanced 64 player small maps with tight choke points reduces the number of classes that are able to be effective. One-sided matches often last hours, which can be an entire person's time to play. On the flip side, playing on the winning/overly strong team can be boring.
A cooldown helps address the spam and abuse side of things, but I think it should be implemented with some nuance:
  • If a scramble passes, a longer cooldown (around 30 minutes) makes sense.
  • If a scramble fails, a shorter cooldown (maybe ~15 minutes) would be more reasonable.
Maps often get unbalanced within 5 minutes of a scramble and return to the same exact state, sometimes with teams flipping as well.I don't think either of these solve the problem, that team scramble algorithm often doesn't work. If team scramble algorithm were fair and balanced, this would be supportable.

Separately, there are other levers worth considering:
  • Adjusting scramble to be pseudo-random instead of fully random (more balanced if it account for things like K/D, etc.)
  • Increasing the vote percentage required (45% instead of 40%)
Overall, I don’t think cooldown alone fixes everything, but it’s a necessary step to reduce spam, prevent abuse, and make the system feel more intentional rather than reactive.
How is scramble calculated? Is it random? I may have been under the wrong impression that scrambles were not 100% random. Increasing to 45% to 40% also seems fine to me.
Do you think 15 minutes is a long time for a 64 player 2fort game? Or would you rather to scramble every 5 minutes? Team stacking will always be a thing. There is no way to moderate it at all without ruining how community servers are played. If you read any of the vote abuse reports, its all the same people that just votescramble to troll. Votescramble or not whatever team im on is always referred to the "unbalanced team". Are we so out of touch with a solution where we think that a 15 minute time limit isn't a reasonable amount of time for the next scramble? People can't push or fight for control of Mid/Sewers in 5 minutes.

Well your suggestion was a 15 minute long wait after any vote scramble pass or fail. I think having a longer timer after a passed scramble is reasonable.
 
To add another thing here -

I think this wasn't an issue when it was a 32 person map. Making this a 64 person map changes the nature of the game entirely, and new considerations should be made.

I don't think this map was designed to handle 64 people, and is structurally unbalanced.

Is this even an issue on other maps that are not 64 2fort? I don't think I see people vote scramble on any other maps really ever.
 
+1

I like eeymonts suggestions for the most part.
Personally, if 2 or 3 scrambles happen close to one another I just leave the server and play something else. It's very annoying to set up a nest or take over a part of the map only to have everything reset multiple times.
I also see it called quite often simply to troll.
 
  • Like
Reactions: dunetoa2 and Lazurs
Well your suggestion was a 15 minute long wait after any vote scramble pass or fail. I think having a longer timer after a passed scramble is reasonable.
Wtf are you arguing then? A time limit is needed after a passed scramble. Thats it
 
  • Like
Reactions: dunetoa2
Vote scramble behaves differently than other votes. Like a mute, it affects more than one person. (To ignore one person, use the ignore command; to punish one person, call a vote mute.) So, going forward with the mindset that it affects everyone on the server, not just the people causing the issue....

In practice, a vote scramble, often doesn’t even fix an imbalance. Sometimes it makes it worse. This often gets called out in chat following such a vote passing. What I see more often is it being called repeatedly, not to solve a real problem, but as spam or frustration. That alone is a strong case for some kind of cooldown.

There’s also the issue of it being weaponized. I’ve personally seen it used to end player streaks or disrupt momentum rather than genuinely balance teams. That’s understandable to some extent—some people don’t like getting rolled—but it still means the system is being used for targeted disruption rather than its intended purpose.

At the same time, one-sided matches don’t last forever by their nature, and some players actually enjoy them. So constantly forcing scrambles can take away from that experience too.

A cooldown helps address the spam and abuse side of things, but I think it should be implemented with some nuance:
  • If a scramble passes, a longer cooldown (around 30 minutes) makes sense.
  • If a scramble fails, a shorter cooldown (maybe ~15 minutes) would be more reasonable.
Treating those two cases differently would prevent spam while still allowing players to respond if conditions actually change.

Separately, there are other levers worth considering:
  • Adjusting scramble to be pseudo-random instead of fully random (more balanced if it account for things like K/D, etc.)
  • Increasing the vote percentage required (45% instead of 40%)
Overall, I don’t think cooldown alone fixes everything, but it’s a necessary step to reduce spam, prevent abuse, and make the system feel more intentional rather than reactive.
You are the only one with my approval, Seren. Im not surprised, knowing you for a long time, smart. But I'd like to add one last thing: I'd say more like 50-55% than 45%. Because we often have to remember that people don't even look at what they're voting for. That's a fact.

And this will balance things out a bit more when you see that a much higher percentage is needed for others (like the kick: 90%. Even if its just for one person, The percentages are not all fair, we must acknowledge that).
 
Currently the cooldown is tied to all votes cooldown meaning it can be spammed several times in the first 15 minutes, which is kind of an oversight already and makes no sense. When multiple people do this it's even worse. And it's been happening often

I don't like people calling scramble solely to ruin killstreaks and while it's been mutable for a while now the overall scramble cooldown should be set to no lower than 15 minutes. Encouraging people to save the scramble for when it's actually needed
 
I was surprised enough that the scramble % to pass went to 50 instead of 40, that I like.

What I don't like is people scrambling the teams for shits and giggles. It's unpredictable when it gets called and there are even some that will call it to ruin some killstreaks as Gala mentioned. To add on, usually scrambling doesn't do a whole lot anyways because people will still stack the teams, engi nests are still existing on bridge/intel/sewer, and it's 64 player 2Fort/Turbine.

Between the pub stompers and the people who play casually, you're not going to get a clear answer of what should actually be done.