simple fix, set a remove from corp flag for next time they log out/dock in station, problem solved, but no, that would be too easy to provide, everything else can be queued up, why not that?

simple fix, set a remove from corp flag for next time they log out/dock in station, problem solved, but no, that would be too easy to provide, everything else can be queued up, why not that?

Very simple.

Currently the only way to kick an AWOXer who wants to stay in the corp is to login before he does after downtime. For a lot of us, this simply isn't possibly because of sleep and/or work. Queue it up and that ceases to be a problem.

If CCP ever removes downtime, then that might cause a bit of a hitch. But that is solvable.

No. Your poor recruitment screening has consequences.

I figured someone would say this eventually. The typical "helpful" eve player.

Do enlighten us. How can you stay newbie friendly without adding excessive risk to your current members?

[...]

Very simple.

Currently the only way to kick an AWOXer who wants to stay in the corp is to login before he does after downtime. For a lot of us, this simply isn't possibly because of sleep and/or work. Queue it up and that ceases to be a problem. [...]

Disclaimer: Yes, this post is fueled by recently having an AXOWer in my corporation and being helpless to expel them and discovering GMs aren't permitted to assist in any way except point me here

Correct me if I'm mistaken, but isn't AWOXing one of those things that CCP is completely okay with and uses as part of its various ad campaigns?

"Join up with a corp, work your way up the ranks, earn money and power and trust and then pull everything out from under them - or don't. The choice is yours. What will you do?."

I suppose doing proper api & background checks is too much work?

I wonder what the so-called "original exploit" was.

Abusive situations:

• You're at war with another corp/alliance. You have a bait ship waiting. Opponents attack. You expel the member in the bait ship. Instantly the opponents are flagged and attacked (by CONCORD and/or empire guns) provided you're in high sec or low sec near empire guns.
• You're sparring with a corpmate in high sec, they begin to fire on you, as a CEO or Director, you could expel them and watch as CONCORD rips their ship apart.
• Other potential abuses by CEO/Director.

I figured someone would say this eventually. The typical "helpful" eve player.

Do enlighten us. How can you stay newbie friendly without adding excessive risk to your current members?

That-¦s not true. Podkill the AWOXer, then remove him quickly.

Or hell, even "Eject from corp on next warp" could work.

The automatic LE flag on corp-against-corp combat start is a good idea. It's been suggested before. Too bad we're past the cutoff for the current round of "Reasonable Things."

Disclaimer: Yes, this post is fueled by recently having an AXOWer in my corporation and being helpless to expel them and discovering GMs aren't permitted to assist in any way except point me here.

you are allowed to kick when they are in space and logged off already and if a person is staying online 23/7 to harrass your corp then a GM can infact kick them once the 24 hour wait time is over (that is 24 hours from the last time they had any corp roles). If any GM told you they couldnt after the 24 hours was already up then that GM doesnt know how to do his job and you need to demand the petition be fowarded to a senior GM. (and yes I know all this for a fact as I've been a ceo/director for over 3 years now and have had the same issue come up before)

So, despite the AWOXer not having broken the EULA, you can get CCP to take action against them ?

That sounds like a failure on CCPs part to me. At most it should be a band-aid to keep things running while they look for a permanent solution.

So, despite the AWOXer not having broken the EULA, you can get CCP to take action against them ?

That sounds like a failure on CCPs part to me. At most it should be a band-aid to keep things running while they look for a permanent solution.

To me this just makes common sense. AWOXers should not be able to stay in the corp after a hit by remaining logged in and in space. If there was some way to catch and kill them then It would be less of a problem, but cloaks.

The gank part I'm fine with, the cloaking in the system part i'm fine with, the camping part i'm fine with. 2 weeks spent trying to remove the guy from corp... yea that was just fking dumb.

The automatic LE flag on corp-against-corp combat start is a good idea. It's been suggested before. Too bad we're past the cutoff for the current round of "Reasonable Things."

The current mechanic of "anything goes in corp-on-corp" could easily be changed to "any corp-on-corp aggression automatically begins a limited engagement." Rather than having corp-specific LE rules, just make any attack on a corpmate start a regular LE, and then let the already established LE code kick in. Booting someone from the corp should have no effect on the LE timer running, and it would continue to run so long as aggression continues.

If the LE ends, because combat ended, then it's just neut-on-neut and the usual rules apply. But so long as the LE continues, there is no exploit. If someone manages to break combat long enough for it to end, then that should not be a problem, and neither party can restart without the expected consequences.

Do this, and you completely solve the "exploits," in a way that makes good and sensible use of the new rules and reliable code already built into Crimewatch. With this in place, there is no longer any need for idiotic kludge-arounds like "can't kick in space."

It's a simple problem with a simple solution. Everything else that will be raised in this thread, as it is raised in every thread on this topic, to "justify" keeping a patently stupid mechanic made obsolete by the simple potential solution under the new Crimewatch, is just so much hurrdurr bullshit.

I would hardly call removing someone from a corp "taking action against them" but ok yes if the corp wants them gone then the corp has the right to remove them, that has always been the case. Also it's not hard to simply log in immediately after DT and kick them while they are still offline.

the reason for no space login kick is real simple. A 0.0 resident has to be be given the chance to dock up and do something with their assets.. If its as simple as pick the one ship they want to ride out on one last time and contract/sell/black frog the rest, so be it.

Remember in 0.0 a kick means lost docking rights in a locked station after the undock as a neut. If no JC in that station....this is not bypassable until station is reclaimed.

CCP has to give ole boy/girl at least one fair shake to get their crap. Or else it be a petition and one they'd have to give into. Because ccp also has to factor in a corp leader being a ****, kicking for no reason and looking to bust balls with no more dock rights to get their crap. You can't black frog a cap.


Then you'd have 0.0 crews going well wtf is the point to station locking if a petition lets people slide in like this.


Do what 0.0 does in this case. Player is a known problem...kill him (in game, ofc). If in a hulk....well then dock up when in local. Get combat ship and kill him becomes an option after that if so desired. Remember, bears have teeth too (and claws even).

the reason for no space login kick is real simple. A 0.0 resident has to be be given the chance to dock up and do something with their assets.. If its as simple as pick the one ship they want to ride out on one last time and contract/sell/black frog the rest, so be it.

Remember in 0.0 a kick means lost docking rights in a locked station after the undock as a neut. If no JC in that station....this is not bypassable until station is reclaimed.