Players Sanctioned: Core| ships

[Garrett Jax]

Core|WV-Moorwen , Core|WV-Sargasso , Core|WV-Comnenos , Core|WV-Tangra and Core|WV-Athena have been sanctioned for:

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.

3.2 A player who was killed during a PvP fight in any form, must not enter the system where the fight took place or re-engage the attacker(s) for 2 hours from the time of their destruction, or until this/these ship(s) leave(s) the game.(There is a 5 minute window after death in which you can leave the system with an empty ship.)

Consequences: The video showing your assault on Freeport 11 revealed the violation of the above rules by many Core| players. Just to get this out of the way, because it was stated time and again just prior to every rule violation you all committed:

[01.05.2016 22:07:30] Core|WV-Comnenos: // We're not going in the NFZ.
[01.05.2016 22:07:53] [Admin]King.Boo: //I don't care. That's a RP thing. It's not against server rules.

This statement was in reference to the NFZ not being governed by server rules. It was not a carte blanche excuse for your faction to constantly violate your ID and basic rules of engagement. Nowhere in your ID does it allow you to attack a Zoner ship, unless he, by definition(half shields), attacks you. I don't think the guy landed a single shot before your group decided to blast him. And yes, he did reengage, for which he got Bastilled.

Next, you went toward Freeport 11 and attacked a Zoner Carrier, who never even fired a shot at you, nor was involved in the conflict. A clear ID violation.

Lastly, you didn't allow the Order vessel to leave the system in the allotted time before you decided to destroy him again.

We are sending your ships to Bastille for the time being, until we can discuss what action to take towards you. This is not the behavior we like to see in an Official Faction, and although some nice things came out of this incident, they could have still come about without the violation of server rules.

---

Original Link for Admin/Mod Use | Discovery Server & Forums Rules | Before You Post Here

---

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

---

[The Core]

I am posting here with permission from an admin.

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.

ID wise we can already kill Zoners. There are no ID infringements. The Zoner we shot prior had actually assisted Order in not only shooting an indie Mako (it undocked from the FP) but had proceeded to shoot Yaren/Bellona alongside The Order. I actually wanted to update our laws and our diplomacy chart to state Zoners were also hostile, but I've been banned and none of my HC are around when I need them to be.

3.2 A player who was killed during a PvP fight in any form, must not enter the system where the fight took place or re-engage the attacker(s) for 2 hours from the time of their destruction, or until this/these ship(s) leave(s) the game.(There is a 5 minute window after death in which you can leave the system with an empty ship.)

There is actually nothing rulewise that prevents the victor of a PvP engagement attacking a recently dead ship again. The ship had also been in the system for longer than 5 minutes. But actually that's not the reason why we shot it. There were so many targets that in the mess that we thought the Ossie was a new target and forgot that we had already shot it. It was a miscommunication error on our part, however as it is not against the rules I don't see how that would justify a sanction. If anything, a warning would be more fitting.

I am very interested to see what the report for this sanction, as it seems to have been very crude and poorly researched. I agree with the echoes of the community that these caps are absolutely essential to ensuring we can maintain consistent activity throughout this event and log in a way that doesn't result in us being utterly blasted to pieces. If the admins still feel we've committed a crime - even though rule wise there has been no infringements - I'd say we should receive a warning at most.

Furthermore in regards to my ban it's really starting to get in the way of ensuring this event can run smoothly both inrp and oorply. Whilst I am not requesting for my main account to be unbanned, I would like to propose that for the duration of this event I would be only allowed to post via The Core account in event threads, threads concerning Core in regards to this event, as well as the RP sections. I need to be able to respond to comms or cool any potential drama, as well as be able to update our laws and our diplomacy so people will not get confused. Whilst nominally I'd have my HC deal with things, most times they are either at school or are asleep or are away. I am very reluctant to randomly start promoting people to HC to make up for that. I can assure you that this sanction wouldn't exist if I was able to post and update stuff accordingly. Finally I would like to say how happy I am to see how the ooRP drama has greatly cooled down since this events inception. Alley and the rest of the staff are doing a fantastic job with the events, and people on both sides are having fun. We are blessed to have been able to create such a huge load of activity and help the server been so much more active than it has been ages, and we hope all the players can continue to enjoy the events and the fun that will follow.

Please do not be too harsh on these ships. They are legacy caps that have been passed down to us from BHG|Core. We feel that we have not made any rule infringements here, but at the least a warning in regards to shooting an Order ship followed by an update to the rules or green message would be suitable. We will certainly not shoot a vessel that is already PvP dead again.

---

[Jansen]

I am posting here with permission from an admin.

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.

ID wise we can already kill Zoners. There are no ID infringements. The Zoner we shot prior had actually assisted Order in not only shooting an indie Mako (it undocked from the FP) but had proceeded to shoot Yaren/Bellona alongside The Order. I actually wanted to update our laws and our diplomacy chart to state Zoners were also hostile, but I've been banned and none of my HC are around when I need them to be.

