DoD Block Exploits (v2.4)

[diamond-optic]

DoD Block Exploits
- Version 2.4
- 11.06.2007
- original: FireStorm
- updates: diamond-optic


Credits:
- FireStorm: original DoD Block Exploits (v1.3)
- Gray Death: spectator fix
- Anthrax & DarkSnow: basis of setinfo check
- TatsuSaisei: lots of help on new logging method
- ucubed: decals thru walls client cvar
- VEN: error loggingInformation:
Contains blocks/detection/fixes for the following:

- connecting client team fix
* connecting clients should now show as spectators instead of appearing on a team

- fullupdate command block
* blocks a command that can be used as an 'exploit' in some plugins.

- non-deployed MG reload
* blocks & detects when clients attempt an exploit that will
allow them to reload an MG without having to deploy it first

- pistol zoom block
* blocks the exploit/bug where clients can zoom in with their pistol

- respawn timer bypass
* blocks & detects when clients try to bypass the respawn delay

- setinfo cheat traces
* scans a clients setinfo data when they join. Some known cheats
add specific traceable keys to a players setinfo when they run them.
a detection doesnt mean 100% that they are cheating, but the chances
are likely that they are. it also means that they at least installed
and ran the specific cheat at some point in the past

- spectator duck bug fix
* fix for the bug where sometimes when you die crouched, you have to
press crouch again afterwards to get out of the spectator 'option'
mode and whatnot

- spectator killing
* blocks & detects when clients attempt to use the exploit that will
allow them to be a 'spectator' and still kill people.
* this is fixed according to the dod change log from 08.24.05, but you
can still detect when a player attempts to use this exploit

- steam id pending
* checks a clients steam id when they join, if it returns a value of
STEAM_ID_PENDING, it waits 60 seconds and checks the steam id again,
if the clients steam id still hasnt been auth'd it triggers this detection

- third-person view fix
* fixes a possible bug on player connect that allows players to be
be in third-person view, which allows you to easily see around corners

- white player model
* blocks & detects when clients attempt to use the exploit that makes
their player model all white

- decals thru walls
* theres a client cvar that can be set to allow players to see decals
(as in blood, bullet marks, explosions, etc) thru walls. This will
lock that cvar at the default value.

- class limit bypass / white model
* there's a way to use the VGUI class selection menu to gain access
to a class that is full/turned off (mainly axis sniper)
* a player using this exploit also spawns with a white player model


Logs will be created daily in: addons/amxmodx/logs/dod_blockexploits/Installation:
- you should put this close to the top of your plugins.ini file, such as
putting it underneath all the default plugins but before third-party
plugins works very well. Otherwise some third-party plugins might hook
something before this plugin gets to block it.

- Put the "dod_blockexploits.ini" file in "../amxmodx/configs/"CVARs (amxx.cfg):
// Warning Message
dod_blockexploits_warnmsg "...Exploits/Cheats/Bugs are not welcome here!"

dod_blockexploits_warnwho "0" // Who get warned
// 0 = guilty client only
// 1 = guilty client & admins
// 2 = admins only
// 3 = all clients


// AMXBans
dod_blockexploits_amxbans "0" // Use AMXBans
// 0 = off
// 1 = on


// Spectator Killing CVARs
dod_blockexploits_speckilling "2" // Spectator Killing action
// 0 = silently block
// 1 = block w/ warning msg
// 2 = kick
// 3 = ban
dod_blockexploits_speckilling_log "1" // Log Spectator Killing detections
// 0 = off
// 1 = on
dod_blockexploits_speckilling_ban "60" // Spectator Killing ban time in minutes (if set to ban)


// White Player Model CVARs
dod_blockexploits_whitemodel "2" // White Player Model action
// 0 = silently block
// 1 = block w/ warning msg
// 2 = kick
// 3 = ban
dod_blockexploits_whitemodel_log "1" // Log White Player Model detections
// 0 = off
// 1 = on
dod_blockexploits_whitemodel_ban "60" // White Player Model ban time in minutes (if set to ban)


