Syn's Nade Exploit Fix v1.002rnrnThis plugin is a spawn off of my dod_avalanche and dod_purple nade exploit fix plugins. This isrndesigned to be used with any map. All you need is a defintion file for a particular map. You canrnalso create your own or modify existing ones with the built in editor. The reason I made a universalrnplugin for all maps is simple. Less to deal with. It would be a redunant to have to get different rnplugins to cover multiple maps. It also creates less mess on the dodplugins.net forums. XDrnrnCurrently comes with the following definitions:rnrndod_avalancherndod_purplernrn===========================rnv1.002 Changesrn===========================rn- Fixed non working player blocks.rnrn===========================rnv1.001 Changesrn===========================rn- Added missing admin flag check for console commands. Allowed anyone to use the editor! o.Orn- Per request, added menu to access all console commands via menu.rnrn===========================rnFeatures & Notesrn===========================rn- Deflects nades from marked exploit locations on maps. Can block Allied, Axis, or all grenades.rnrn- Blocks can be set to deflect players instead of nades on either or both teams as well. This isrngood for spawn protection or anywhere you don't want players getting to.rnrn- Built in editor for creating and editing your own custom blocks.rnrn- Supports as many maps as you want.rnrn- Each map definition file supports up to a maximum of 64 blocks.rnrn- Want to have a map fixed? Let me know and I'll create a definition file for it or you can use thernbuilt in editor to make your own!rnrn- Credit goes out to the following people for helping me test, improve the original plugin to thisrnfinal refined, unified plugin and provide exploit locations for dod_avalance:rn| Tank | Diamond-Optic | OnEHiTwOnDeR | Dr.G |rnrn- Block locations whose vector is 0.0 / 0.0 / 0.0 (X/Y/Z) are ignored. The chances of placing a rnblock at these coordinates are very slim but just incase I'm mentioning it.rnrn- Unlike my previous dod_avalanche nade exploit fix map, I have not added an Axis player block intornAllied appartments from the penguin room. You can add it if you want.rnrn===========================rnEditor Modern===========================rnBecause this is a more in depth function of the plugin, it gets it's own section. I've tried tornmake it so creating your own block points are as less of a pita as possible.rnrn[> Setting up <]rn- First you are going to join sectators and turn on the editor by typing: nade_exploit_edit rninto your console. This toggles the editor on and off and anytime the map changes or the server rnrestarts, it will always default off. Once you have enabled editor mode (console will show a messagernto this effect) you can begin placing your blocks.rnrn[> Keys <]rnAttack - Place a new or select a highlighted block location for editing.rnrnAttack2 - Cycle's through a selected entity's block modes, nade/allied/axis/all/remove.rnrnJump - Increment block location size.rnrnDuck - Decrement block location size.rnrnTurn Left - Rotate deflection direction to the left. This is not strafe left.rnrnTurn Right - Rotate deflection direction to the right. This is not strafe right.rnrnRun - Delete block location when editing it.rnrnUse - This will instantly warp you back to the last spot you were editing from so you can check yourrnblocks quicker after spawing instead of walking all the way back. This location is saved only rntemporarily and does not save between map changes.rnrnIf you don't know the binds for these keys, here they are in the same order:rnrn+attackrn+attack2rn+jumprn+duckrn+turnleftrn+turnrightrn+runrn+usernrnIf you don't know what to do and don't know how to bind keys this example will help. Let's say yournwant to bind cancel to your I key. You would go into the console and type:rnrnbind i +cancelrnrnSo by looking at that you can see first we are using the bind command, then the first argument isrnthe key you want, I in this case, and the last part is the action command we are binding to the Irnkey. It's really simple. You can do this with any of your keys and any command. rnrn[> Working with blocks <]rnThis editor takes a simple approach to editing locations. All you have to do is aim where you wantrnthe block to go and press your primary attack button. To make things even easier, there is arntemporary placement rabbit model for reference. Where this temp model is, is where your block willrnbe. The new block is also represented with a rabbit model. After placing a block, make sure you arernaiming at it. You will know your on it because you will see a white highlight box around it and an rnimplosion effect. The implosion effect is a general representation of the block radius, that is,rnthe range at which you want to cover for blocking something. So now that you have your new blockrnhighlighted press your primary attack again. This time the rabbit will turn red and thernhighlight box will dissapear indicating that this block locations is currently being edited. You canrnmove around the map and place it in another location or you can change it's block type. There are rn6 block types you can choose from. These are Allied nades, Axis nades, all nades, Allied players, rnAxis players or all players. To cycle through each block type, have your block location bunny rnglowing red and press your secondary fire button. It will take you through all the modes. Also, if rnyou want to delete a block location, have it in the red and hit your run key. This will remove it rncompletely. Now on to the deflection. Setting this up is just as easy. Look at the way the rabbitrnmodel is facing. He is pointing in the direction which objects will be deflected in. You can rotate rnthe deflection angle with your turn left, and turn right keys. Generally you want to always deflectrnaway in the opposite direction of where something shouldn't go. All that is left now is the radius rnof the deflection. The radius is how big of an area you want to cover. Keep in mind that this radiusrnis the shape of a sphere. After playing around and setting up your block locations, test them out.rnTo make things easier after you spawn, press your use key and it will take you to the location ofrnthe last block you edited. Once you are satisfied, go into the console and type: nade_exploit_save rnand it will save all of your current work to a file for the corresponding map your on. You can then rnexit editor mode by typing: nade_exploit_editor into the console again. This will resume normal rnoperation. There is also a menu to access all console commands and can be gotten to by typing: rnnade_exploit_menu in console.rnrn[> Additional info <]rn- Remember that depending on the location you may need a few smaller radius block locations to coverrnan area while others will suffice with a larger single block. Too big of a radius and it could blockrnparts of the map you don't want blocked and too small could lead to gaps that aren't fully covered. rnrn- If you need to start over to the last time you saved, just type: nade_exploit_load into the rnconsole.rnrn- Using the console command: nade_exploit_wipe will completely wipe all block data from memory if rnyou want to start all over. This does not wipe a saved map file though.rn.rn===========================rnConsole Commands:rn===========================rnnade_exploit_editorrn- Toggles editor mode on or off for creating/editing exploit definition files.rnrnnade_exploit_statusrn- Displays info in the console as to the status of the plugin such as the total exploit blocksrnrunning or any errors the plugin encountered.rnrnnade_exploit_savern- Will attempt to save the current exploit definition data to the map's corresponding file. Thisrnprocess can take a few seconds to complete.rnrnnade_exploit_loadrn- Will attempt a load or reload of the current map's exploit definition file if available.rnrnnade_exploit_wipern- Use this to completely start over with no block locations. Use this with nade_exploit_save tornclean the map definition file as well.rnrnnade_exploit_menurn- Allows access to all the console commands via manu.rnrn===========================rnCVARsrn===========================rnnade_exploit_fix | 0 = off | 1 = onrn- Enables or disables the Map Exploit Fix plugin. Default on.rnrnnade_exploit_scan_time | x.xrn- Allows changing the delay between every scan. This will let you adjust the plugin's CPU usage.rnWhile it doesn't take alot of work to check these locations, you might have a slower server or wishrnto optimize your server if you have lots of plugins running. The higher the number, the more timernthere will between each global check but if it's too high, you run the risk of a blockee gettingrnpast a block location. For the most part you want to keep this under 1 second. You can enter an rninteger or real number here. For example, a value of one would just be 1 second and a value of 1.5rnwould be 1 and a 1/2 seconds. Also, this only is for nade block locations. Players have to bernchecked much faster in prethink. Default 0.5.rnrn===========================rnInstallationrn===========================rn- Compile the .sma file | An online compiler can be found here:rn http:www.amxmodx.org/webcompiler.cgirn- Copy the compiled .amxx file into your addonsamxmodxplugins folderrn- Add the name of the compiled .amxx to the bottom of your addonsamxmodxconfigsplugins.inirn- Copy the desired map definition files to a new folder named nade_exploits inside of your amxmodxrnconfig folder. For example most people's setups would look like this:rnaddonsamxmodxconfigs
ade_exploitsrn- Change the map or restart your server to start using the plugin!

