Short disclaimer before going off into the sunset on fixing the issue.

I'll admit it is far too easy and there needs to be some 'challenge' added for it to happen. Over time though corps will eventually burn all the alts out of the corp so this problem might die down or be reasonably managed within the coming weeks well before CCP pushes out a Sony patch to fix it.

/kick or /votekick option would result in well... lets say far more drama and actual 'real grief' than Awoxing itself.

Example 1 of why kick is bad.
Timmy wanted to enjoy PC for the first time, he is rather fresh and nobody else was available to help fight at the minute the battle started. Timmy we come to find out is far better than originally though far better than the guy he is filling in for. Johnny logs on a minute late to the fight and see that Timmy took his spot. Johnny /kicks Timmy right in the middle of a what would have been a game winning hack and costs the corporation the planet. Johnny would have got fired but he's the CEO and blames Timmy for the loss and kicks him from the corp for something not his fault.

Example 2 of why kick is bad.
Floyd is a spy, he got the role to kick people from a corp match. The corp all goes into a battle and Floyd being very sneaky invites his not so friendly friends and makes them squad leader, and then kicks everyone that isn't his friends out. End Result nobody suspects Floyd because Floyd isn't in the fight and there is not a single friendly on the field. The one sided match does into a grand Mario Kart Race.

TL:DR
Barring the /kick option. What other 'out of the box' solutions would you have? Role? Other Mechanics? Corp Tools? Flagging?

Anyways the floor is yours guys and gals; have at it.

It sounds to me like Floyd has played his cards right and is benefiting from worming his way into a position of trust. Also, why would there not be a notification of who has kicked a player (like most other AAA games)? The spy does his damage in a blatant way, burns his cover but potentially has a decisive effect on the corp battle.

How about this?

Battle Commander - Can kick anyone.
Squad Leader - Can kick anyone in his squad.

If the Battle Commander is a spy, game over and rightly so. This person has played the metagame like wormtongue/littlefinger and is reaping the reward by throwing the match irrevocably.
If the Squad Leader is a spy he can start kicking members of his squad or replacing them at a critical moment in the game. He will be removed by the Battle Commander but the damage he does has a good chance of losing the battle for his host corp.

Minor issue is the password protection on channels is broke again it seems. They had fixed it a while back but it seems to be popping up again


Basically if a Dust created channel is put under PW protection one could enter the name of the chat and reset the client and you would be in the channel. While this mechanic being suggested is different it something that could end up failing or be bypassed, IE try to enter battle and get PW screen, reset client and potentailly have access to the match(granted given the need for reset likely the team will have successfully filled in by the time you relog so perhaps its moot, just playing devil's advocate).

Currently Awoxing doesn't guarantee wins though there was a few corps yesterday bragging about foiling evil plans of betamax infiltration.

or the guys you infiltrated into the battle where the bottom of the merc marketplace.

I won't know until I ask either. Passwords are 'feasible' but the hardest of the options right now.

That was kind of the point of this thread.

To lay out options and then get CCP's input on what is possible to get out in a matter of days or weeks, without waiting months for an expansion.


Ironwolf is just not very good at creating threads like this yet :P

Okay I understand then.

I'm not sure how long another solution is away, but I prefer the toggle idea that you can choose to allow only Corp members into PC battles, or open it. It seems simpler than the password to implement, and I don't feel the Corp communication tools are adequate to make the password idea work without a lot of frustration at the moment.

Probably the easiest to implement idea I had was to make a Market item that was a "PC pass", ensuring that players have enough SP to obtain it, as a barrier to newly created alts being spies. This makes spies have to work harder on the character in order to sabotage someone, and this would create a barrier to people being unattached to that character since they will have had to play it long enough to get there. I would bury it into the skill tree, behind a core skill, and make people aware of it. This is probably one of the more contentious ideas.

ie. requiring engineering and others to be at skill 1 before it can be obtained.

Passwords could be exploited to bring in a squad of alts yes, but a PC Pass would not. Every alt would need a PC Pass, not just squad leaders.

I think we need to get through to a more permanent solution, so having an SP requirement would be simple to implement, and buy a couple of months while they get the roles sorted out.

There's rarely a case when 'the majority' of the community wants anything. In this case, the majority of the community realizes that awoxing is too easy, but to say that the majority agreed on any short term solution is completely false. One can easily selectively read and say "But there is so many posts saying people want X" but the truth is that almost every suggestion in favor of something had an equal (or almost equal) amount of people saying "But X is bad". In the long term, most people can agree that giving corps proper management tools (Whatever those tools may be) is the optimal solution, and it is. This thread was not about the long term, though. It was about finding something CCP can do -now- (If anything needed to be done at all)

In cases like this, it really doesn't matter what option the CPM likes most. Our job isn't to pick what CCP does. It's to make sure they know the benefits and harm each option can cause and leave it to them to do whatever solution is 'right'.