28.02.2018, 01:43
This isn't possible with weapon hacks and ammo, i tested this long time with serversided and cheats override Reseting weapons etc. The checks work but you cannot force the cheater unfortunately.
Well as you're already using OPU, you could just check for a weapon change in OPU, an if there 'is indeed' a change in weapon you could then call your external function to check if the new weapon is stored in the enumerator and ban/kick if not.
As already stated, resetting and setting the weapons continuously will have no effect.. you're better off to just ban/kick offenders as minigun user can kill a whole bunch of players in 3 seconds. |
Nope i still dont get what youre trying to say here and im pretty sure no one does, how's that going to cause any problems when he returned the same function? Hows it supposed to look like then??
|
stock wSetPlayerAmmo(playerid, weapon, ammo)
{
weaponsInfo[playerid][Ammo][weapon] = ammo;
if(!weaponsInfo[playerid][wImmune]) SetTimerEx("wResetImmune", 3000, false, "i", playerid);
weaponsInfo[playerid][wImmune] = true;
return SetPlayerAmmo(playerid, weapon, ammo);
}
weaponsInfo[playerid][Ammo][weapon] = ammo;
If you pass an invalid ID (higher than MAX_PLAYERS or max weapon slots) to this function: (let it be playerid, or weapon id)
PHP код:
PHP код:
|
You could combine all your includes without having to deal with a large file, just create separate files, then include them to the main anti cheat file with options to disable certain anti cheats.
This way there'll be no maintaining difficultly, as well as you can include the anti laggers include as a must for users which you say it helps your other anti cheats to not false detect laggers. |
Originally Posted by RogueDrifter
Well that really wouldn't matter much at the moment as using all of the includes none of them will affect the other, meaning you can simply download+include all and they'll still work, i'll say it would be better for you as a user to use one include that links the anticheats to one system but there's a reason that i didn't do that.
The reason that i'm breaking my releases into separates is that it: 1- Motivates me to keep going & releasing more 2- Helps me find bugs a hella lot easier 3- Is more clear & short code to look through That's why my includes work safely, I've had good time creating, testing and fixing them, you'll see that they hardly return false positives and if they do you'll see me updating it immediately. Rest assured that Pottus has already caught my attention on the fragmented releases part and i will start working on an all-in-one system soon. |
V1.2 - Added type #4, anti ammo freeze aka infinite ammo aka no reload.