DoD Block Exploitsn- Version 2.4n- 11.06.2007n- original: FireStormn- updates: diamond-opticnnnCredits:n

- FireStorm: original DoD Block Exploits (v1.3)n- Gray Death: spectator fixn- Anthrax & DarkSnow: basis of setinfo checkn- TatsuSaisei: lots of help on new logging methodn- ucubed: decals thru walls client cvarn- VEN: error logging

Contains blocks/detection/fixes for the following:nn    - connecting client team fixn        * connecting clients should now show as spectators instead of appearing on a teamnn    - fullupdate command blockn        * blocks a command that can be used as an 'exploit' in some plugins.nn    - non-deployed MG reloadn        * blocks & detects when clients attempt an exploit that willn          allow them to reload an MG without having to deploy it firstnn    - pistol zoom blockn        * blocks the exploit/bug where clients can zoom in with their pistolnn    - respawn timer bypassn        * blocks & detects when clients try to bypass the respawn delaynn    - setinfo cheat tracesn        * scans a clients setinfo data when they join. Some known cheatsn          add specific traceable keys to a players setinfo when they run them.n          a detection doesnt mean 100% that they are cheating, but the chancesn          are likely that they are. it also means that they at least installedn          and ran the specific cheat at some point in the pastnn    - spectator duck bug fixn        * fix for the bug where sometimes when you die crouched, you have ton          press crouch again afterwards to get out of the spectator 'option'n          mode and whatnotnn    - spectator killingn        * blocks & detects when clients attempt to use the exploit that willn          allow them to be a 'spectator' and still kill people.n        * this is fixed according to the dod change log from 08.24.05, but youn          can still detect when a player attempts to use this exploitnn    - steam id pendingn        * checks a clients steam id when they join, if it returns a value ofn          STEAM_ID_PENDING, it waits 60 seconds and checks the steam id again,n          if the clients steam id still hasnt been auth'd it triggers this detectionnn    - third-person view fixn        * fixes a possible bug on player connect that allows players to ben          be in third-person view, which allows you to easily see around cornersnn    - white player modeln        * blocks & detects when clients attempt to use the exploit that makesn          their player model all whitenn    - decals thru wallsn        * theres a client cvar that can be set to allow players to see decalsn           (as in blood, bullet marks, explosions, etc) thru walls. This willn           lock that cvar at the default value.nn     - class limit bypass / white modeln         * there's a way to use the VGUI class selection menu to gain accessn            to a class that is full/turned off (mainly axis sniper)n         * a player using this exploit also spawns with a white player modelnnnLogs will be created daily in: addons/amxmodx/logs/dod_blockexploits/

- you should put this close to the top of your plugins.ini file, such asn  putting it underneath all the default plugins but before third-partyn  plugins works very well. Otherwise some third-party plugins might hookn  something before this plugin gets to block it.nn- Put the "dod_blockexploits.ini" file in "../amxmodx/configs/"

