Jump to content

ID 149 - (NLR, RDM)

Recommended Posts

Player(s) being reported: ID 149
Date of interaction reported: 14/06/2019
Unix time stamp from HUD: 1560462790

Your characters name: Patrick Ferrera

Other player(s) involved: ID 23

Specific rule(s) broken:

12. New Life Rule (NLR)

  • The new life rule is triggered whenever a player’s character spawns at a hospital. Players cannot force their own death.

  • The deceased character loses memory of their death, the events that caused it and the information collected in that time frame.

  • Example: A player is killed in a robbery. The player’s knowledge of the robbery, the robber and their death is not usable by the player in their new life.

  • All parties involved must avoid interaction with each other for 30 minutes. A player must not return to the area of their death for that time frame or attempt to retrieve lost possessions from involved players. An exception is made for government faction members who may provide a faction duty service, though their memory being lost and inability to retrieve assets still apply.


14. Deathmatch (DM)

  • Deathmatching is the act of attacking a player or their property without a proper roleplay reason.

  • 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 demands, attempt to escape, or call other players for help in a situation where they are required to display fear under fear roleplay rules.

  • 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 another player more than once including a failed attempt.

  • The act of killing a player with no engagement in roleplay is not allowed.

  • 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)?

During a pursuit we reach the interstate 1, where we see ID 191 murdering ID 149, completely finishing him off. We proceed to arrest him for Murder but after 5-6 minutes, ID 149 arrives back on scene, on a BF-400 as a passenger. The only thing we hear is ''Hands up motherfucker'' and not even after 1 second he opens fire on us, attempting to shoot up ID 191, RDM, for sure. We then manage to return fire, making them flee.

Evidence of rule breach:


Edited by KrismeisterSG
Link to comment
Share on other sites


Thank you for your patience, since reported party did not bother to defend, will use evidence as it is.

After reviewing the evidence in this report, I've decided to apply the following offenses to the following accounts:

  • Mike_Cupper | NLR, NonRP #1 | 
  • Mike_Cupper | DM # 1 |

Mike Cupper: Came back to the area he was killed and attempted to kill his killer without any proper roleplay reason since NLR was activated.

Kind regards,



You can appeal your punishment here: https://forum.eclipse-rp.net/forum/3-punishment-appeals/ 
Refund requests can be found here (25000$ minimum): 

Locked & archived

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.