I think I can have a good guess at an answer for this, if you disconnect for any reason you should not re-engage at all, you cannot proove why you disconnected, just that you did. As a result every disconnect should be treated as an F1 incident, and the rules applied. If this seems overly harsh, it is, but then every disconnect could be excused away if you let even one pass.
Saint Del is considered a holy healer of diseases of children, but also as a protector of cattle.
' Wrote:I think I can have a good guess at an answer for this, if you disconnect for any reason you should not re-engage at all, you cannot proove why you disconnected, just that you did. As a result every disconnect should be treated as an F1 incident, and the rules applied. If this seems overly harsh, it is, but then every disconnect could be excused away if you let even one pass.
In other words...
Deal with it, and take their work for it?
Cheers:cool:
"Three o'clock is always too late or too early for anything you want to do."
People are way to quick to report others for f1'ing.
And fraps only works for the game......it doesn't record the crash to desktop.
FLHook is set to hang onto a ship for about a minute after someone f1's.
So, if ''thier body'' is setting in space for a minute, without any chat replies or ship movement, like turns....then they either crashed, f1'ed or got disconnected.
If my math is right....Just the 7 hours of playing last night, the server crashed 3 times.
A good way to handle this is just leave it up to the guy you are fighting. You get kicked, re-log after a min and ask. If he says no, tough break, there is always tomorrow. If he says yes then its on again.
When I see this happen to people I am fighting I let them back into the brawl if they can at least give a reasonable answer why they left. By the time they can log back in your shields are back up too so there really is no advantage to it. It is pretty obvious if they do it to escape death.
Crash happen. My FL crahs almost once every day. It usually happen during a dogfight (NPC or PC) or while i'm at base.
it happened once against Basilik. I log on explained the situation and reengaged.
It happened once against the NovaPG. I log on, typed "Sorry guy crash" and been exploded. So fair enough.
F1ing in a dogfight to come back 1min later is a suicide.
"Perfection, honesty, devotion" "Immortality is our subconscious main concern" "To change the system, you have to be inside the system and play by the rules"
a bit off topic but.. Ian try turning off the 3D Sound option in your freelancer option tab it "should" fix the problem...i had the same problem and this seemed to fix it.
IMO...If my system crashed,or if freelancer CTD (which xfire does on a regular basis to me),I would log back in and explain what happened.If I was sanctioned as for F1,I would become extreemly hostile,as I never F1 from combat.I have in the past had to disenguage combat due to 1). having my butt handed to me. 2). lag soooo bad that I cant hit anything, even at less than 300m.
The only 'grey areas' exist due to people being unable to see the difference between black and white.
.
.
.
Incase anyone missed my meaning, you CTD, BSD, disconnect, F1 etc and then try to re-engage me and you will be told bluntly to clear off and a sanction report will be sent in if you fail to do ask requested.
There are no loopholes in the rules, there are no grey areas either.
' Wrote:You BLOCADE the location where they logged off. I am very patient at these things.
unfortunately, the only time I did that, the guy never came back from the rest of the night. But I made some other good pirate catches meanwhile.
Yeah.. I remember one of those... some random merc in an Avenger F1ed in the minefield.. We had Avengers aswell, three of them. So, we just waited there... and when he popped in, KABLOWIE! Instakill.