[Xanimos]

If you have it static, then your checking if its less than current which it all ways willl be so you could just take it out. My guess what that you wanted to check to make sure that the command wasn't used too soon after someone just used it.

And yes I know how get_systime() works but, thank you anyways.

[EDIT]
Also please don't set a cvar for the last time. You can use the get_systime() off set how I used it above and it saves you the extra steps. It looks like you took my suggestion and then added like 5 extra un needed steps for yoursef.

[hjvl]

I changed the plugin a lot..
I just didn't know what you did mean with using the offset(now i know)

I use a cvar for the "LastTime" to make a longer delay possible than the map time.The request was to make a delay possible of more than 1 hour.

I wasn't cheacking the static offset against the current time but the time that was stored in the cvar against the current time.
The static offset, i used only to make the results smaler.

I first tried it, store ths last time used in the offset.
But the strange thing is that i get lots of overflows. Somehow the get_systime can't handle offsets bigger than 9 decimals.

In the first script i added delay time by the curent time and then placed the result in the cvar. This was done at the end of the sellect user menu.
In the sayit i then compared the new current time with the cvar and this way blocked the script during the delay.

In the curent script i set the cvar at the end of the player sellection menu with the current time.
At the sayit function the time in the cvar is substracted of the current time and compared with the delay.

I now use integers instead of floats and simlpy moved the calculation.

The plugin is now much faster and works

[qsush]

hey can you add support for amxbans? that would be great!

[hjvl]

Originally Posted by qsush hey can you add support for amxbans? that would be great!

Adding amxbans is beyond the scope of this plugin.
So NO.

[Xanimos]

Originally Posted by hjvl Adding amxbans is beyond the scope of this plugin. So NO.

Actually you misunderstood what he was asking.

All you need is a cvar to decide whether to use AMX BANS style banning or the default AMX style.

The differences are:
Default:
amx_ban <steamID | nickname> <time in mins> <reason>
AMX BANS:
amx_ban <time in mins> <steamID | nickname> <reason>

So you would just have to switch the time and steamid around depending on the cvar.

[hjvl]

The original request for this plugin was: http://forums.alliedmods.net/showthread.php?t=42127
That request stoot for about 3 weaks before it was trashed....

The original plugin was made in less than 30 minutes, did work and was exactly as requested.

I changed a lot in the plugin to make it faster and added "ban on ip" support.(addip)
The plugin works as requested (the original request) and wil not be changed any further.(by me)

If someone wands other ban "types", please feel free to change row 212 & 213 or add more "cases" to this area.
These "cases" can be sellected with the amxx_voteban_type cvar.

[Xanimos]

You know...that's a real shame. If plugins are not updated or aren't kept up then they are sent to unapproved. So by saying that you will not support anything for this is not such a good idea. It is a simple addition. If you wanted to make someone a plugin they requested and just want it how they requested and not change it after it's done, then make it and PM it to him or post it to the request thread. Don't release it as a plugin if you don't plan on maintaining it.

[hjvl]

I'm not saying that i don't support/maintain it anymore, I'm just not going to add any unnecessary addons.

This plugin is for non permanent bans. (To avoid abuse.)
It uses nativ hl server commands.(banid & addip)
(did you even noticed that?)
Adding amxbans to this, adds nothing extra.

If i start on something i make a list of objectives.
The objectives for this plugin are clear.
Im not going to change them further.
I have made it very simple to add more ban methodes to it.
Just read the addons on the original post.

[SweatyBanana]

except it would be smart to add something like amxbans support since a good number of people use that for banning instead of default server bans..

Maybe they want all bans to be documented on their site?

[hjvl]

That is the first good reason i hear.....
(probably one of the few who takes the time to read)

I didn't think off that.
My webserver has access to the log files of the servers and takes his data directly from there.

But i'm a little confused. Didn't you say: "This has already been made in the base amxmodx code."

But amxbans has also amx_banip.

Shouldn't this be added as wel?