(11-14-2016, 01:55 PM)Haulerman Wrote: Sometimes (often) i and several others i have talked to in the past are like: "freck" i didnt even had time to respond properly before they shot warningshots on my shield!!
And then i get even more stressed and it all colapses to a gigantic beutiful transport explosion in less then 30 sec....
What you describe is not a set-msg problem, but a sanctionable player rule break.
Being pirated successfully:
Pirate CDs you, you halt. You immediately write "I stopped!". Take a picture with you on 0 speed and your line. Why? If he kills you now bc he is hunting for blues, is a lolwut or whatever... you can easily sanction. You have to be fast! 30 seconds to write 2 words should be a maximum you safely have.
He makes a demand. Screen the demand. If he does not make a demand and shoots you, you sanction him.
If he does not give you time to answer to the demand, sanction him.
As long as the pic shows that you were not "running away" (see step above) you will get him in the sanction IF he shoots you without demand or when he does not give you enough time to answer... IF you are not running away. If you are moving during that time, a pirate can kill you and he is right in doing so.
Comply to the demand if it is not outrageous. Pirates are part of the game. If the demand is outrageous (like... 15 mils from an empty T), screen the demand and report it. Admins will decide (demanding all your cargo is NOT a sanctionable demand, by the way).
If it is a normal demand, hey... play and pay. Or run for base, or fight... Disco would be bad without a threat.
If you were killed in anything that was not clean piracy, collect your screens, also the one of your own blue message.
Then log to your dsace.log, which holds exact time stamps for every line that was written. This way, it becomes clear whether enough time was given between demand and kill. Copy paste the whole encounter into the report...
Et voila... get a sandwich if you feel upset about what happened, and play somewhere else.