Yep, that is true, ID fix is on the way. EDIT: Also at the time of the report Zoners were not listed as hostile in any of your diplo or law things, they are still listed as neutral in your faction diplo. The law edit happened after the report.

3.2 A player who was killed during a PvP fight in any form, must not enter the system where the fight took place or re-engage the attacker(s) for 2 hours from the time of their destruction, or until this/these ship(s) leave(s) the game.(There is a 5 minute window after death in which you can leave the system with an empty ship.)

There is actually nothing rulewise that prevents the victor of a PvP engagement attacking a recently dead ship again. The ship had also been in the system for longer than 5 minutes. But actually that's not the reason why we shot it. There were so many targets that in the mess that we thought the Ossie was a new target and forgot that we had already shot it. It was a miscommunication error on our part, however as it is not against the rules I don't see how that would justify a sanction. If anything, a warning would be more fitting.

While there is no exact rule telling you to let people leave, there is also this bit in the rules

The intent behind these rules are for everyone to be excellent to one another. Consider the people around you. Keep fair play in mind.

The way the shooting looked in the evidence made me feel like you just shot that guy because you could and because its "THE FLAGSHIP!!!1!!!", there also didnt seem to be as many targets as you claim and even though one of your group members pointed out that the guy was killed and is leaving, which the Order ship himself did as well, you killed him again. Not an okay kind of behaviour from an official faction.

I am very interested to see what the report for this sanction, as it seems to have been very crude and poorly researched. I agree with the echoes of the community that these caps are absolutely essential to ensuring we can maintain consistent activity throughout this event and log in a way that doesn't result in us being utterly blasted to pieces. If the admins still feel we've committed a crime - even though rule wise there has been no infringements - I'd say we should receive a warning at most.

I have sent you the evidence, enjoy.

Furthermore in regards to my ban it's really starting to get in the way of ensuring this event can run smoothly both inrp and oorply. Whilst I am not requesting for my main account to be unbanned, I would like to propose that for the duration of this event I would be only allowed to post via The Core account in event threads, threads concerning Core in regards to this event, as well as the RP sections. I need to be able to respond to comms or cool any potential drama, as well as be able to update our laws and our diplomacy so people will not get confused. Whilst nominally I'd have my HC deal with things, most times they are either at school or are asleep or are away. I am very reluctant to randomly start promoting people to HC to make up for that. I can assure you that this sanction wouldn't exist if I was able to post and update stuff accordingly. Finally I would like to say how happy I am to see how the ooRP drama has greatly cooled down since this events inception. Alley and the rest of the staff are doing a fantastic job with the events, and people on both sides are having fun. We are blessed to have been able to create such a huge load of activity and help the server been so much more active than it has been ages, and we hope all the players can continue to enjoy the events and the fun that will follow.

You should have thought about having to use your posting abilities before doing something that got you banned, we are already making an exception to let you post here.

Please do not be too harsh on these ships. They are legacy caps that have been passed down to us from BHG|Core. We feel that we have not made any rule infringements here, but at the least a warning in regards to shooting an Order ship followed by an update to the rules or green message would be suitable. We will certainly not shoot a vessel that is already PvP dead again.

Considering that there is also the part where you destroy a Dragon Battleship with very minimal roleplay, we have decided to give the ships back, however, their guns stay in Bastille.

[The Core]

Yep, that is true, ID fix is on the way

The ID description reads this way so that the Core ID can deal with quasi-lawfuls and generic IDs when they commit a 'crime' outside of the standard Core Laws, and also when I am is unable to update them. The Order ID is pretty much exactly the same, as well as every other Lawful ID. I don't think it needs a 'fix' (as given the previous history of how the staff have handled IDs I'm cautious what a fix entails) but if anything placing a comma after 'quasi-lawuls' would help.

While there is no exact rule telling you to let people leave, there is also this bit in the rules

The intent behind these rules are for everyone to be excellent to one another. Consider the people around you. Keep fair play in mind.

The way the shooting looked in the evidence made me feel like you just shot that guy because you could and because its "THE FLAGSHIP!!!1!!!", there also didnt seem to be as many targets as you claim and even though one of your group members pointed out that the guy was killed and is leaving, which the Order ship himself did as well, you killed him again. Not an okay kind of behaviour from an official faction.

Well as I have said our intent was not malicious and it was a communication error. I had actually talked to the player on that ship on Skype afterwards to clear the air. A lot of us weren't paying attention to the group chats as we were communicating heavily through teamspeak. As I said, it was a communication error. A warning would be much more suitable for this sanction.

You should have thought about having to use your posting abilities before doing something that got you banned, we are already making an exception to let you post here.

I'm not a psychic. I didn't anticipate that this Zoner drama, that urgently needs an active leader presence, would erupt. If i had known this I asssure you I wouldn't have posted a bad meme.

Considering that there is also the part where you destroy a Dragon Battleship with very minimal roleplay, we have decided to give the ships back, however, their guns stay in Bastille.

Thank you. But the BD battleship was already shooting our Core ships when arrived. To all the caps it looked like it had begun to silently engage our ships, so we shot back at it.

---