[Sanjay Singh]

hey i have tried this but its not working please help me :/

PHP Code:

Adding Max Ban Times:
The order in which you add ban limits is the order in which they are checked.
- Example: If you do:
Code:
amx_addbanlimit "b" "9000"
amx_addbanlimit "c" "4000"
- Then if a player has flags "b" and "c", then only "b" will be used.
If you want immunity to have no limit, but other admins to have it, then add this FIRST! to the amxx.cfg
Code:
amx_addbanlimit "a" "0" 


[sigerman]

Guys, I found a bug, when you amx_addban someone It has no limits, you could ban easily an admin!!! (you can ban someone that is not in amx_last, without having rcon access)

amx_addban should be like this:

/* amx_addban is a special command now.
* If a user with rcon uses it, it bans the user. No questions asked.
* If a user without rcon but with ADMIN_BAN uses it, it will scan the old
* connection queue, and if it finds the info for a player in it, it will
* check their old access. If they have immunity, it will not ban.
* If they do not have immunity, it will ban. If the user is not found,
* it will refuse to ban the target.
*/

Can someone take a look at this? I love this plugin
Thanks

[fysiks]

That is the description of amx_addban in the original admincmd.amxx plugin. That is not how the command works in this plugin. Therefore, this is not a bug, it is simply a difference between Advanced Bans and the default bans.

So, what feature are you requesting be added to the amx_addban command in this plugin?

[sigerman]

Originally Posted by fysiks That is the description of amx_addban in the original admincmd.amxx plugin. That is not how the command works in this plugin. Therefore, this is not a bug, it is simply a difference between Advanced Bans and the default bans. So, what feature are you requesting be added to the amx_addban command in this plugin?

Anyways, sounds like a problem the advanced bans amx addban (anyone can ban anyone, useful, but dangerous)
In that case my request would be to change the advanced bans amx_addban for the default one admincmd

Thanks for reading, and sorry for my english.

[fysiks]

Originally Posted by sigerman Anyways, sounds like a problem the advanced bans amx addban (anyone can ban anyone, useful, but dangerous) In that case my request would be to change the advanced bans amx_addban for the default one admincmd

That won't happen in the official plugin and it's unlikely that someone would create a custom one for you because certain components that would be required are not implemented in this plugin (e.g. amx_last).

I personally think that Advanced Bans' version of amx_addban is the more proper one.

[sigerman]

Originally Posted by fysiks That won't happen in the official plugin and it's unlikely that someone would create a custom one for you because certain components that would be required are not implemented in this plugin (e.g. amx_last). I personally think that Advanced Bans' version of amx_addban is the more proper one.

Then I have another idea, the admins contained in users.ini cannot be banned, sounds better?

[fysiks]

Originally Posted by sigerman Then I have another idea, the admins contained in users.ini cannot be banned, sounds better?

That would require adding processing of users.ini but it a somewhat reasonable request (when not considering the code required). I'm sure someone could do it.

[aEEk]

help?

PHP Code:

L 01/07/2017 - 17:33:13: Start of error session.
L 01/07/2017 - 17:33:13: Info (map "de_nuke_rarea") (file "addons/amxmodx/logs/error_20170107.log")
L 01/07/2017 - 17:33:13: Invalid cellvector handle provided (1:-1:1881)
L 01/07/2017 - 17:33:13: [AMXX] Run time error 10 (plugin "adv_bans.amxx") (native "ArrayGetArray") - debug not enabled!
L 01/07/2017 - 17:33:13: [AMXX] To enable debug mode, add "debug" after the plugin name in plugins.ini (without quotes). 


[HamletEagle]

debug not enabled

[wizzkidon]

ML_NOTFOUND: AB_BAN_INFORMATION
ML_NOTFOUND:AB_NAME: asd
ML_NOTFOUND: AB_IP:81.196...
etc

Why?