F1 when you're already dead?

[Nodoka Hanamura]

I wanted to bring this up for discussion since this came up.

If I'm a capital ship that has suffered a total loss and have yet to be *blued* but am going through the process of 'cooking off' as it were, if I log off before I properly am killed, that's a sanctionable offense? Or am I misunderstanding?

---

[TheSauron]

It is a sanctionable offense because, when timed properly, it prevents a blue message from appearing, denying the enemy kill confirmation for player bounties or event scoreboards.

---

One MD Admiral

[Sally]

Yes, it's a dick move that can be covered by both 1.0 and 1.2 as it tries to negate evidence of confirmed kills, specially if a pvp event or bounties are involved, and in many cases there's always the prospect of bounties or MDs being a thing.

If it's accidental then you can post on the disconnected thread and apologize for the inconvenience caused, I haven't seen so far such scenario being accidental but it can happen and should not be reported if it is.

---

"I suppose many people will continue moving towards careless computing, because there's a sucker born every minute." - RMS

[Nodoka Hanamura]

It is a sanctionable offense because, when timed properly, it prevents a blue message from appearing, denying the enemy kill confirmation for player bounties or event scoreboards.

Huh. Didn't know that. I'll admit I think I've done it once or twice but more out of frustration than trying to defraud someone of the kill - though to my knowledge it didn't prevent the blue from being reported. Will keep that in mind for the future so I don't get sent to the funny prison system.

---

[Nika]

I wanted to bring this up for discussion since this came up.

If I'm a capital ship that has suffered a total loss and have yet to be *blued* but am going through the process of 'cooking off' as it were, if I log off before I properly am killed, that's a sanctionable offense? Or am I misunderstanding?

It is. It's said above already but it does, in fact, prevent a kill message for appearing - something I learned firsthand through this sanction. Genuinely didn't know this before, now I do. Probably a byproduct of reimplementation of fuses.

[Dark Chocolate]

Demonstration of what happens when you F1 in middle of fuse. (For Educational Purposes)

Suggestion:- Death Fuses are beautiful. It gives great satisfaction when you manage to get a kill on a Capital Ship. It's okay to lose. Allow your opponent to have his moment of glory.

As your Capship slowly explodes, Use the Time to RP. Make your crew panic as the ship slowly disintegrates. an example below:-

LNS-Michigan:- *static* Reactor Critical! All Hands get to the Escape Pods! Abandon Ship! I repeat. Abandon sh*static*

Have fun as you beautifully explode.

[Sally]

Demonstration of what happens when you F1 in middle of fuse. (For Educational Purposes)

Honestly I think there's probably room to patch out this, it'd solve the issue and wouldn't waste people's time sanctioning and punishing this behavior.

---

"I suppose many people will continue moving towards careless computing, because there's a sucker born every minute." - RMS

[Karst]

It is a sanctionable offense because, when timed properly, it prevents a blue message from appearing, denying the enemy kill confirmation for player bounties or event scoreboards.

This isn't just about bluemsgs or the denying thereof. If you're in-game, in range of other players, don't F1. Whether you're about to explode or not.
I mean doing it while you're exploding is way worse than in other circumstances, but just don't do it ever.

Also, thread mildly cleaned. Feel free to discuss the actual Rules aspect but keep the shittalking to a minimum, please.

---