// Respawn Timer Bypass CVARs
dod_blockexploits_respawntimer "0" // Respawn Timer Bypass action
// 0 = silently block
// 1 = block w/ warning msg
// 2 = kick
// 3 = ban
dod_blockexploits_respawntimer_delay" "15" // Respawn Timer Bypass delay (in seconds)
// This controls the amount of time
// before the client can rejoin a team.
// 15seconds is the default dod spawn time
// but you might want to increase it to
// make it more of a punishment for trying.
dod_blockexploits_respawntimer_log "0 // Log Respawn Timer Bypass detections
// 0 = off
// 1 = on
dod_blockexploits_respawntimer_ban "5" // Respawn Timer Bypass ban time in minutes (if set to ban)


// Non-Deployed MG Reload CVARs
dod_blockexploits_mgreload "1" // Non-Deployed MG Reload action
// 0 = silently block
// 1 = block w/ warning msg
// 2 = kick
// 3 = ban
dod_blockexploits_mgreload_log "1" // Log Non-Deployed MG Reload detections
// 0 = off
// 1 = on
dod_blockexploits_mgreload_ban "60" // Non-Deployed MG Reload ban time in minutes (if set to ban)


// Setinfo Traces CVARs
dod_blockexploits_setinfo "1" // Setinfo Traces action
// 0 = do nothing
// 1 = show warning msg
// 2 = kick
// 3 = ban
dod_blockexploits_setinfo_log "1" // Log Setinfo Traces detections
// 0 = off
// 1 = on
dod_blockexploits_setinfo_ban "180" // Setinfo Traces ban time in minutes (if set to ban)


// Steam ID Pending CVARs
dod_blockexploits_idpending "2" // Steam ID Pending action
// 0 = do nothing
// 1 = show warning msg
// 2 = kick
dod_blockexploits_idpending_log "1" // Log Steam ID Pending detections
// 0 = off
// 1 = on


// Class Limit Bypass / White Player Model CVARs
dod_blockexploits_limitbypass "2" // Class limit bypass / white model action
// 0 = silently block
// 1 = block w/ warning msg
// 2 = kick
// 3 = ban
dod_blockexploits_limitbypass_log "1" // Log Class limit bypass / white model detections
// 0 = off
// 1 = on
dod_blockexploits_limitbypass_ban "120" // Class limit bypass / white model ban time in minutes (if set to ban)


// Third Person View Block
dod_blockexploits_thirdperson "1" // Third Person View Setting
// 0 = Disable
// 1 = Enable (Block)
Extra:
- Default admin level is ADMIN_KICKChange Log:
- 12.26.06 - Version 1.4
added public tracking cvar
replaced some if statements with switches
fixed mistake in respawn timer handling
cleaned up code a bit

- 05.28.07 - Version 2.0
Rewrote almost everything...
Added fix for spectator duck bug
Added fix for connecting players showing up on a team
Added check for cheat traces in setinfo lines
Added Steam ID Pending check
Added FullUpdate block
Logs are now daily and in their own folder

- 06.04.07 - Version 2.1
Fixed banning function.. stupid me :P

- 08.07.07 - Version 2.2
Third Person View block actually works now
Added block for seeing decals thru walls
Added block for class limit bypass (and white model)
Added control over who will see the warning msg

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

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


Download Mirror: http://www.avamods.com/download.php?view.154


** this is a CLOSED SOURCE plugin, as approved by bailopan.. there is no sma available for public download **

download the attachment that corresponds to the AMXX version you are running.... but be warned this is written for and tested on AMXX 1.76d (AMXX 1.8.0 since version 2.4), so no guarantee that any previous versions work fully...

[LT.KRATZER]

So do i copy the Cvars code and paste them with my AMXX Cvars ?

[diamond-optic]

well you dont 'have' to persay.. cause if you dont they will just use the default values, which i think all those are showing..

but yeah, if you want, or if you want to change them... just copy and paste them into the amxx.cfg file

[superbulette.nordend]

hey diamond..

