Ner'Zul Nexhawk
Seraphim Auxiliaries CRONOS.
237
|
Posted - 2013.05.21 14:41:00 -
[1] - Quote
Natu Nobilis wrote:Before battle:
1 - If you-Śre in a player corporation, you answer to people with functions / roles.
2 - One of this functions/roles, should be the one of designating people to battle on the corporations behalf.
3 - Be it assigning a squad leader and letting him choose his team, or handpicking the entire team themselves.
4 - Any resposability of bad picking lies with the person responsible for the battle designations.
During battle:
1 - Implement a "Prevent spawn" similar to the flag already in place that is used when a team is out of clones to respawn.
2 - An active awoxer remains active until death.
3 - Awoxer cannot respawn at that battle, but still takes a slot, damaging the team.
This way you can awox, you can damage the team, and you have a PERSON that is responsible for anything that happens with the team.
If an awoxer got in, blame your HR responsible, fire him or have proper selection next time.
Definitely this.
I am firmly against kicking AWOXers from the match altogether. What I am in favor of, however, is kicking them from the team.
So here are my 2 ISK on the issue.
Whenever you are TKed, you have the option to initiate the "Suspect" vote on the player that killed you. A small window appears on the top left corner of the screen of every team member except for the killer, prompting them to either "Approve" (arrow up) or "Deny" (arrow down). Once a set number of votes in favor has been casted (probably half of the team, since the TKer doesn't vote), the AWOXer now has a "Suspect" flag on him. What that means is that he will be marked yellow for the remainder of his team, allowing them to kill him without losing WP. He will be also restricted access to the team's clone vats, practically putting him into "hardcore" mode with one life. Upon death he, as it was suggested previously, will be able to ask the opposite team to accept him in, and a vote similar to "Suspect" would be performed to accept or reject his request.
In the case where the enemy team doesn't accept the betrayer, his clone would remain on the ground for an extended period of time. During this time, if the AWOXer has a buddy that didn't yet reveal himself or wasn't killed as a Suspect, the latter can revive the fallen AWOXer silently and let him continue on his rampage. Note that the location of the downed Suspect should be shown to every merc in the battle with a nanite injector as the yellow NI sign to indicate that this is not simply a team member calling for help.
Squad leaders should also have a "Suspect" option on their command wheel; this option would initiate the vote as well. This command would be useful when you see a person sabotaging your team but not by means of TKing anyone (for example, he still shoots his teammates, but only brings them to low health for the enemy to finish).
I definitely agree with the suggestions of the corp roles, but I believe that the method described above will help when there are no people with sufficient rights present at the time of battle. That would especially work out better for small corps where directors and CEOs are not always online and can't decide who will go into the battles.
|
Ner'Zul Nexhawk
Seraphim Auxiliaries CRONOS.
237
|
Posted - 2013.05.21 16:32:00 -
[2] - Quote
The password is an excellent idea. But what are you going to do once the person got access to the password and got into the match? I'll post my opinion on that again, and I realize that it is a long-term solution, but lore-wise something like that has to be implemented, as I think.
Ner'Zul Nexhawk wrote:
I am firmly against kicking AWOXers from the match altogether. What I am in favor of, however, is kicking them from the team.
So here are my 2 ISK on the issue.
Whenever you are TKed, you have the option to initiate the "Suspect" vote on the player that killed you. A small window appears on the top left corner of the screen of every team member except for the killer, prompting them to either "Approve" (arrow up) or "Deny" (arrow down). Once a set number of votes in favor has been casted (probably half of the team, since the TKer doesn't vote), the AWOXer now has a "Suspect" flag on him. What that means is that he will be marked yellow for the remainder of his team, allowing them to kill him without losing WP. He will be also restricted access to the team's clone vats, practically putting him into "hardcore" mode with one life. Upon death he, as it was suggested previously, will be able to ask the opposite team to accept him in, and a vote similar to "Suspect" would be performed to accept or reject his request.
In the case where the enemy team doesn't accept the betrayer, his clone would remain on the ground for an extended period of time. During this time, if the AWOXer has a buddy that didn't yet reveal himself or wasn't killed as a Suspect, the latter can revive the fallen AWOXer silently and let him continue on his rampage. Note that the location of the downed Suspect should be shown to every merc in the battle with a nanite injector as the yellow NI sign to indicate that this is not simply a team member calling for help.
Squad leaders should also have a "Suspect" option on their command wheel; this option would initiate the vote as well. This command would be useful when you see a person sabotaging your team but not by means of TKing anyone (for example, he still shoots his teammates, but only brings them to low health for the enemy to finish).
I definitely agree with the suggestions of the corp roles, but I believe that the method described above will help when there are no people with sufficient rights present at the time of battle. That would especially work out better for small corps where directors and CEOs are not always online and can't decide who will go into the battles.
|