Jump to content
reeceobz

ID 134 DM

Recommended Posts

Player(s) being reported: ID 134
Date of interaction reported: 19/02/2019
Unix time stamp from HUD: 1582130342

Your characters name: Reece Curry

Other player(s) involved: N/A

Specific rule(s) broken:

14. Deathmatch (DM)

  • Deathmatching is the act of attacking a player without a proper roleplay reason and interaction.

  • Examples of valid reasons to attack another player:

• If they attempt to arrest or hurt you, an ally, or damage your property.

• If they report you to the police for a serious crime.

• If they are not in compliance with plausible demands, attempt to escape, or call backup.

  • A player cannot kill their victim if the victim is in compliance with the demands.

  • A player must allow their victim enough time to comply with the demands.

  • If a player informs you that your VOIP isn’t working, you must either fix your VOIP using appropriate commands or use text to deliver your demand(s).

  • Vehicles cannot be used to attack a player on foot more than once, including a failed attempt.

  • Killing a player that has obeyed all orders and demands during a roleplay situation is allowed, with roleplay, only within 3 hours of:

    1.  Severe hostile or criminal action is taken against you, e.g. someone is robbing you at gunpoint. (Excluding police aiming a gun at you.)

    2.   Someone is attempting to take your life.

    3.   Someone is attempting to take the life of your close friend or ally, or if you have witnessed it happen.

  • You must explain your reason to kill to the player IC and have OOC evidence proving your reason.

How did the player break the rule(s)?

Started shooting me with no interaction or a valid reason to open fire. 

Evidence of rule breach:

https://streamable.com/iwvd2

4e156486bc1713a3075c97c537241ef5.png

Link to comment
Share on other sites

Thank you for submitting this report, and be patient as we review the evidence and allow all parties involved to respond. 

After reviewing this report and the evidence attached to it, I have decided that this report cannot be concluded at this time. We will make inquiries on players involved to obtain relevant details to reach a decision. Please stand by.

Kind Regards,
Sr. Support krooks365

Moderator Jasmine  

Link to comment
Share on other sites

Thank you for your patience as we reviewed the report. Prior to concluding this report, we would like to hear statements from the players as specified below

  • Constantine_Smirnov | ID 134 -  Please provide your POV on this situation if you have it and explain your involvement within it. Why can you be observed shooting the OP with seemingly no prior interaction.

The above mentioned players will be notified in game as appropriate and will receive 24 hours to provide their side of the story. We look forward to hearing back from you!

Jasmine and Krooks365

Link to comment
Share on other sites

Thank you for your patience while this report was under review.

After reviewing this report and evidence attached to it, I've decided to accept this report and issue punishment(s) to the following player(s)

Constantine_Smirnov [ID 134] - Death Matching #1 | Attacking without Valid Reason -  Per the provided evidence there was no RP interaction that would have given you rights to shoot at the OP in the way that you did. This puts you in breach of DM rules and that is why you are receiving this punishment today.

If you have received a punishment that you disagree with, feel free to file a punishment appeal following the punishment appeal guidelines and format. If the reporting party suffered a loss greater than $25,000 in value, feel free to file a refund request following the refund request guidelines and format. 

Regards,

Jasmine and Krooks365

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.


×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and our Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.