we really like your plugin and have it running for some time now.
but theres one thing on my mind, that would be really comfortable:

would it be possible to customize the banreasons?
we try to use only standard-phrases as reasons with our amxbans, such as
Racist Terms/Nazi Tag
Swearing/Flaming/Whining
Unallowed Bugusing

a specific explanation is given in braces, as in
Unallowed Bugusing (Respawn Timer Bypass)
or
Racist Terms/Nazi Tag (chat: nigger)

I know you wont release the sourcecode and we appreciate this for obvious reasons, but could you make a kind of .txt or .cfg with banreasons every user can customize? maybe something like the multilanguage-files..

would be great,

thanks anyway,

bulette

[superbulette.nordend]

hey diamond, any chance of getting a short answer to my post above? ;)

greetz,

bulette

[diamond-optic]

oh damn im sorry i somehow missed that post..

i'll try to add customizable ban/kick reasons this weekend (or maybe monday or tuesday lol) and get that up here

[superbulette.nordend]

great, thanks very much..

greetz,

bulette

[diamond-optic]

ok ive found a bit of a mistake...

ok a pretty big mistake actually lol...



the decals thru walls detection can give false detection if a client does exec config.cfg mid-game

so 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..

so 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 it

hopefully over the next day or two ill have an update ready..


really really really sorry bout this lol

[diamond-optic]

also superbulette.nordend

just to get more information on what your looking for...

do you want to be able to customize the WHOLE message for each thing..? or just part of it?

like say for spectator killing, it should say this:

Exploit/Cheat/Bug NOT allowed! (Spectator Killing)

..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..


cause right now the message is: Exploit/Cheat/Bug NOT allowed! (%s)
..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..

like you could set it to just "%s" and it would say: Spectator Killing
or you could set it to "Detected %s" and it would say: Detected Spectator Killing
or you could set it to "Detected Exploit" and it would just say: Detected Exploit ..without saying which

i 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)

i think what i wrote is probably confusing right there lol

* edit *

oh 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?

unless 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..


damn 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..

or do you want a totally customizable message for each specific one? cause now that i think of it.. i should just do that lol

[knife108]

Can this plugin find out if someone had downloaded a cheating software but didn't use it ?

[diamond-optic]

how would it do that?

theres no way to monitor what people download and scan what it is, especially if they dont use it lol

[knife108]

how would it do that?

theres no way to monitor what people download and scan what it is, especially if they dont use it lol

you mean that we will know if people use the cheat software and the setinfo data changed by the software.

[diamond-optic]

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

[knife108]

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

Sorry about it :p

I mean can we know people is cheating or not by this plugin ?

[diamond-optic]

depends what you mean by 'cheat'

and no matter what you mean by it exactly.. most 'cheats' arent detected by this

[knife108]

depends what you mean by 'cheat'

and no matter what you mean by it exactly.. most 'cheats' arent detected by this


roger that..it's rigorous to requir this plugin to detected "cheats"...

:lol that is VAC's job !

[diamond-optic]

lol i wouldnt put much faith in VAC either...

the best tool is experienced admins :P

[knife108]

the best tool is experienced admins :P


connecting people :p

[blobby]

Surely if someoen was to buy all the best hacks and then make a plugin to find the code in the hacks it would be possible to detect them ??

[diamond-optic]

the way most cheats work theres no way that amxx would be able to do anything at all concerning them..

VAC 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)

[superbulette.nordend]

hi diamond,

sorry for the long time to answer, but rl got me somehow..

first of all: thanks for your effort and the two posts above..

but what i wanted to be customizable are the banreasons appearing in the amxbans-db

for example:

if player "ki||4h" uses the specjump he is banned for 5 minutes and the reason appearing on our banlist is actually "Respawn Timer Bypass".

I´d like to be able to change that to something like "Unallowed Bugusing (SpecJump)", since that would match our standard-banreasons much better.