// Warning Messagendod_blockexploits_warnmsg "...Exploits/Cheats/Bugs are not welcome here!"nndod_blockexploits_warnwho "0"        // Who get warnedn                                     // 0 = guilty client onlyn                                     // 1 = guilty client & adminsn                                     // 2 = admins onlyn                                     // 3 = all clientsnnn// AMXBansndod_blockexploits_amxbans "0"        // Use AMXBansn                                     // 0 = offn                                     // 1 = onnnn// Spectator Killing CVARsndod_blockexploits_speckilling "2"    // Spectator Killing actionn                                     // 0 = silently blockn                                     // 1 = block w/ warning msgn                                     // 2 = kickn                                     // 3 = banndod_blockexploits_speckilling_log "1"    // Log Spectator Killing detectionsn                                         // 0 = offn                                         // 1 = onndod_blockexploits_speckilling_ban "60"   // Spectator Killing ban time in minutes (if set to ban)nnn// White Player Model CVARsndod_blockexploits_whitemodel "2"    // White Player Model actionn                                    // 0 = silently blockn                                    // 1 = block w/ warning msgn                                    // 2 = kickn                                    // 3 = banndod_blockexploits_whitemodel_log "1"    // Log White Player Model detectionsn                                        // 0 = offn                                        // 1 = onndod_blockexploits_whitemodel_ban "60"   // White Player Model ban time in minutes (if set to ban)nnn// Respawn Timer Bypass CVARsndod_blockexploits_respawntimer "0"    // Respawn Timer Bypass actionn                                      // 0 = silently blockn                                      // 1 = block w/ warning msgn                                      // 2 = kickn                                      // 3 = banndod_blockexploits_respawntimer_delay" "15"  // Respawn Timer Bypass delay (in seconds)n                                            // This controls the amount of timen                                            // before the client can rejoin a team.n                                            // 15seconds is the default dod spawn timen                                            // but you might want to increase it ton                                            // make it more of a punishment for trying.ndod_blockexploits_respawntimer_log "0    // Log Respawn Timer Bypass detectionsn                                         // 0 = offn                                         // 1 = onndod_blockexploits_respawntimer_ban "5"   // Respawn Timer Bypass ban time in minutes (if set to ban)nnn// Non-Deployed MG Reload CVARsndod_blockexploits_mgreload "1"        // Non-Deployed MG Reload actionn                                      // 0 = silently blockn                                      // 1 = block w/ warning msgn                                      // 2 = kickn                                      // 3 = banndod_blockexploits_mgreload_log "1"    // Log Non-Deployed MG Reload detectionsn                                      // 0 = offn                                      // 1 = onndod_blockexploits_mgreload_ban "60"   // Non-Deployed MG Reload ban time in minutes (if set to ban)nnn// Setinfo Traces CVARsndod_blockexploits_setinfo "1"        // Setinfo Traces actionn                                     // 0 = do nothingn                                     // 1 = show warning msgn                                     // 2 = kickn                                     // 3 = banndod_blockexploits_setinfo_log "1"    // Log Setinfo Traces detectionsn                                     // 0 = offn                                     // 1 = onndod_blockexploits_setinfo_ban "180"  // Setinfo Traces ban time in minutes (if set to ban)nnn// Steam ID Pending CVARsndod_blockexploits_idpending "2"        // Steam ID Pending actionn                                       // 0 = do nothingn                                       // 1 = show warning msgn                                       // 2 = kickndod_blockexploits_idpending_log "1"    // Log Steam ID Pending detectionsn                                       // 0 = offn                                       // 1 = onnnn// Class Limit Bypass / White Player Model CVARsndod_blockexploits_limitbypass "2"      // Class limit bypass / white model actionn                                       // 0 = silently blockn                                       // 1 = block w/ warning msgn                                       // 2 = kickn                                       // 3 = banndod_blockexploits_limitbypass_log "1"       // Log Class limit bypass / white model detectionsn                                            // 0 = offn                                            // 1 = onndod_blockexploits_limitbypass_ban "120"     // Class limit bypass / white model ban time in minutes (if set to ban)nnn// Third Person View Blockndod_blockexploits_thirdperson "1"    // Third Person View Settingn                            // 0 = Disablen                            // 1 = Enable (Block)n

- Default admin level is ADMIN_KICK

- 12.26.06 - Version 1.4n    added public tracking cvarn    replaced some if statements with switchesn    fixed mistake in respawn timer handlingn    cleaned up code a bitnn- 05.28.07 - Version 2.0n    Rewrote almost everything...n    Added fix for spectator duck bugn    Added fix for connecting players showing up on a teamn    Added check for cheat traces in setinfo linesn    Added Steam ID Pending checkn    Added FullUpdate blockn    Logs are now daily and in their own foldernn- 06.04.07 - Version 2.1n    Fixed banning function.. stupid me :Pnn- 08.07.07 - Version 2.2n    Third Person View block actually works nown    Added block for seeing decals thru wallsn    Added block for class limit bypass (and white model)n    Added control over who will see the warning msgnn- 09.23.07 - Version 2.3n    Added CVAR to control third-person view blockn    Removed detection for decals thru walls (now it just blocks)n    Now using an INI file to set the detection namesn    Removed some junk left over from previous versionsnn- 11.06.07 - Version 2.4n    Updated INI file * important *n    Removed the pointless 'fullupdate' loggingn    Removed 'fullupdate' block console msg (showed when recording demos)n    Enhanced INI file checking & error loggingn    Removed some old unused coden    Reduced some msg sizes due to words being cut offn    Added compiler define for new amxx 1.8.0+ log title formatn

well you dont 'have' to persay.. cause if you dont they will just use the default values, which i think all those are showing..nnbut yeah, if you want, or if you want to change them... just copy and paste them into the amxx.cfg file

oh damn im sorry i somehow missed that post..nni'll try to add customizable ban/kick reasons this weekend (or maybe monday or tuesday lol) and get that up here

ok ive found a bit of a mistake...nnok a pretty big mistake actually lol...nnnnthe decals thru walls detection can give false detection if a client does exec config.cfg mid-gamennso in the next version im taking out the detection and replacing it with just blocking as i wasnt able to figure out anyway to detect what value clients entered..nnso i would suggest until then that you might want to set dod_blockexploits_decals to 0 to silently block the use of the cvar but not kicking/banning/warning about itnnhopefully over the next day or two ill have an update ready..nnnreally really really sorry bout this lol