Ahh, that was leftover data from testing. I didn't bother cleaning it up since it will get ignored anyway. XD The ones that have zeros are just place holders for each of the blocks. As for that roof block, I'll have to adjust that lol. It probably needs to be pushed back more or the radius increased.nnLOL @ edit #3nThat had to be a mess. Good thing it caps at the limit. XDnnOh and it determines a block entry in if the first three lines (block origin) of the block are all zeros or not. It doesn't bother checking the rest of the data in the entry if they are zeros.

Basically I'm just checking objects within x distance of block origin and using velocity to deflect them. Since there isn't anything really there at a block location the only ways I can think of is to use entities or create some collision / movement code. Entities would be easy but they are too slow so I could probably come up with some simple collision math that makes it just like a wall.

Updated the Avalanche def for the block up above the W crack. It was set to only block Allied nades. XD

Now with menu and an important fix. Yeah, I never really bothered with the old menu system too much.

Wow I'm outdated. Sorry for the delay in getting back with you Tank. Type nade_exploit_status into the console and see if it reports any problems. If all is good, I may have accidentally set it to only a certain type of block I.G. allied only or axis only like I did with the ceiling block above the W crack house. XD I'll check it out though.

New update. Was setting up some blocks for a map and realized that they weren't working in non-editor mode because player origins were only being stored in editor mode. Now they work like they should.