the thing is that we use about 7 or 8 banreasons, but obviously they are quite general, such as "Racist Terms/Nazi Tag" or "Unallowed Bugusing".
Thats why we give a specific explanation for the ban in braces.
"Racist Terms/Nazi Tag (chat: whateverhesaid)"

So all i want is really to customize the amxban-reason written into the banlist..

maybe something like the multilanguage-files, so that every admin using your plugin can have his own banreasons..

hope that wasnt too confusing (and im hoping that this thread will autoemail me next time an answer is given, didnt work lately.. ;) )

thanks and greetz,

bulette

[{DwP} 325th ABN]

diamond ill tell you im deffinatley putting this on the server. wasnt going to say anything read the thread sounds killer. but man i give my probs way to stay with your plugin when i saw all the updates from a-d keep up the good work dude gots it going on. hey is the sma hanging around so we can upload it to i cant seem to find it

[Wilson [29th ID]]

hah, did you say "from a-d" instead of from a-z? :P

Just figured I'd jump in and let you know that the SMA is unavailable on purpose; so as to prevent those who do not know how to exploit from finding out through the SMA (and thus doing it).

[=|[76AD]|= TatsuSaisei]

;7650']hah, did you say "from a-d" instead of from a-z? :P

no I think he really meant a-d and that it was in regards to the 4 different versions of amxx 1.76 ...

:p

[{DwP} 325th ABN]

tis true tatsu a-d thanks for the post i understand and agree it is a good thing to keep hidden.

[diamond-optic]

Update To Version 2.3

* it is highly recommended that you update to this version due to false detections with the previous one *

- 09.23.07 - Version 2.3
Added CVAR to control third-person view block
Removed detection for decals thru walls (now it just blocks)
Now using an INI file to set the detection names
Removed some junk left over from previous versionsDont forget to download the "dod_blockexploits.ini" file and put it in "../amxmodx/configs/" on the gameserver

[knife108]

Nice D.O

first time to download !

:D

[knife108]

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

[dwarf]

is there no .sma file with this plugin?

[diamond-optic]

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

lol.. make sure you overwrote the old file and restarted or such.. showing 2.3 for me (been showing 2.3 for me for a while now as ive been testing it for a couple weeks)

..also where are you reading the public cvar value from? directly from the server itself thru rcon/hlsw? or game-monitor or some other 3rd party place, as they might not be updated to to whats actually on the server just yet


is there no .sma file with this plugin?

nope, no sma.. closed source

[knife108]

..also where are you reading the public cvar value from? directly from the server itself thru rcon/hlsw? or game-monitor or some other 3rd party place, as they might not be updated to to whats actually on the server just yet


readed from HLSW :D

[diamond-optic]

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

[=|[76AD]|= TatsuSaisei]

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

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

server has to be literally shut off then back on to reflect changes to these cvars... simply adding the latest plugin, changing the map, or even doing a console "restart" will not alter that value...

[knife108]

|= TatsuSaisei;7687']server has to be literally shut off then back on to reflect changes to these cvars... simply adding the latest plugin, changing the map, or even doing a console "restart" will not alter that value...

Roger that :cool:

[zak1212]

Nice work diamond

appreciated on our server.! stopping the lamers in the tracks

[superbulette.nordend]

hey diamond... did you read my last post? was it understandable? or, more important: can you do that?

greetz,

bulette

[superbulette.nordend]

ah well, i see, i see, you already did this... thanks very much..!

greetz,

bulette

[diamond-optic]

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 :)

[diamond-optic]

Update To Version 2.4

Highlights:
- AMXX 1.8.0 support
- Enhanced INI Checking

Full Change Log:
- 11.06.07 Version 2.4
Updated INI file * important *
Removed the pointless 'fullupdate' logging
Removed 'fullupdate' block console msg (showed when recording demos)
Enhanced INI file checking & error logging
Removed some old unused code
Reduced some msg sizes due to words being cut off
Added compiler define for new amxx 1.8.0+ log title format


