[sgtbane]

Basicly this plugin will allow you to set objects to block people from going places.

I help maintain several servers, and in several of them I have problems with people camping in hard to reach places. I created this plugin to physicaly set an object in a place to prevent them from going there.

Unlike the other 'wall' plugins, with this, you can set the exact size of the wall you want, and once it is placed it will stay there till removed.
I have also added the ability to load and save them so that once they are set, you can forget about them.

/**
* Changelog
*
* version 0.1
* - Intial Attempt
* version 0.2
* - Fixed Calculations
* - Added Model
* - Added 'Kill'(Delete) Features
* version 0.3
* - Added Visual Aid (Beams Forming A Cube, And Center Point)
* version 0.4
* - Added Ability To Load/Save
* - Fixed Various Problems
* version 0.5
* - Added 'Load By Mapname'
* - Added Cvar (block_autoload) To Auto Load Blocks On Mapload
* version 0.6
* - Fixed Various Problems
* version 0.7
* - Added Menu
* version 0.8
* - Added Ability To See Bounding Boxe Of Set Blocks
* - Added Different Colors For Beams (RED = Being Placed | GREEN = Placed)
* - Fixed Problem With Load
* - Organized Code & Added Several Comments
* version 1.0
* - Added Changelog
*/

Try it out and tell me what you think.

Attached is the model required. Simply an orb that can be used as a reference so you can see where the center point of your wall is.

(Set as Cstrike Only, but would probly work with any mods since the only required modules are: <amxmodx>, <amxmisc>, <fakemeta>)

[godlike]

looks nice but whats the difference between this one ?
http://forums.alliedmods.net/showthread.php?t=55245

it has the same features with something extra's.

[Alka]

hmm,this look nice too! Gj anyway

[sgtbane]

well to be honest i never saw that one before I wrote this one, and if I had I would have probly just modified that one and kept it for personal use.
I guess one main difference between mine and that one is that mine simply prevents the people from going there.
Its like setting up a wall, instead of just hurting the people who go into it.
Also mine requires far less resources since after it is set, there are no timers(tasks) or other events that interact with it.

The only thing that it may do that would be a downside is that it consumes an entity. One entity per block. But then again so does his.

Pros:
Uses fakemeta instead of engine. (I am anti-engine)
Easyer to set (Instead of having to stand in the place you want to set it, just point and click)
Uses less resources.

Edit:
now looking more into his, I see that he posted it just a few days before mine.
Before anyone goes and says that I 'jacked' his code, look through both and find anything that looks stolen.

[redx6580]

Before i download it, what would the commands be to use this, and is it possible to set it while dead or in spectator mode?

-LJ

[sgtbane]

amx_blockmenu - You can do all of the below commands with this one
+setblock - Bind this to a key to place the blocks. Or use the menu..
-setblock
amx_saveblocks - Save blocks you have set
amx_loadblocks - Load saved blocks
amx_killblock - Remove block under crosshair
amx_killblocks - Remove all blocks
amx_toggleauto - Toggle auto load on mapchange cvar

The following are optional.
Bpush - Extend...
Bpull - and Retract point where end of block is..

Note: I forgot to mention.
setinfo gab true *Optional*
setinfo mwup invnext *Optional*
setinfo mwdn invprev *Optional*

gab: grab auto bind (used in other plugins of mine. Kept same setinfo)
if set to true then when you begin placing the block, it automaticaly rebinds your mousewheel. When you are done it rebinds your mousewheel to what you have in the other two setinfos. (if nothing is defined in them, it rebinds to invnext and invprev)

Example of use:
setinfo gab true
setinfo mwup +duck
setinfo mwdn +jump

[Lt Llama]

We have been talking about nothing else over at the map hax department on Euroskillz the last couple of days. I cant see why this wont work with other mods, you have no cstrike include so shouldnt the modification be All. And maybe also change the folder for the model used so you dont have to use Cstrike folder, put it in a more generic location.

Very well done, gonna test this in TFC

[Hawk552]

The other one does this and much better. Redundant, unapproved.

[sgtbane]

thanks for your input hawk.
i aprecieate your comment because i respect you and your work. many of the plugins i have written i have come accross problems, and you seem to be the main person who finds solutions to them.
so thanks.
I released this plugin because it is rather simple, yet it gets the job done using minimal resources for all those people who hate plugins that create fps lag... it all adds up in the end..
Also because mine is fakemeta instead of engine. I hope im not the only person who hates engine o.0

idk... i guess i just figured someone might find it usefull

and for lt llama,
it is not cstrike specific, though i set it for that because im not sure. though it should work in any other mod. I just put it in the cstrike folder in the zip kuz i thought it would make it easyer for people :\
the model simply needs to be:
models/banes/BlockPointer.mdl
or you can edit the plugin for any other model you want.

[Hawk552]

Originally Posted by sgtbane so thanks. I released this plugin because it is rather simple, yet it gets the job done using minimal resources for all those people who hate plugins that create fps lag... it all adds up in the end..

While this may be true, the difference is minimal. Both of the plugins that do this use reasonably efficient methods; the extra stuff on the other is probably going to be used by most people anyway (thus the simplicity argument may not apply here).

Originally Posted by sgtbane Also because mine is fakemeta instead of engine. I hope im not the only person who hates engine o.0 idk... i guess i just figured someone might find it usefull

I don't know why people are on this rampage about getting rid of engine. If you can use either, then use which ever you're comfortable with. If you need something from fakemeta, then use it alone or even both. If you understand how engine works, you'd know that if any plugin includes it, it sends out its forwards to all plugins (the slowest part of it). How can you know that your plugin is not the only one running engine?

There's nothing wrong with engine or fakemeta. Use whichever one you're more comfortable with, but please don't use it as an argument for something being better/worse.