Jump to content
GabeWad

ID 55 [NRP]

Recommended Posts

Player(s) being reported: ID 55
Date of interaction reported: 8/25/2019
Unix time stamp from HUD:1566792671

Your characters name: Brian Kwang

Other player(s) involved: None

Specific rule(s) broken: 8. Non-Roleplay (NRP)
 

  • Actions that are unrealistic or promote poor quality roleplay are considered as non-roleplay.

  • Examples of actions that are considered as non-roleplay:

• Cop Baiting - Provoking a reaction from emergency services without a realistic reason.

• Mercy Killing - Asking to be killed by a friend (Killing a friend falls under deathmatching).

• Unrealistic stunt jumping or the use of an expensive vehicle to ram into other vehicles.

• Spawning a scripted work vehicle and using it for crimes or submerging any vehicle in water.

• Swimming in water for an unrealistic amount of time or without a destination during a chase.

  • Players who disconnect during roleplay must reconnect and inform other parties in order to resume roleplay. If you are unable to reconnect it may be excused after providing proof.

  • In a situation where a player gets away from an incident where they're being chased/pursued, they must wait 15 minutes before they can logout. Players should not instigate roleplay situations if they do not have time to play it through. 

  • Players who ignore answering roleplay commands directed at them, e.g. /do.

  • In a situation where a player’s game crashes or the player is kicked from the server, they should be allowed to have the same advantages as they have had before their leave.


How did the player break the rule(s)?

As I was equipping my weapon to confront ID 55 I ended up desyncing off my bike and got injured. The individual came up to me to try and loot. I immediately tryed explaining to him in /ooc that I desynced/bugged off the bike and the reason why i was downed all the sudden. He ended up continuing to frisk me and take my items off my person and fleeing.
Evidence of rule breach:

https://youtu.be/6hIDMpyE5NE

  • Upvote 3
Link to comment
Share on other sites

PLAYER REPORT LOCKED FOR REVIEW

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

After reviewing this report and the evidence attached to it, I have decided to lock this report for review to gain a better understanding of the situation for the following reason(s):

  • Will be discussing internally before I finalize my decision.

You will be notified when we conclude this report. In the meantime, we ask that you remain patient and be respectful towards one another. If you have any questions, comments, or concerns that are related to this report, feel free to utilize the forum private messaging system to message involved players and/or staff members.

Regards,
Brawnkoh

Link to comment
Share on other sites

PLAYER REPORT DENIED

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

After reviewing this report and evidence attached to it, I have decided to deny this report for the following reason(s):

  • I will be the first to admit, I have had this happen to me and I know how frustrating it can be. However, I don't believe a rule was broken here, as only staff can pause RP. As such, another player does not have to abide by someone else's attempt to pause and/or change RP oocly unless directed to by staff. I did bring this to a couple of other mods to see if they felt the same way I did, and we seemed to agree on the outcome.

This decision is final. Unless instructed to, if you post another player report pertaining to this incident, you may be muted from posting on the forums for a temporary period. If you disagree with the outcome of this report, please file an appeal following the appeal guidelines and format.

Regards,
Brawnkoh

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.