littlewhitey's Servers Forum (SA-MP/VC-MP/MTA/Zomboid)
VC-MP Server - 51.38.93.130:8192 => VC-MP Reports => VC-MP Resolved Reports => Topic started by: ZayBee on April 07, 2016, 02:46:14 PM
-
Nickname: 958_Bolt^
Time and date (if known): 7 April 2016
Suspected method of cheat/exploit/rule break used: C-Glitch
Evidence: https://youtu.be/2YiSeryaerM (https://youtu.be/2YiSeryaerM)
Additional information: He was Constant Glitching for a long time even that he was warned.
-
Maybe i'm blind but I don't see any crouch glitching here. All I can see is the slide + fire uzi bug which is caused atm by 0.4 when holding the mouse button.
The same bug as in this video which isn't crouch glitch, it's a bug caused by players holding the fire button when they switch-glitch and its effected depending on how high the players ping is: https://vid.me/nYDR
-
The only people allowed to post in existing threads of the VC-MP Reports board are:
the player that has initiated the report
members of the staff
the reported player (if, by the time he decides to post, the thread is still open)
http://forum.littlewhiteys.co.uk/index.php/topic,19256.0.html (http://forum.littlewhiteys.co.uk/index.php/topic,19256.0.html)
-
Maybe i'm blind but I don't see any crouch glitching here. All I can see is the slide + fire uzi bug which is caused atm by 0.4 when holding the mouse button.
The same bug as in this video which isn't crouch glitch, it's a bug caused by players holding the fire button when they switch-glitch and its effected depending on how high the players ping is: https://vid.me/nYDR
Didn't know that a bug like that existed, it seemed to me that he was switching and sliding between spaz and mp5, Sorry for the false report, will consider re-checking my reports in the future.
-
Don't apologize, you never done anything wrong it's good that you reported a player that you thought was breaking the rules. Crouch glitching + this bug look very similar and it makes it a pain in the ass to distinguish between them. I mean, hopefully this bug gets removed in the next update but this bug in the video has been an on going issue for 0.4 for awhile now.