Ideas to thwart commander eject griefing
ChitownFreeze
Join Date: 2008-03-29 Member: 63994Members, Constellation
Join Date: 2008-03-29 Member: 63994Members, Constellation
<div class="IPBDescription">Server admins please read!</div>Lately there has been a rash of griefing occurring on pub servers where at least two people (apparently buddies) join the same team and then immediately kick out whoever tries to become the commander. This happened to me on at least three servers last night. I jumped into the chair one game and was immediately ejected, before the command chair had even closed fully. It even happened on a clan server with admins present, and the admins were unable to determine who to kick/ban because there was no notice given as to who did the voting. They had to assume it was the most recent two people to join, since up to that point there wasn't any problem.
The LUA server-side script VoteManager.lua provides two variables that control ejection conditions:
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// Commander ejection
VoteManager.kMinVotesNeeded = 2
VoteManager.kTeamVotePercentage = .3<!--c2--></div><!--ec2-->
There is one major flaw with this scheme, and it is this: with the default settings requiring only two minimum votes needed and a 0.3 percentage, it only takes two idiots on a team with six or fewer players to render that game completely unplayable. These bobble-headed twats will just eject anyone and everyone who attempts to command. This flaw is most apparent at the very start of a new map when there tends to be only a handful of players who have even joined a team due to the large difference in load times amongst players.
Imagine a scenario where two of these idiots running fast computers manage to join the same team before the bulk of the players have even entered the ready room. Until there are more than six players on the team, they will be able to grief at will with no consequences, since there's no notification that someone has even voted. This problem is magnified on servers that might not be full 100% of the time, and even worse on servers with 12 player limits, since even if the server is completely full those two twats will always be able to eject if they are on the same team.
It seems to me that there are a few things that can be done to help alleviate this problem:
<ul><li>First and foremost, there should be an option in the LUA script to enable team-wide notification of who has voted to eject the commander. That is, display a message to all players that an eject vote has been started. This will fix the problem with griefers going undetected on servers with admins present, since it will be quite obvious who the griefers are when they instantly vote to eject anyone who jumps in.</li><li>Bump up the vote percentage to 0.41, which will prevent two people from griefing on teams with more than four players.</li><li>Add a variable to limit the number of times a person can initiate the vote during any given round. That is, be the first person to vote to eject when a commander jumps into the chair. They can always vote to eject if someone else has initiated it, which would mean that two griefers could only eject a total of two times (assuming the variable is set to 1). A value of 0 could mean no limit, if admins chose not to use that feature. This would be useful to thwart two griefers on the same team; if there are more than two, the team might as well be considered doomed.</li></ul>
Of these, I think the first would be most useful, assuming the server has some active admins on it. Then at least the griefers could be banned for a period of time, assuming there's a way to ban for 30 minutes or something? Maybe there are other ideas that could also be implemented. Just wanted to at least get a discussion going. Having active admins on servers would be exceptionally useful.
The LUA server-side script VoteManager.lua provides two variables that control ejection conditions:
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->// Commander ejection
VoteManager.kMinVotesNeeded = 2
VoteManager.kTeamVotePercentage = .3<!--c2--></div><!--ec2-->
There is one major flaw with this scheme, and it is this: with the default settings requiring only two minimum votes needed and a 0.3 percentage, it only takes two idiots on a team with six or fewer players to render that game completely unplayable. These bobble-headed twats will just eject anyone and everyone who attempts to command. This flaw is most apparent at the very start of a new map when there tends to be only a handful of players who have even joined a team due to the large difference in load times amongst players.
Imagine a scenario where two of these idiots running fast computers manage to join the same team before the bulk of the players have even entered the ready room. Until there are more than six players on the team, they will be able to grief at will with no consequences, since there's no notification that someone has even voted. This problem is magnified on servers that might not be full 100% of the time, and even worse on servers with 12 player limits, since even if the server is completely full those two twats will always be able to eject if they are on the same team.
It seems to me that there are a few things that can be done to help alleviate this problem:
<ul><li>First and foremost, there should be an option in the LUA script to enable team-wide notification of who has voted to eject the commander. That is, display a message to all players that an eject vote has been started. This will fix the problem with griefers going undetected on servers with admins present, since it will be quite obvious who the griefers are when they instantly vote to eject anyone who jumps in.</li><li>Bump up the vote percentage to 0.41, which will prevent two people from griefing on teams with more than four players.</li><li>Add a variable to limit the number of times a person can initiate the vote during any given round. That is, be the first person to vote to eject when a commander jumps into the chair. They can always vote to eject if someone else has initiated it, which would mean that two griefers could only eject a total of two times (assuming the variable is set to 1). A value of 0 could mean no limit, if admins chose not to use that feature. This would be useful to thwart two griefers on the same team; if there are more than two, the team might as well be considered doomed.</li></ul>
Of these, I think the first would be most useful, assuming the server has some active admins on it. Then at least the griefers could be banned for a period of time, assuming there's a way to ban for 30 minutes or something? Maybe there are other ideas that could also be implemented. Just wanted to at least get a discussion going. Having active admins on servers would be exceptionally useful.
Comments