Jump to content

ID 75 - Combat Log, NonRP

Recommended Posts

Player(s) being reported: ID 75
Date of interaction reported: 15/06/2019
Unix time stamp from HUD: 1560530900

Your characters name: Patrick Ferrera

Other player(s) involved: N/A

Specific rule(s) broken:

9. 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’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)?

Was getting in a pursuit with a Comet Retro who had a Charge for Murder of Gov. Employee but after the car crash against ID 75 I knew I would've lost him, so I approach him, changing my target, deciding to issue him a citation and demerit. The situation evolves into an OOC conversation where he claims ''desync'', like almost every other player does in the server, so I asked him for proof and he replies with, and I quote, ''man, why would I lie?''. He then proceeds to flee from me, like nothing happened, without any type of RP, trying to juke me and thinking that he would've sent me a clip where he showed me proof of his desync. After a little bit of time in the pursuit, he crashes, probably stalls and as soon as I approach he ALT F4's, leaving the game. I waited for 15 minutes with Kai Devito and Eleanor Quinn, they were with me the whole time during the waiting. I never met players like this, a big big big big fucking Y I K E S!

Evidence of rule breach:


Edited by KrismeisterSG
Link to comment
Share on other sites

Hello and thank you for making this report! @KrismeisterSG


After reviewing the footage and the logs I'd like to ask for the POVs of both the reported and the reporting side.


Player James_Fielding [ID: 75 @Fielding27- You stated that you logged back in but looking at the logs you never did. Could you explain to me what happened? 


Player Patrick_Ferrera [ID: 31 @KrismeisterSG- Could you explain to me why didn't you speak in-game whilst being in a TAC Frequency in TS? 


All of the above-stated players have 24 hours to respond to the report!


Best Regards,

Link to comment
Share on other sites

Hey, first of all, I'd like to thank both sides for responding within the given time frame.


@Fielding27 gave me a PM containing some information he'd like not to get shared here but it did help the situation somewhat. You had the officer's Discord and you could've, without issues, notified him of what was happening. 


With that all being said I'd like to give out the conclusion of this report

Player James_Fielding [ID: 75 @Fielding27- Will be receiving Non-RP Offence #5 for Combat logging and not notifying the participating party of it.

Player Patrick_Ferrera [ID: 31 @KrismeisterSG- Will be receiving a verbal warning for the usage of IC TAC channels without holding the N key, as told by department regulations. 


Thank you, once again, for making this report @KrismeisterSG

The report has been accepted and archived!


Best Regards,

Link to comment
Share on other sites

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.