These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
Previous page123Next page
 

Allows CEOs to expel members in space - Ideas for solving the previous abuses

Author
Kaarous Aldurald
Black Hydra Consortium.
#21 - 2013-06-20 09:46:51 UTC
Alpha Taredi wrote:
I suppose doing proper api & background checks is too much work?


Apparently, yes. A determined awoxer can get around this, of course.

But the majority of potential awoxings, can be avoided thusly.

"Verily, I have often laughed at the weaklings who thought themselves good because they had no claws."

One of ours, ten of theirs.

Best Meltdown Ever.

Muad 'dib
State War Academy
Caldari State
#22 - 2013-06-20 09:52:58 UTC
Would give wormholers the ability to use a core game mechanic in the space they live in too.

Cosmic signature detected. . . . http://i.imgur.com/Z7NfIS6.jpg I got 99 likes, and this post aint one.

Amizo Hamma
Imperial Shipment
Amarr Empire
#23 - 2013-06-21 00:03:18 UTC
I figured I'd get all of those responses. More tears. PVP happens. CCP shouldn't make up for your mistakes. etc. etc. blah blah.

Maybe if people read anything I had posted before replying they'd discover my intent for this feature and idea post: As a CEO or Director wouldn't it be nice if you could kick members that are in space?

That's it. That's all I was getting at. It has implications for anti-griefing, wormhole corps, and more. The rest of my walls of text were my attempts at intelligently walking through the issues of regaining that ability to kick members while they're in space and looking at possible solutions for those issues.

Obviously internet forums for a video game isn't where I should be expecting intelligent discourse, but this isn't for the players. It's for the devs.
Black Dranzer
#24 - 2013-06-21 00:16:09 UTC  |  Edited by: Black Dranzer
Corp-side limited engagements are clunky and probably hard to program.

I agree that a simple "Eject from corp on next logout or dock" flag would be far better. Or hell, even "Eject from corp on next warp" could work.

Don't give me this crap about "Hurr durr choices consequences". This is not an intentional gameplay style designed to promote interesting interactions, it's an unavoidable oversight that only exists because CCP was trying to fix a far worse exploit from past times.

EDIT:

Also, it should be pointed out that it is not the obligation of corp owners to justify their desire to eject people from their corporation. This mechanic is implcit; It's your corp: you get to decide who gets in, who gets out, who's given roles, etc. If you don't like this, you, the AWOXer, must provide a counterargument. Now, the ability to eject people was revoked under certain circumstances, but the reason for this was explicitly to counter an exploit. However, in doing this, a new exploit was created.

The key is, the implication that an owner has a right to eject whoever they want has not changed. If we can find a better solution to the original exploit, then it should be implemented. The fact that the initial attempt opened up a new exploit does not somehow grant the new exploit more authority. The original and primary goal is to provide a CEO with the tools he needs to efficiently run a corp without being granted access to exploits.

If you want a license to shoot the guy, go start a war.
Alvatore DiMarco
Capricious Endeavours Ltd
#25 - 2013-06-21 03:17:35 UTC
I wonder what the so-called "original exploit" was.
Black Dranzer
#26 - 2013-06-21 12:08:28 UTC
Alvatore DiMarco wrote:
I wonder what the so-called "original exploit" was.

Amizo Hamma wrote:
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.

BOldMan
Game Land Operations
#27 - 2013-07-26 20:06:05 UTC
This exploit is used by pizza right now.
Using exploits must be punished cf eve rules. Or GM and other people involved in overwatch this game to work properly are failing hard.
Freighdee Katt
Center for Advanced Studies
Gallente Federation
#28 - 2013-07-26 21:53:59 UTC  |  Edited by: Freighdee Katt
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.

EvE is supposed to suck.  Wait . . . what was the question?

Hesod Adee
Perkone
Caldari State
#29 - 2013-07-26 22:21:52 UTC
Amizo Hamma wrote:
Aliventi wrote:
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?


Ask for a full API check from all new recruits. Check it.

