Discovery Gaming Community
Admin Notice: Player F1ned - Printable Version

+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Rules & Requests (https://discoverygc.com/forums/forumdisplay.php?fid=6)
+--- Forum: Rules (https://discoverygc.com/forums/forumdisplay.php?fid=25)
+---- Forum: Sanctions and Warnings (https://discoverygc.com/forums/forumdisplay.php?fid=43)
+---- Thread: Admin Notice: Player F1ned (/showthread.php?tid=24814)



Admin Notice: Player F1ned - Korrd - 08-13-2009

The player Oracle|Kayder has just been fined.

Reason:
  • F1ing out in space while being pirated
I've removed all your equipment and some credits. It would have been cheaper if you had just given the pirate the credits he requested, tried to RP your way out, or just fought back instead.

Please, don't do it again.:rtfm:


Here be dragons


Admin Notice: Player F1ned - Xareck - 08-13-2009

Could I see the evidence, as I have no recollection of ever having F1ed at any point in time.


Admin Notice: Player F1ned - Egon Bigmemes - 08-13-2009

Yeah uh, I'm generally flying with him most of the time he's online. I've never seen him F1 anywhere except in space, and I haven't seen him pirated. The only possible situations I've seen it say he tried to F1 out was when he lagged out infront of Manhattan, and in the Pittsburgh debris field.


Admin Notice: Player F1ned - Elsdragon - 08-13-2009

WHenver you laggout, get back on as sson as possible,Or post a thing in flood with your char name and apoligizing for the disconnect.


Admin Notice: Player F1ned - Korrd - 08-14-2009

The sanction is being reviewed as we speak on the admin forums. Please, be patient while it is discussed.


Admin Notice: Player F1ned - eyvind - 08-14-2009

I would like to mention that I was witness to -- and have evidence of -- an incident that might be directly related to this. I will of course cooperate in such capacity, if necessary.


Admin Notice: Player F1ned - Cannon - 08-16-2009

After review this sanction has been reversed. On balance it has been accepted that this was an accidental lag out rather than an intentional disconnect.