Open Rainnegan opened 5 years ago
Did they forgot to also add CS 1.6 issue tag or is this just for CZ?
@kisak-valve This is also tagged for CS 1.6/CZ.
You can make it by server side modules.
You can NEVER exced those values specially because legit players can't exced those values
Seems like you never had played mod's based on GoldSRC, it's also possible in 1.6 and in half-life and cs cz, it's also can be done server side plugins and other stuff, like https://wiki.alliedmods.net/Half-life_1_game_events#ScreenShake
So, there no limitation and that's expected(also no limit's for .z), for example you can see svencoop(which is official) and The Specialists - Half Life Mod gameplays and you gonna find this UNEXPECTED VALUES https://youtu.be/rW73fhu-vuM?t=147. @kisak-valve it's should be feature request, and that's not related to cs or cs cz at all.
Pls close fool issues.
You can make it by server side modules.
You can NEVER exced those values specially because legit players can't exced those values
Seems like you never had played mod's based on GoldSRC, it's also possible in 1.6 and in half-life and cs cz, it's also can be done server side plugins and other stuff, like https://wiki.alliedmods.net/Half-life_1_game_events#ScreenShake
So, there no limitation and that's expected(also no limit's for .z), for example you can see svencoop(which is official) and The Specialists - Half Life Mod gameplays and you gonna find this UNEXPECTED VALUES https://youtu.be/rW73fhu-vuM?t=147. @kisak-valve it's should be feature request, and that's not related to cs or cs cz at all.
Pls close fool issues.
Then add a punchangle calculation regarding viewangles that server can receive from CmdStart and problem resolved, if some user send a high value, disconnect him from server.
viewangles[0] = (Min: -89 Max: 89) +/- punchangle viewangles[1] = (Min: -180 Max: 180) +/- punchangle
PD: Don't be sad that your cheat will not working anymore: 2757 :)
You can make it by server side modules.
You can NEVER exced those values specially because legit players can't exced those values
Seems like you never had played mod's based on GoldSRC, it's also possible in 1.6 and in half-life and cs cz, it's also can be done server side plugins and other stuff, like https://wiki.alliedmods.net/Half-life_1_game_events#ScreenShake
So, there no limitation and that's expected(also no limit's for .z), for example you can see svencoop(which is official) and The Specialists - Half Life Mod gameplays and you gonna find this UNEXPECTED VALUES https://youtu.be/rW73fhu-vuM?t=147. @kisak-valve it's should be feature request, and that's not related to cs or cs cz at all.
Pls close fool issues.
So you're really getting mad because this guy is requesting many fixes to some already-known bug/exploits of this game. Sad to see that you're randomly tagging somebody as a noob in this topic because is offering solutions to something that has never been fixed before. You'll be surprised to see how this things will get fixed soon, so keep your arrogancy away telling developers to do what do you offer with no proofs at all
You can make it by server side modules.
You can NEVER exced those values specially because legit players can't exced those values
Seems like you never had played mod's based on GoldSRC, it's also possible in 1.6 and in half-life and cs cz, it's also can be done server side plugins and other stuff, like https://wiki.alliedmods.net/Half-life_1_game_events#ScreenShake So, there no limitation and that's expected(also no limit's for .z), for example you can see svencoop(which is official) and The Specialists - Half Life Mod gameplays and you gonna find this UNEXPECTED VALUES https://youtu.be/rW73fhu-vuM?t=147. @kisak-valve it's should be feature request, and that's not related to cs or cs cz at all. Pls close fool issues.
So you're really getting mad because this guy is requesting many fixes to some already-known bug/exploits of this game. Sad to see that you're randomly tagging somebody as a noob in this topic because is offering solutions to something that has never been fixed before. You'll be surprised to see how this things will get fixed soon, so keep your arrogancy away telling developers to do what do you offer with no proofs at all
Wouldn't be surprised if he blocks you now, if you go against him, he'll block you.
For some reason this dude doesn't want anything to be fix (Cheating related) and he's beign arrogant with his answers too.
Hope this gets fixed.
@kisak-valve Wondering how people like him are not banned already from the Github, we were having really friendly and decent discussions here on different feature request/issues and this guy keep trash-talking everyone pretending he knows everything, tagging Mike whenever he can without reason (that's harrasing?)
Hello again!, i adjunt the method that can detect all Anti-Aims hacks, just in case, to get the idea that i'm talking about (will be nice if someone can test if this is working correcly in all circustances, so we can approach to the solution!):
#include < amxmodx >
#include < fakemeta >
public plugin_init ( )
{
register_forward ( FM_CmdStart, "Fw_CmdStart", 0 )
}
public Fw_CmdStart ( const id, const uc_handle, const seed )
{
new Float:Angles[3]
get_uc ( uc_handle, UC_ViewAngles, Angles )
if ( ( Angles[0] > 89.0 ) || ( Angles[0] < -89.0 ) || ( Angles[1] > 180.0 ) || ( Angles[1] < -180.0 ) )
{
server_cmd ( "kick #%d ^"Anti-Aim Detected^"", get_user_userid ( id ) )
}
}
@mikela-valve High pitch angles (for example 180 degrees) are used by cheaters to desynchronize hitboxes and the visible player model. This can be clearly seen in the following video: YouTube
It would be good to limit the setting of the pitch angles [-89; 89] by players on the server side.
@mikela-valve OpenGL can be easy hooked by WallHack, you can remove OpenGL render and replace to 'DX10-12' to protect game ? (80% of all AIM BOTS/WH uses only OpenGL render)
There are limits on client to avoid excecing the angles limit:
cl_pitchdown "89" cl_pitchup "89"
You can NEVER exced those values, so there are players using hacks, specially "Anti-Aims" that changes the behaviour of his angles (goes more than 89 and less than -89) and completly destroy the gameplay.
cmd->viewangles.x = 178.0f; cmd->viewangles.y += 180.0f; // Example of Anti-Aim
A possible and secure solution to this will be limit the angles values from Server-Side (specially because legit players can't exced those values).