Player Features and Ideas Discussion

Sounds reasonable though if you have these types of problems, you need to keep a closer eye on your members. Also, that doesn't constitute piracy. That falls under the espionage category.

Get a PvP ship and blow the offender out of the water space. Stop trying to get NPCs to do your job for you!

Security is an ongoing issue in any corp. You can't check an API key and be done with it. I admit I know nothing about the particular situation you describe, but my experience with these types of things is there are generally some warning signs. I've seen it done in retribution for slights from the senior leadership from otherwise very honest players (pirates are often honest btw, piracy and dishonesty are in no way linked). More often though, it's from guys who have zero respect for other players and can't think 5 second ahead of them. Those types are fairly common and just about any real corp will eventually find one in their midst. I wouldn't boot them over a gut feeling, but I do recommend keeping a close eye on them. It all comes down to knowing your corp members really. There just isn't any substitute for chatting with them casually.

Anyways, I still support your proposal since it's reasonable.

If you don't want to consent to PvP, don't undock.

I don't muck around on the test servers much. When I test set ups and train for PVP I do it live. Without the lack of interference of CONCORD with internal disputes, I'd be forced to the test server. That's a huge hassle to deal with a problem I've never experienced first hand.

"Never trust anyone you can't punch in the face"

My first CEO ever told me that. I've lived by that. And I haven't had any problems at all.

I feel Awoxing is a valid gameplay tactic.


Let the teamkilling continue.

If they are going to AWOX, give them an incentive to leave.

Circulate a corp mail that for the next week a free kill hazing rite will be open on that pilot. The pilot with the most kill mails on them, podding included, will win a prize.

Then do it again the next week.

You either create a feel good sport, or they leave. Win / Win. You might possibly rehabilitate them, but let's not get too optimistic.

As someone closely involved with such "safaris", here's my advice on dealing with this:

Vet your recruits better. A proper API check will tell you what other characters they have on their account. Doing research on THOSE characters might reveal something. Be sure you can see their kill logs, and look for them killing members of their own corp.

Have a minimum SP limit. If you really want to recruit and train noobs, establish a feeder corp where noobs can reside while you help them get started, and then move up once they get to your SP requirement. This eliminates short-term alts from being able to shoot anything more than cheap T1 stuff. Be sure your noobs know that your policy is that any ships lost to recruits in the feeder corp are insured by the corp. That way if some schmuck DOES go noob bashing, they know you've got their backs.

What I think needs to be changed:

So far as I know, neutral logi repping a corp fight don't get any form of aggression. This gives an awoxer invincible logi support. This is a hole that should be closed.

It's impossible to kick a corpmate in space. Previous bugs have shown that this prevents inadvertent Concord losses and other problems, BUT you should at least be able to set someone to be kicked at the next downtime if they're in space and can't be kicked immediately. Theyshouldn't get to stay in a corp that wants to kick them just because they beat the CEO to logging in after downtime.

This sounds like a pretty decent compromise, at least a CEO/Director would know they'd be gone at some point within the next day instead of having to deal with someone they couldn't hope to remove unless they managed to catch them docked.

Why don't we just make a PVE server like WoW... Not!... Eve isn't made for little boys.