* remember to download and install the new INI file (especially if you've customized the detection names) otherwise the plugin will use the default names *

[Box Cutter]

Thanks for keeping this plugin fresh d-o, you big sexy beast you!

[knife108]

works fine D-O !

[diamond-optic]

works fine D-O !


:rolleyes: now would i post something that didnt.. lol

[WARDOG]

There is a possible new exploit going around( at least I think it's new, first time for us ) that occurred in our server last night, that would be easy to block I think.

If you would like to add it to your code let me know and I will PM you the details of what happend, it would possibly head off some annoyance to other server ops if implemented before it spreads, although there might be other ways to block it easily. We did ban the perpetrator quickly.

[diamond-optic]

sure i'd love to hear about it :)

[meathead]

Last night heard of an excel progrom that counts head /neck shots, takes the %
and kicks/bans < 93%.

[TigerMan4]

Hey DO, is there anyway you can adjust this plugin to fix the stupid nade glitches in Avalanche ? or does the mapper have to fix that ?

( blue room / red room stairs and under rock ? )

[diamond-optic]

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 source

i 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

[TigerMan4]

I`ll ask in this thread since you seem to know about it.

Is there anyway to change respawn times ?

I know this plugin fixes the spectator jump glitch.

but I was playing Charlie today and it really Irritated me to the point that I left the map....I was on axis and every time I would get killed , there would be a 15 second respawn time ( it never use to be that way ) but I think Valve did somthing during one of their updates a while back.

anyway to fix it ? so that the respawns are 10 seconds and no more ?

I know I know...15 seconds is short , but its forever on a map with cap points like that.

[Box Cutter]

I`ll ask in this thread since you seem to know about it.

Is there anyway to change respawn times ?

I know this plugin fixes the spectator jump glitch.

but I was playing Charlie today and it really Irritated me to the point that I left the map....I was on axis and every time I would get killed , there would be a 15 second respawn time ( it never use to be that way ) but I think Valve did somthing during one of their updates a while back.

anyway to fix it ? so that the respawns are 10 seconds and no more ?

I know I know...15 seconds is short , but its forever on a map with cap points like that.

Try this.

http://forums.alliedmods.net/showthread.php?t=55978&highlight=DoD+Respawn+Time+Controller

[thanatopsizer]

I just wanna say that this is a great plugin. I have had it running for a week and it hasl already caught 4 people with various exploits. Keep up the good work.

[TigerMan4]

SO i was correct !!

when I mentioned that the respawn times had been changed on the dod forums ,I got slammed ,saying , no they wernt.

" But on some maps (charlie, flugplatz and falaise for example) the map designers altered the factors to make the maps more balanced. You may have noticed that on dod_charlie, the Axis takes 3 times longer to respawn than the Allies. That's because the Axis factor is 1.5 and the Allies factor is 0.5. So if there were 10 players/team, the Axis respawn in 18 seconds (12 x 1.5) and the Allies respawn in only 6 seconds (12 x 0.5)."

Great plugin D.O. I have it runing...no more snowmen showing up.

[WARDOG]

SO i was correct !!

when I mentioned that the respawn times had been changed on the dod forums ,I got slammed ,saying , no they wernt.

" But on some maps (charlie, flugplatz and falaise for example) the map designers altered the factors to make the maps more balanced. You may have noticed that on dod_charlie, the Axis takes 3 times longer to respawn than the Allies. That's because the Axis factor is 1.5 and the Allies factor is 0.5. So if there were 10 players/team, the Axis respawn in 18 seconds (12 x 1.5) and the Allies respawn in only 6 seconds (12 x 0.5)."

Great plugin D.O. I have it runing...no more snowmen showing up.

Download BSPEdit, open the dod_charlie.bsp with it.

At the top "Entity to search for" box type info_doddetect. Click find.

At the Entity "info_doddetect" , edit these line times to your liking

"detect_axis_respawnfactor" "1.5"
"detect_allies_respawnfactor" "0.5"

and save. Re-upload the .bsp to the server only, not fast Dowloads. Same with your other maps you would like to change.

{
"origin" "16 224 384"
"detect_wind_velocity_y" "0.0"
"detect_wind_velocity_x" "0.0"
"detect_axis_respawnfactor" "1.5"
"detect_allies_respawnfactor" "0.5"
"detect_points_timerexpired" "5"
"detect_points_allieseliminated" "5"
"detect_points_axiseliminated" "5"
"detect_axis_infinite" "1"
"detect_allies_infinite" "1"
"classname" "info_doddetect"
}

[TigerMan4]

D.O. please see my thread for a request to block the ` glitch in player names , where they think you cant kick them if they have ` in their name.

thanks

[diamond-optic]

i dont think thats really something that fits in with this plugin.. but i see wilson replied to your thread :)


.......

but anyway i got a question..

does 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..

when i trigger something, it will say im banned and adds me to the amxbans sql db.. BUT it doesnt actually kick me..

and 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..

this is using amxbans 5.0

if anyone else could let me know if it works or doesnt work for you that would be swell :)

