Freeport.13 has been sanctioned for breaking the following rule:
Quote:5.9 Disconnecting from the server in a PvP fight to escape, as well as in any other situation that involves player interaction, is not allowed. If you lose server connection during a player interaction, you should get back in game quickly to continue the interaction, with the other player's permission. If that is not possible, then post on the forums and PM the players involved.
You have been fined something. Note in your hold. When you got back in game you should have PMed the guys who were near you to ask if they wanted to continue the interaction.
I've been asked to post on behalf of Mudd, I hope you don't mind.
Quote:Cannon, as you know I've been having some odd issues for months now with that one ship having randon disconnects.
Bear can confirm it's been happening as of late still, as he's seen it happen as well.
I've not knowingly done so on other folks without getting back to them.
I honestly have no clue when or were this happend, however all I can figure was it was in the last few days as that is about the only time in a while I've took it out of Omicron 74, I flew around randomly DCing every system or two then docked it to see if the issue was persisting after I removed all cargo as you had mentioned over skype that the lights/guns plus cargo all add up to some limit that can cause issues.
All I can figure is that I DCd about the time someone pooped on long range scans or shortly before then.
Simply put, as far as I know there WAS no interaction as I never saw anyone even, although yes I am aware that simply F1ing if someone appears on scan can count as an F1 due to the abuse by the lolminers.
However, I had no reason to do that. The whole point of the ship's RP is to run into folks and RP with them.
You were in Omicron Iota. I found you with my morph. While I was calling for some backup, you F1'd. You came back after a few minutes, and stayed in the system for around 10-15 minutes, before heading back to Omicron Delta.
I didn't say anything yet, cause you know, Battleship vs Morph, I needed some backup. It seemed to me that you were looking for an easy way out.
This sanction is being reviewed, etc, etc and so on. Due to a lack of entrails I expect this will be delayed until the shipment comes in around the 20th of the month. Stay tuned.
Proud member of "the most paranoid group of people in the community"
#1 as the admins know, Ive had a history of random disconnects on this ship.
In skype cannon has admitted that it's due to a possible unknown bug.
Quote:[8/11/2010 2:59:56 AM] Matt (Cannon) says: I've noticed this with other big ships. I've never known why.
#2 in the SS of the sanction, there is no need to F1.
Simply put, it was a morph. Unarmed aside from a CM.
He couldnt hurt me. He couldnt CD me. All he could do was call in a fleet.
#3 There was no attempt at RP from the morph, or anything in system/local chat, just a 'git yer bombas fer bluemsg' call in group chat
#4 When I reconnected several minutes later (I never even saw anyone on scanners) there was NOONE on scanners. He simply SSd for a report and flew off. And while yes it is mostly on the person who disconnected to re-initate the RP, the fact that he vanished within a short time shows he simply SSd for a sanction and flew off. I dont think I was off more than five minutes tops, I just alt tabbed, read skype, then came back.
As I said above, this sanction is being reviewed. Obviously this review has not completed.
You may not use stuff said by me in skype to force a review. Don't bother contacting me via skype again.
I'll remind you that the main reason you were sanctioned was that "When you got back in game you should have PMed the guys who were near you to ask if they wanted to continue the interaction."
Proud member of "the most paranoid group of people in the community"