Jump to content

valchucho

Member
  • Posts

    9
  • Joined

  • Last visited

Reputation

1 Neutral

1 Follower

About valchucho

  • Rank
    Newbie
    Newbie

Recent Profile Visitors

189 profile views
  1. First Last or PlayerID (Specific Rule Broken) ID 113 (Deathmatch, NRP) Required Report Format Player(s) being reported: ID 113 Date of interaction reported: 14/JUL/2021. Unix time stamp from HUD: 1626285076. Your character name: Robert Inchinelli Other player(s) involved: Rufnek Sooner(206), ID58, ID214, ID170 Specific rule(s) broken: Deathmatch (DM) Deathmatching is the act of attacking a player without a proper IC motive and interaction. Non-Roleplay (NRP) If a crash / disconnect occurs, players must post in the crash reports discord channel and contact all parties to resume. Players reconnecting must be given all opportunities held prior. How did the player break the rule(s)? (300 words maximum) ID113 ran to bayview and immediately started firing shots at the customers and mechanic on duty. While I was calling 911 they downed ID113 which is when he disconnected. (he did not report it in the ECRP Crash-Reports channel). According to the players involved no one had prior interaction with ID113 Evidence of rule breach: https://streamable.com/px465e
  2. Just chiming in to clarify. The reason i did the report is because i had already told Nick Tuffin OOCly that it was bug abuse, and caught him attempting it again later. The reason i decided to include Dutch Mortinson in the report was because it looked like he was aiding him in the rule break. I agree that a crime should be handled IC, however this had escalated beyond that given that Nick was told of the bug abuse already. I did file an in game report but by the time i got a response Nick was no longer on, so i was asked to take it to the forums. Id like to thank the Admins for handling this. Please let me know if you have any questions on the matter
  3. First Last or PlayerID (Specific Rule Broken) ID 248 and ID 61 (4.Hacking and Exploits) ID 248 (Bug Abuse) ID 61 (Assisting Bug Abuse) Required Report Format Player(s) being reported: ID 248, ID 61 Date of interaction reported: 27/JUN/2021. Unix time stamp from HUD: Your character name: Robert_Inchinelli Other player(s) involved: Revan_Ryder Specific rule(s) broken: 4. Hacking and Exploits Server bugs may not be used for advantage and must be reported on ECLIPSE Roleplay forums. How did the player break the rule(s)? (300 words maximum) When I first encountered the player he was in front of Bayview surrounded by employees accusing him of stealing cars out of the back. There is a bug that will cause the gates not to appear when you spawn in (some players are not aware of this so I try to inform them OOCly if I hear them mention their absence), so I told him that it is a bug and told him he would need to exit out and relog to correct it. He told me that he had already been made aware of it by someone (I don’t have recording of this encounter but it should show up in the logs). My next encounter was when I logged in hours later, in the back lot of Bayview and I see someone standing next to a Rebla then run through the gate when they see me. Not knowing it was the same player I made them aware of the buggy gates OOCly and informed everyone over the radio that someone was in the back. I got a better look at him when I went up front and recognized him since he was wearing the same outfit and mask. I PMd him which he then ran to his friend in the car and drove off. You can see all this in my POV. The other 2 videos were provided by Revan one in which you can hear him say that he did not see a fence but then acknowledges something there making him stuck, and a second where he got a car through the gate. He was informed that the gates were buggy multiple times and still continued to abuse it. Evidence of rule breach: My last encounter with the individual. https://streamable.com/lgzhgc Revan_Ryders encounters with the player ( 1624831805) (1624827673)
×
×
  • 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.