[gui1porpis]

Support AMXBans?
----EDIT----
I have problems to compile the plugin ...
Error on line 134. See the attachment.

Thank you.

[HamletEagle]

Compiles fine with online compiler, and also on my pc. Maybe you are trying to compile with amxmodx 1.8.3 and it's a build that doesn't have get_map_objectives native.

Can you detail more about amx bans ? What kind of compatibility do you need ?

[gui1porpis]

Yes I am using amxx compiler 1.8.3-dev, and would build for him?
Note: I'm using version 0.4 and it was compiled by amxx 1.8.3-dev smoothly.

About AMXBans, the syntax would look like this: amx_ban time userid reason.
In the plugin is as follows:

server_cmd(  "amx_ban #%i %i ^"%L^"", iUserid, get_pcvar_num( g_iCvars [ CVAR_BAN ] ), iUserid, "HP_NOTALLOWED" )

Would not it be so?

server_cmd(  "amx_ban %i #%i ^"%L^"", get_pcvar_num( g_iCvars [ CVAR_BAN ] ), iUserid, "HP_NOTALLOWED" )

Thank you.

[HamletEagle]

Ok, will try to add it.

[faKe91]

Hello. Mby there are another way to set plugin to pause, when the server is not running a map cs_, such as Bomb Objective Management plugin? Plugin makes a lot of error files and I must delete it manually. Thank You.

[Jockey]

You could make a new folder in amxmodx/configs called maps.

In this folder you create a new file called plugins-cs.ini with the content hostage_protection.amxx enabled

And dont type it in plugins.ini

Now its only loaded on cs_ maps.

Could there be also a check for how many hostages should get killed ?

The reason is easy.

You throw a grenade or just shoot at a CT and you hit a hostage one time you get banned ( yes i want them get banned ) .

So how could i make it that it only bans the player if he shoot/kill whatever 3 hostages and not just 1 ?

[HamletEagle]

Ok guys, I'll think about that and when I have some free time I'll update the ml file and also the plugin :d

[Brad]

I'd strongly recommend not writing information out to the log or error files unless there's an actual error. It'd be a lot better, IMO, to just print an admin message in game, and that's if you feel compelled to notify anyone at all.

Why?

It just gets messy with information that rarely changes and isn't useful to admins other than when they initially install and want to make sure it's working properly.

Perhaps add a "debug" CVAR that, when enabled, will write the information out to the appropriate files.

[HamletEagle]

All of your suggestions are appreciated and were fallowed, except the part with the number of hostages killed. This will come in a future update, because it needs to redesign this plugin a bit and right now I don't have the needed time.

Changelog:

+Improved code readability
+Now using good variable names
+Added suport for amxbans(UNTESTED)
+Using a new method to pause the plugin
+Added new languages to ml file.

Waiting for more translations.

Edit: Updated HasOnlyKnife stock, thanks to claudiuhks for pointing out this mistake. It was working as it should but it was strange :O

[safetymoose]

This is a great plugin for an Assault 24/7 server. Great job