Check the recruits killboard history and question any time they shoot their own corp members.

StoneCold wrote:
That´s not true. Podkill the AWOXer, then remove him quickly.

There is no way to catch a pod in high or low sec without the target making a mistake.

Black Dranzer wrote:
Or hell, even "Eject from corp on next warp" could work.

That would limit the potential damage the AWOXer could do by far too much for my liking.

What happens if they do a short, in battle, warp ?

Freighdee Katt wrote:
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."

That could work to allow kicking in space. But it would also drastically limit the potential damage the AWOXer could do.

With the kick on next log/dock flag, the only change is that you don't have to race to login when downtime ends to kick the AWOXer. A race that can easily be lost as the AWOXer just needs to login but the CEO needs to login, load into space/station and then hit the kick button. But for many CEO's, they can't even attempt that race without missing work or sleep. Giving a major advantage to AWOXers living in AU timezones, as downtime happens during their primetime.
Omega Flames
Caldari Provisions
Caldari State
#30 - 2013-07-27 01:47:27 UTC  |  Edited by: Omega Flames
Amizo Hamma wrote:
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)
Hesod Adee
Perkone
Caldari State
#31 - 2013-07-27 02:37:31 UTC  |  Edited by: Hesod Adee
Omega Flames wrote:
Amizo Hamma wrote:
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.
Arthur Aihaken
CODE.d
#32 - 2013-07-27 03:38:53 UTC
Amizo Hamma wrote:
Maybe if people read anything I had posted before replying they'd discover my intent for this feature and idea post: As a CEO or Director wouldn't it be nice if you could kick members that are in space?


The people whining are the ones AWOX'ing, naturally. I'm all for equal abuse; if you can AWOX corps members then you should be able to kick them out n space and set them up too. All is fair in love and war. :D

I am currently away, traveling through time and will be returning last week.

Onslaughtor
Phoenix Naval Operations
Phoenix Naval Systems
#33 - 2013-07-27 04:17:31 UTC
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.
BOldMan
Game Land Operations
#34 - 2013-07-27 10:06:15 UTC
Hesod Adee wrote:

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.


Oh, they are break EULA using an exploit. CCP fail when they implement that crap expel rules.
Who defend this, is on verge of using this.
Diesel47
Deep Core Mining Inc.
Caldari State
#35 - 2013-07-27 10:47:47 UTC
No thanks.

EvE is a tough place, I don't like making it easier for weaklings.
Omega Flames
Caldari Provisions
Caldari State
#36 - 2013-07-27 11:36:49 UTC
Hesod Adee wrote:
Omega Flames wrote:
Amizo Hamma wrote:
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.

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.
Muad 'dib
State War Academy
Caldari State
#37 - 2013-07-27 11:39:15 UTC
Onslaughtor wrote:
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.


what about:
If the player has recently attacked another corp member without dueling they can be kicked?

or since thats still exploitable

just dont allow friendly fire in corps, like corp to corp in an alliance is.

We have dualing now for fights, so whats the big funking deal bintch?

Cosmic signature detected. . . . http://i.imgur.com/Z7NfIS6.jpg I got 99 likes, and this post aint one.

Phoenix Jones
Small-Arms Fire
#38 - 2013-07-27 12:00:20 UTC
We had this happen somewhat recently. Guy was booting ships out of a sma (why I have no idea), retrieved boats, changed passwords, removed roles, the guy decides to camp the system in a cloaked t3 for the next two weeks. Couldn't kick him out of corp as he would log in just after downtime, throw some music up and afk cloak for half the day, attempting to find a solo person to gank.

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.

Yaay!!!!

Arthur Aihaken
CODE.d
#39 - 2013-07-27 15:21:30 UTC
Phoenix Jones wrote:
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.


Some people are just supreme a**hats.

I am currently away, traveling through time and will be returning last week.

Gospadin
Bastard Children of Poinen
#40 - 2013-07-29 18:39:48 UTC
Freighdee Katt wrote:
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.


Great (and simple) idea.
Previous page123Next page