also superbulette.nordendnnjust to get more information on what your looking for...nndo you want to be able to customize the WHOLE message for each thing..? or just part of it?nnlike say for spectator killing, it should say this:nnExploit/Cheat/Bug NOT allowed! (Spectator Killing)nn..like do you mean just the Exploit/Cheat/Bug NOT allowed part? or the actual reason in ( ) too? lol it would be a lot easier for me lol to do the 1st part in a way..nnncause right now the message is: Exploit/Cheat/Bug NOT allowed! (%s)n..where %s gets filled in with the actual thing detected and i could easily make it so you can have whatever you want there, and if you decide to include %s it will show the actual detection..nnlike you could set it to just "%s" and it would say: Spectator Killingnor you could set it to "Detected %s" and it would say: Detected Spectator Killingnor you could set it to "Detected Exploit" and it would just say: Detected Exploit ..without saying whichnni could do the other way where you can customize the actual detection name, but it would just be more work then i rather do lol (but i guess ill do it lol if you really want that)nni think what i wrote is probably confusing right there lolnn* edit *nnoh wait looking in the code (lol i should do that more often before i post lol) i see that if you have the amxbans setting on it puts just the detection name and not the Exploit/Cheat/Bug part.. so im gonna assume you want to be able to customize the actual detection names right?nnunless if i make the Exploit/Cheat/Bug msg part customizable and include that in the amxbans reason, then you should be able to put like: WhateverYouWant (%s) as the amxbans reason and %s will be the detection name..nnndamn i just confused the hell outta me.. i should rethink what im trying to say and try to post again in an understandable way.. maybe you can help me out by giving me an example of what you would like it to say specifically for you for say Spectator Killing detection..nnor do you want a totally customizable message for each specific one? cause now that i think of it.. i should just do that lol

how would it do that?nntheres no way to monitor what people download and scan what it is, especially if they dont use it lol

im a bit confused by exactly what you mean...

depends what you mean by 'cheat'nnand no matter what you mean by it exactly.. most 'cheats' arent detected by this

lol i wouldnt put much faith in VAC either...nnthe best tool is experienced admins :P

the way most cheats work theres no way that amxx would be able to do anything at all concerning them..nnVAC could probably block/detect a lot of them.. if VAC itself was 'really' worked on and updated.. plus im sure those at valve are only concerned with source game cheats.. i wouldnt be surprised if they figure letting HL1 engine games have an abundance of cheats will bring more people to the source engine (especially if they focus on source engine cheats)

nUpdate To Version 2.3nn* it is highly recommended that you update to this version due to false detections with the previous one *n n

- 09.23.07 - Version 2.3n    Added CVAR to control third-person view blockn    Removed detection for decals thru walls (now it just blocks)n    Now using an INI file to set the detection namesn    Removed some junk left over from previous versions

i d used V2.3 dod_blockexploits_1.75a on my server but dod_blockexploits_stats is still "2.2" :confused:

is there no .sma file with this plugin?

hmm i just checked inside the .amxx file and its definitly showing 2.3

will probably post an update tomorrow along with a 1.8.0 compiled version (tho 1.76d probably works fine) just as a head up :)

Update To Version 2.4nnHighlights:n

- AMXX 1.8.0 supportn- Enhanced INI Checking

- 11.06.07 Version 2.4n    Updated INI file * important *n    Removed the pointless 'fullupdate' loggingn    Removed 'fullupdate' block console msg (showed when recording demos)n    Enhanced INI file checking & error loggingn    Removed some old unused coden    Reduced some msg sizes due to words being cut offn    Added compiler define for new amxx 1.8.0+ log title formatn

works fine D-O !

sure i'd love to hear about it :)

well for the most part.. i believe that has to do with the brushwork in the map and cant truly be fixed without the map sourcenni did once have a few ideas for trying to fix some of the nade & rocket exploits in avalanche, but it proved to be more work then i felt like doing lol

i dont think thats really something that fits in with this plugin.. but i see wilson replied to your thread :)nnn.......nnbut anyway i got a question.. nndoes anyone use this plugin with amxbans?? im just trying to get amxbans going for my servers and after dealing with numerous problems all last night and today i thought i was finally getting somewhere.. till i decided to test the block exploits amxbans stuff..nnwhen i trigger something, it will say im banned and adds me to the amxbans sql db.. BUT it doesnt actually kick me..nnand whats wierd is if i manually put in the exact code the plugin uses (amx_ban time steamid reason) it works fine.. but for some reason it doesnt when the plugin does it..nnthis is using amxbans 5.0nnif anyone else could let me know if it works or doesnt work for you that would be swell :)nn**edit**nnok maybe its a problem with amxbans.. when i try to use amx_ban in rcon via HLSW, it adds the ban but doesnt kick the player :-