**edit**

ok 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 :-\

[WARDOG]

I believe you have to use the option, kick and ban, in HLSW. I'm not sure if HLSW bans, writes to AMXBANS on the sql. either, maybe just to the banned.cfg

[diamond-optic]

ok i fixed the amxbans problem...

was a problem with the actual code for amxbans itself..


basically 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..

so i fixed this and it works now, i also posted about it on the amxbans forums, tho i wouldnt be surprised if its ignored :-\

...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 :-)

[{DwP} 325th ABN]

ill be waiting for that one, ive been using this one for awhile love it no doubts

[Vet]

I have a couple ideas for this bad boy...
How about the option to just log the player/exploit info. No notification to anyone.
Add the option to 'do nothing' on all exploits. Not just some of them.
Add action Cvars for the pistol zoom exploit.

The reasoning behind this is because I would prefer to handle any exploiters on a personal level rather than have players/admins know about it. And I'm only concerned about checking for some of the exploits. So I'd like the ability to just log the info and take no action on all exploits.

[diamond-optic]

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

[diamond-optic]

ok so far here's a little news i guess lol..

with 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 work


As for not blocking certain exploits...

** these should work with the current released version, but on the next update i'll add it to the comments **

> with the dod_blockexploits_warnwho cvar, setting to -1 will not warn anybody

> setting these cvars to -1 will make their detections do nothing (the logging cvars for each still function tho)
* dod_blockexploits_speckilling
* dod_blockexploits_whitemodel


** these ones will NOT work till the update is released **

> settings these cvars to -1 will make their detections do nothing (the logging cvars, again, will still function)
* dod_blockexploits_respawntimer
* dod_blockexploits_mgreload
* dod_blockexploits_limitbypass



it 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..

BUT!!! 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 :-)

[meathead]

I also love this plugin. The only weird thing I have with it is, my log file is empty most of the time. However once a month, the same 2 guys pop up for reloading undeployed mgs, at the same time. I don't think they are actually doing anything on purpose.
Still love seeing people come in and leave right away when they can't use there cheats!

Meathead

[diamond-optic]

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)

and 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 accidental

i should make note of which settings are reccommended for each one (besides the default settings) at some point when i have a chance

[Dr.G]

Does this work with the respawn controler? Or do it over rule it?

***Edit***
Found out it did.. dod_respawnctrl.amxx just needs to be listet before dod_blockexploits_176d.amxx in plugin.ini

[diamond-optic]

just wanna post some news about this plugin...

i 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 that

BUT!

the 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.

there 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 something

...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.

anyway I just wanted to let anyone interested know that progress is being made and its almost ready for a release :)

[{DwP} 325th ABN]

im in ill test it out for you no doubts

[diamond-optic]

damn i didnt expect such a fast response hahah

sounds good :)


...most likely a beta will be posted early this week, i hope.. depends if lazyness sets in again or not

[meathead]

Happy to put it on our server also.

[diamond-optic]

ehh im running a bit behind on this..


due 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

[diamond-optic]

Version 3.0 Final is now available for download...


CLICK HERE (http://www.dodplugins.net/forums/showthread.php?t=1230)