Quote:<div>
i'm confused why there is so much text in this thread... (so i guess i'll be hypocritical and add some more)
correct me if i'm wrong, but there are still two 4v4 arenas types, 4v4prac# which does not have !forcecap and 4v4squad# which does (b/c its premised as a squad vs. squad arena). so if you are concerned with or do not like the use of !forcecap, go to 4v4prac# and wait until there are enough like-minded people there to play. if the majority of people choose to patronize 4v4squad#, and you cannot get sufficient interest in 4v4prac#, then people have in effect voted for the use of !forcecap and you are in the minority and at some point you are going to have to accept and deal with that. that is, it would be a bit ludicrous to expect the majority to bend over backwards to cater to your minority view and whining on an online forum is unlikely to change that, but feel free to try.
so you have three options:
1) recruit more people to play in 4v4prac# arenas.
2) get better (socially, skill-wise, etc.), so that you aren't considered a nuisance, liability, and/or "unpickable."
note: this game isn't hard, most anyone with decent resolution who isn't spastic should be able to become competent and "pickable"
3) find another game.
note: majority rule is common in most online communities, and if you find it objectionable here, i'm afraid you're likely to find it objectionable elsewhere as well.
ps: what about first to 12? is that still an option? would seem to minimize the major issue of playing a man down when newbs (or drunk vets) die out.
</div>
4) Change how the bots work so that the abuse of !forcecap is minimized
...
The suggestion to migrate people over to 4v4prac is ridiculous. Here is why:
SuckyDude gets in !cap line in 4v4squad. No one knows who he is, or he is known to suck, or is just a jerk. There are 5 others behind him in line that are all average, known players. TeamStack has just won. SuckyDude gets !cap. TeamStack decides to !fc the next guy in line, or whoever else they want. SuckyDude has to wait 10-30 mins for each game, thinking he gets next, to be !fc'd over because no one wants to play against him or the winning cap is just a troll.
So, SuckyDude decides to go to prac arena and !spam. He is an unknown and maybe 2 people come to see what happens and maybe join. In the meantime, the other arena has 5 people still waiting behind him in line who are willing to play in that 4v4squad because there is a 99% chance that !fc won't be an issue with them. They aren't squads, it's TeamStack vs TeamNextRandom and no one will leave to join SuckyDude willingly with a live line in progress in 4v4squad.
!fc works great when there are issues with captains that AFK while holding it. Or AFK and !away claim. Or, or... there are valid uses. And so having !fc is the better option when comparing 4v4prac vs 4v4squad. Realistically, no one actually cares about 4v4squad vs 4v4prac. The people saying it means something are spewing out a line of crap of how it's supposed to work, or what was in mind when it was implemented this way. But it's ultimately a load of shit. They should be the same, and in effect on a daily basis, they are.
All this boils back to letting the winners abuse the rest of the arena, and the people in line that they don't like. That's what 99% of the complaints here actually are. A tool for trolling has been given to the players, and those who choose to abuse it will do so whenever they see fit.
Fix the tool. Change how often is can be used by adding a timer. Maybe check for valid squads so that it can only be used for a winning squad to !fc another squad (they can make a private freq and the bot can look at it and check the 4 players and their squad and then activate everything). Or look at my previous post in this thread that elaborates and provides some other ideas for using it and enhancing 4v4.
Leave it open for trolls to abuse it, and they will. This issue will never go away in it's current state and it will continue to drive the newer people away from league. Ask for attrition and ye shall receive.