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.
12Next page
 

24h period of time after ally disbanding.
Author
Previous Topic Next Topic
Mikey PooNanny
Industrial and Science Union
#1 - 2014-03-12 19:17:39 UTC
As you know, ally Darkness of Despair was disbanded by the ally maker without any notifications to the ally members.

That was very ... suddenly. And now, a lot of players have a problem with moving their assets, capital's, supers and so on,
because of loosing claim on stations and systems.

Can the CCP make the time delay after disbanding the ally for the 24 hours with sending notifications to the all ally members like 'Your ally will be disbanded in 24 hours!'

Thanks.
Rediska2
Doomheim
#2 - 2014-03-12 19:28:44 UTC
+1
Whitmore
Far East Inc
DarkSide.
#3 - 2014-03-12 19:39:03 UTC  |  Edited by: Whitmore
Crymea river
indiana bones
Federal Navy Academy
Gallente Federation
#4 - 2014-03-12 19:44:33 UTC
-1

Hi Sec = High Security
Low Sec = Low Security
Null Sec = No Security

If you want more security, go to Hi Sec.
Vaju Enki
Secular Wisdom
#5 - 2014-03-12 20:01:48 UTC
No. Cry more.

The Tears Must Flow
Rediska2
Doomheim
#6 - 2014-03-12 20:04:10 UTC
Our tears are over. You can be next )
Kotofeya
Russian ICE Bears
Goonswarm Federation
#7 - 2014-03-12 20:26:33 UTC
agreed with TS, so it will be fair, cos if some one can loose control or have "emorage", He can push the button of Disband ally.

i have more ideas: All directors need to vote about Disband, all corporation (if they was kicked from ally) have stasis 1-3 days.
Gizznitt Malikite
Agony Unleashed
Agony Empire
#8 - 2014-03-12 21:23:02 UTC

I have mixed feelings.

I like the idea that certain key individuals have the power to disband an alliance. I am alright with a 24hr cooldown with a few caveats:

1.) Alliance assets and Sovereignty are frozen, so you cannot transfer Sov level assets to another entity. Then, when after the cooldown, sov is 100% dropped in all systems.

2.) A notification is sent to the CEO of all member corps that the alliance is about to disband, and that they are stuck for 24 hrs. By stuck, I mean they cannot drop alliance and join another... they are in stasis while the alliance disbands.

This gives you a little notice to prepare for the loss of sov, but it doesn't save you from it. It gives you a little notice to work with allies and alliance mates to limit some of the blue-confusion, but you'll still have to cope with it.

If you want more than this, I just cannot support it. If you don't like the fact some members have such power, then limit who has the power and prey you choose well.
Shameless John
Close Encounters of the EVE Kind
Goonswarm Federation
#9 - 2014-03-13 08:34:47 UTC
Leaving corp when you have roles 24h stasis period
Joining the alliance 24h waiting period

Kicking corp from alliance immediate???

Out of game hacking of holder's account causes irreparable damage.
To mitigate this either 24h global (all corps) stasis period should be implemented,
or just like as with having roles, corps with ally assets deployed cannot be kicked immediately.
assets like: online tcu, stations, online hub, online sbu, online bridges, online cynogens, online csaa and such.
Zelendub
Backwater Redux
Tactical Narcotics Team
#10 - 2014-03-14 12:27:24 UTC
+1
Rendiff
The Scope
Gallente Federation
#11 - 2014-03-14 12:41:06 UTC
Shameless John wrote:
Leaving corp when you have roles 24h stasis period
Joining the alliance 24h waiting period

Kicking corp from alliance immediate???

Out of game hacking of holder's account causes irreparable damage.
To mitigate this either 24h global (all corps) stasis period should be implemented,
or just like as with having roles, corps with ally assets deployed cannot be kicked immediately.
assets like: online tcu, stations, online hub, online sbu, online bridges, online cynogens, online csaa and such.


It's never made sense why minor things like a toon dropping roles has a 24hr cool down but disbanding an entire alliance is instant.
Helia Tranquilis
Confused Bunnies Inc
#12 - 2014-03-14 12:47:56 UTC
I agree. Actions of this magnitude shouldn't be instant.

Only ones disagreeing are individuals who have their alts infiltrating to director level position for similar content creation.

+1
Gizznitt Malikite
Agony Unleashed
Agony Empire
#13 - 2014-03-14 15:12:19 UTC
Helia Tranquilis wrote:
I agree. Actions of this magnitude shouldn't be instant.

Only ones disagreeing are individuals who have their alts infiltrating to director level position for similar content creation.

+1


I don't have a problem with a "cooldown" stasis period prior to the disbanding. However, if you have a spy or disgruntled member at that level of leadership, I have a problem with you sidestepping the majority of harm they may cause. As such, you should not be able to:

♦ Prevent your Sov from dropping (which means you should not be able to transfer sov to another entity).
♦ Reclaim assets and isk they stole.
♦ Stop the inevitable disbanding of the alliance.

The 24 hr cooldown, which allows you to make a contingency plan for WHEN (not if) the alliance disbands and sov drops is fair. It also allows you to insure the rogue directors account wasn't hacked. However, lets be frank, account sharing is not hacking, and if that lead to the loss you get a character ban AND a disbanded alliance, as CCP shouldn't have to deal with that bullshit EULA violating situation.

Woeful Animation
Ascendent.
Test Alliance Please Ignore
#14 - 2014-03-14 16:31:34 UTC
I understand the shenanigans of sudden disbanding of large alliances and corps have caused, and understand that it is part of the fabric of the game. I also see the point. The alliance rank and file members suffer the most once the station is locked. A 24 hour cool down before dissolution is appropriate.
Various-V
State War Academy
Caldari State
#15 - 2014-03-28 03:35:51 UTC
+100000
TheMercenaryKing
Collapsed Out
Pandemic Legion
#16 - 2014-03-28 03:45:07 UTC  |  Edited by: TheMercenaryKing
Oh, you kept assets in a player owned station. As Shakespeare would word:

A fool of fortune for which he was, yet never once doth he learn: should the merchant not protect his love, an evil shall swoop from above. For the ages now gone yet he yearns, why his goods were never returned.
Alex Mortiss
Arctic Beans
Pandemic Horde
#17 - 2014-04-24 14:36:44 UTC
+1
Bane Nucleus
Dark Venture Corporation
Kitchen Sinkhole
#18 - 2014-04-24 15:12:06 UTC
If you were in that alliance, it's your fault it happened. Don't trust anyone with all of your assets. All your eggs in one basket and what not.

No trolling please
Lephia DeGrande
Luxembourg Space Union
#19 - 2014-04-24 15:18:12 UTC
Frostys Virpio
State War Academy
Caldari State
#20 - 2014-04-24 17:05:42 UTC
indiana bones wrote:
-1

Hi Sec = High Security
Low Sec = Low Security
Null Sec = No Security

If you want more security, go to Hi Sec.


Then no-one should receive warning when a structure is getting attacked unless a player notice and warn the appropriate people.
12Next page