ok i fixed the amxbans problem...nnwas a problem with the actual code for amxbans itself..nnnbasically what was happening is when the server itself uses amx_bans it has an id of 0, but the amxbans code was trying to get the team of the id that called the ban but since it was the server it threw and error and the plugin stopped..nnso i fixed this and it works now, i also posted about it on the amxbans forums, tho i wouldnt be surprised if its ignored :-
n...anyway i want to add that ive had a new version of this plugin going thru live testing for the past week or two and it should be ready for another public update anytime now :-)

ya thats something ive forgot to do several times now lol..

ok so far here's a little news i guess lol..nnwith the pistol zoom, i cant seem to find any way to detect it (the plugin basically resets the fov value when switching off of a sniper rifle) ..i tried a few different things but nothing actually gave fov values of being zoomed in while using the pistol zoom.. i can probably try a few more things once i get a chance, such as wilson's scoped stock tho im not so sure if it will worknnnAs for not blocking certain exploits...nn** these should work with the current released version, but on the next update i'll add it to the comments **nn> with the dod_blockexploits_warnwho cvar, setting to -1 will not warn anybodynn> setting these cvars to -1 will make their detections do nothing (the logging cvars for each still function tho)n * dod_blockexploits_speckillingn * dod_blockexploits_whitemodelnnn** these ones will NOT work till the update is released **nn> settings these cvars to -1 will make their detections do nothing (the logging cvars, again, will still function)n * dod_blockexploits_respawntimern * dod_blockexploits_mgreloadn * dod_blockexploits_limitbypassnnnnit would kind of look better to redo the cvar settings and have all them set to 0 to do nothing and 1 to silently block and so on.. but i think it might be best to not mess around with changing cvar settings that way right now to avoid forcing everyone to redo their settings or risk having different actions happen then what they want..nnBUT!!! the plugin is getting a bit LARGE and confusing as well lol.. and its not commented too well anymore so i get lost sometimes.. so i do plan during the beginning of next year to really go thru it and basically re write it over again cleaning it up and making lots of comments, redoing the cvars (maybe have warnwho cvars for each one to be more specific on which are important enough to warn just admins or all players etc), and using seperate *.inl files to keep it a bit organized.. Would really help me work on specific things without dealing with all the code at once and would probably be easier to add new things as well... But that will be version 3.0.. so up till and during the progress on that i'll still do updates to 2.x when needed :-)

hmm if you see ppl join and leave right away because of something... it should show in the logs (if logging is on for whatever it is)nnand the non deployed mg reload could be triggered 'accidently' ..id explain why but i dont wanna post how to actually do the exploit... so its best to set that to block but not kick/ban (as the default setting is set to).. well in a sense some players could trigger a few of these accidently.. but getting the same ones from the same players over and over again i would think are likely not accidentalnni should make note of which settings are reccommended for each one (besides the default settings) at some point when i have a chance

just wanna post some news about this plugin...nni know i said i would fix/add a few things a put up a v2.5 while working on the re-write v3.0 but since i dont have much time i basically skipped doing the v2.5 update.. Plus there was really no point in me bothering with new stuff in the mess that v2.4 is. So im sorry about thatnnBUT!nnthe good news is ive got v3.0 basically ready :D spent the whole evening/night today finishing it up (i started it nearly 2 months ago, just didnt have time to keep up working on it) SOOOO right now ive got an alpha version that i tested myself and all seems to work good and im gonna run it on my server for a couple days as an alpha. Then I'll most likely post it as a beta and let anyone interested help with the final testing to make sure it all works properly and to see if theres anything else that can or needs to be done to it before making v3.0 final.. That will hopefully prevent it being released with any problems.nnthere is also a few things in it that im not sure if i like the way i have it setup but nothing too major. I was also planning on adding a feature for it to check if the server is running the latest version, but that might get postponed till v3.1 or somethingnn...also want to make note that I havent totally decided if i want to keep backwards compatibility with older AMXX versions. Tho im sure there's plenty of you that will want this as i see it was downloaded quite a bit for pre-1.8.x AMXX.. but there really is no reason for anyone to be using anything older then 1.76d, but i guess if i keep compatibility for that theres really no reason not to compile it for older ones that it should still work with.nnanyway I just wanted to let anyone interested know that progress is being made and its almost ready for a release :)

damn i didnt expect such a fast response hahahnnsounds good :)nnn...most likely a beta will be posted early this week, i hope.. depends if lazyness sets in again or not

ehh im running a bit behind on this.. nnndue to a recent increase in crashes on my server im gonna hold off for a bit and make sure its not cause of this plugin.. as its the only one ive really been working on and changing lately

nVersion 3.0 Final is now available for download...nnnCLICK HEREnnn