I have... well, had... a 400Cr bounty on my head for accidentally zapping a pirate before the scan had explicitly identified him, so after the scan did ID him, I finished him off and left for the local starport, feeling pretty confident, from previous experience, that the small bounty would not disallow docking.
On approach to the starport I requested and was given docking permission. Then, just as I was about to enter the cage, ships outside (presumably the fuzz) started shooting at me and the PROCEED TO LANDING BAY 22 disappeared and, as I entered to starport, TRESPASS WARNING appeared. I left immediately (and with time to spare) and my ship was then rapidly destroyed outside. I have a vid to show all of this.
I accept that the fuzz would fire upon a WANTED player, but I've not seen docking permission being revoked and becoming a TRESPASS WARNING before.
Is this a new feature?
{Edit: I see that I know have a dormant bounty of all of 435Cr for the next nearly 7 days. Is this how minor infractions are being dealt with now?)
On approach to the starport I requested and was given docking permission. Then, just as I was about to enter the cage, ships outside (presumably the fuzz) started shooting at me and the PROCEED TO LANDING BAY 22 disappeared and, as I entered to starport, TRESPASS WARNING appeared. I left immediately (and with time to spare) and my ship was then rapidly destroyed outside. I have a vid to show all of this.
I accept that the fuzz would fire upon a WANTED player, but I've not seen docking permission being revoked and becoming a TRESPASS WARNING before.
Is this a new feature?
{Edit: I see that I know have a dormant bounty of all of 435Cr for the next nearly 7 days. Is this how minor infractions are being dealt with now?)
Last edited: