Test Server Feedback

I personally would appreciate it if you hold this back till you're ready to overhaul the entire corporation interface.
It's just a one click you remove with little to no benefits and a whole lot of possible headaches and abuses.

I'm sure that once you're ready redoing the interface you'll find no need for this one-click add-on many do not want nor need.
Is this really needed I ask myself.

Also introducing this then going oh, we need to to mitigate the concerns that have been raised seems a bit odd.
You're an EVE dev. First thing you probably should do when you have an idea of a new mechanic/item/etc is asking your self, "how will our players abuse this?" You know us we will. Give us a hand we'll run away with your arm.

Ok all, thanks again for all the feedback.

Firstly let me clear up some misconceptions that have been rampant in this thread and then Ill get onto what we're doing to address some of the legitimate concerns people have for this change. Bear with me!

How the current system actually works (On TQ right now)
1. Character applies to corporation. - Must be in station
2. A corp member with appropriate roles invites player to join. - Can be in space or in station
3. Character accepts invite and enters corp. - Can be in space or in station

As you can see from the above, most of the things people are worried about are already possible on TQ, the only thing a station is required for currently is the initial application, after that application is in the rest of the process is unrestricted.

After considering this though, we do admit that the system is inconsistent and is open to abuse, so we've made some changes that should improve this for all.

How the system will work in Rhea (Including changes we've made)
1. Character applies to corporation. [SKIPPABLE] - Can be in space or in station
2. A corp member with appropriate roles invites player to join. - Can be in space or in station
3. Character accepts invite and enters corp. - Must be in station OR pod

In addition to this, quitting corp will also now be subject to the station or pod restriction, meaning that changing corporations is always consistent.

This change does a few things:
- Moves all restrictions to the most obvious step, aligning them with the existing restriction to changing to a rookie corp.
- Allowing people to switch corporations while in pod restricts their ability to abuse the mechanic (Which as some have pointed out is already a confirmed exploit), while not forcing wormholers and other stationless folk to return to a station to change corporations.

Some notes on spam
Many were concerned that this option will be open to spam abuse, and you could expect to receive a constant stream of invitations every time you enter places such as Jita. Firstly, invite spam is a bannable offence, if you suspect someone of doing this you need only report them for spam and our GMs will do the rest! Secondly, a player can only have one invite pending per corp, so while spamming from multiple corps is possible one corp cannot send you an invite more than once. And last but not least, we'll be throttling the amount of invites a player can send per minute to 6.

And as mentioned previously, you can use the new notification to ensure you never have to see another invitation.

For those unclear of the process it is as follows:
1. Click the notification button.
2. Click the settings button.
3. In the resulting window, expand the 'Corporate' section.
4. Deselect both check boxes next to 'You have been invited to join a corporation'

And finally, I just wanted to ensure everyone that this is by no means the end of Five 0s foray into corps, but in fact the beginning. This was simply a low hanging fruit designed to ease the process from newbro to corporation member and all round spacebro. Expect to hear more from us in the future as we delve into this wonderland of contradictions and old code!

Agreed. To me, this is quite useful and makes sense to have a standardization of the recruitment/kicking process.

What a dramatic twist.
Looks like the change is not that useless anymore.

Question.

I undock in a shuttle or rookie ship and allow a war target to blap me without resisting them (no limited engagement timer). I then accept another corp invite into a neutral corp in space as a capsule before the WT has a target lock - if they shoot my pod, will they be CONCORDED?


Second question.

Re invite spamming. Is it acceptable to send totally unsolicited corp invites under this new system, assuming you don't intentionally send more than one invite to a given pilot and you don't intentionally time the invites to be disruptive? (and you don't use any means to circumvent the 6 per minute rule)


Third question.

I assume it is against the rules to ever send someone an unsolicited corp invite at a time that is intended to be disruptive, even if you only ever send one invite (e.g. when you have a station trade window open with the person on your alt). Is this correct?




Concrete suggestion to fix the first issue: Have joining a corp in space in a capsule be only possible if you do not have a capsuleer combat logoff timer.

You might want to consider automatic role/title drop when players want to leave or gets kicked..

So, the process now to get into a corp in space is:

1) Have Invite Ready
2) Eject Pod
3) Accept Invitation
4) Board Ship

Unless you're considering adding a flag to prevent a pod from boarding a ship within a short period surrounding joining or leaving a corp.

Sorry I should have made this clear, a session change happens when you change corp, so you can't board a ship for a short time afterwards.

Hmm, I was sure that this wasn't how it worked, but you're right. My mistake.



Okay, so given that joining is now pod or station restricted, I presume the old surprise war target exploit ruling will no longer apply? So this is actually a wardec buff and intentionally so?

What about a player who is in a pod and currently pointed joining another corp to immediately change the rules of engagement while in pvp? This remains an issue, could you restrict accepting an invitation to a) docked or b) in pod with no pvp logoff timer?

Complaints about invite spam stand, but clearly you aren't going to budge on that.

The exploit ruling stands until we explicitly state otherwise. This change makes that particular exploit less powerful and more difficult, but that doesn't negate the earlier ruling.