Email when alliance member sets self-destruct. #241

Open
icydee opened this Issue Jun 1, 2013 · 6 comments

Projects

None yet

4 participants

@icydee
Member
icydee commented Jun 1, 2013

Alliance GSD recently lost three SS because the member who 'owned' them self-destructed.

Ideas are:-

  1. Don't allow someone with SS, and who is in an alliance with other members to self-destruct.
  2. Allow self-destruct, but send out an email.
  3. Transfer all SS to the Alliance owner on self-destruct.

I think I prefer option 3.

  • icydee
@rizen
Member
rizen commented Jun 1, 2013

Heh. I prefer the chaos of it all. Let it burn!

Sent from my iPhone

On Jun 1, 2013, at 10:33 AM, Iain C Docherty notifications@github.com wrote:

Alliance GSD recently lost three SS because the member who 'owned' them self-destructed.

Ideas are:-

  1. Don't allow someone with SS, and who is in an alliance with other members to self-destruct.
  2. Allow self-destruct, but send out an email.
  3. Transfer all SS to the Alliance owner on self-destruct.

I think I prefer option 3.

icydee

Reply to this email directly or view it on GitHub.

@lemming552
Collaborator

Duly noted. :)

We also need to take into account an alliance leader self destructing after timing out. 

JT Smith notifications@github.com wrote:

Heh. I prefer the chaos of it all. Let it burn!

Sent from my iPhone

On Jun 1, 2013, at 10:33 AM, Iain C Docherty notifications@github.com wrote:

Alliance GSD recently lost three SS because the member who 'owned' them self-destructed.

Ideas are:-

  1. Don't allow someone with SS, and who is in an alliance with other members to self-destruct.
  2. Allow self-destruct, but send out an email.
  3. Transfer all SS to the Alliance owner on self-destruct.

I think I prefer option 3.

icydee

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

@rizen
Member
rizen commented Jun 1, 2013

Do what you think is right. Don't listen to my ramblings.

Sent from my iPhone

On Jun 1, 2013, at 12:54 PM, Mark Lemming notifications@github.com wrote:

Duly noted. :)

We also need to take into account an alliance leader self destructing after timing out.

JT Smith notifications@github.com wrote:

Heh. I prefer the chaos of it all. Let it burn!

Sent from my iPhone

On Jun 1, 2013, at 10:33 AM, Iain C Docherty notifications@github.com wrote:

Alliance GSD recently lost three SS because the member who 'owned' them self-destructed.

Ideas are:-

  1. Don't allow someone with SS, and who is in an alliance with other members to self-destruct.
  2. Allow self-destruct, but send out an email.
  3. Transfer all SS to the Alliance owner on self-destruct.

I think I prefer option 3.

icydee

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub.

@lemming552
Collaborator

But the ramblings are very entertaining!

So, in answer to icy, I prefer #3 with the caveat that something must be done if it's the alliance leader self destructing. Probably best to pick the most active member for the new leader, IMO.
Sea of Goats dissolved because their leader timed out.
On one hand, the alliance should be able to police their own in that case, but this way the solution is a little more flexible.

@fireartist
Collaborator

I think there's value in allowing as many avenues as possible for someone to turn against their own allies.
If we really need to change anything, I'd prefer option 2 - automatically email allies - but preferably not as soon as they turn on self-destruct - maybe just 12 hours before the timeout.

@lemming552
Collaborator

OK. I was fixing the code that had supply chains continue to SS after a member leaves. Same place for logic, so now live on pt we have this:
If a member leaves an alliance for any reason:

  1. If leader, who ever has the latest login becomes leader. (only happens if leader self destructs)
  2. Any SS under leaving member's ID, gets turned over to current leader.
  3. All supply chains from leaving member to space stations get terminated.

I haven't done any email portion of this, but it looks like the only ones that need to be done is if someone self destructs. (I did note, leadership transfer doesn't send an email either, probably should.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment