Faction Sanction: \V/

[Garrett Jax]

The \V/ faction has been sanctioned for:

Server Rule 1.3 Every player must have one ID equipped on their ship. Player should follow the restrictions and allowances listed in their ID and their roleplay and conduct must match the actions of their characters. In cases where these restrictions and allowances conflict with the server rules, the ID overrides the rules.

Consequences: You are not Liberty Police, yet you are using their ID. There is not an easy way to play the Vigilante role in this server, since the Vigilante ID was removed. Twisting an existing ID to try and make that role work is confusing for players and is misleading. You can either change your role play to Liberty Police or you change your ID. You have 48 hours to decide before we start towing your ships to Bastille.

Admin Link

COMPLETE SERVER RULES

BEFORE YOU POST

If you post in this sanction and are not directly involved or a leader of the accused person's faction be advised that you are consenting to be subjected to the reprisal of my choice which may involve in game repercussions up to a ban.
Blaming members of your immediate family, neighbours, friends, pets, and assorted Orcs, Trolls and any other legendary creatures may result in the use of Admin Right #CTE 750AE

---

[Vigilantes]

Oh, well, that's a new one.
We have to settle some things with a few people, we'll give the answer tomorrow.

---

[Evo]

Oh, well, that's a new one.

Myself along with many others were attempting to explain this to you for the longest time via the feedback thread rather than just shout for the admins immediately. I gave you ideas for you to continue doing what you do albeit a little restricted or requiring some set up if you wish to read back in the feedback thread. It won't be perfect but it will tide you over if you so desire if/until the Vigilante ID or a similar one is added once more. Good luck.

---

[Vigilantes]

@up
I meant that I haven't seen a faction-wide warning ever here.

@topic
http://discoverygc.com/forums/showthread...pid1592814

I suppose that's resolved then.

---