admincmd.amxx
Hi, i'm a new AMXX user. I was using AMX 0.9.9. till now.
I am impressed with what AMXX has to offer but VERY pissed for one thing. I must admin that its possible to be my mistake but still i'll ask. The admincmd.amxx as i see differs from the admincmd.amx. The command i'm interested in is amx_ban So in AMX the command was as normal as it can : amx_ban #ID and there you go, you have banned the user permanently to his IP. But what do i experience with AMXX? typing amx_ban #ID gives me a hint to use amx_ban #ID [minutes] [reason] , ok no prob, but when i do that the user gets "BANNED" .. but no really , he just gets kicked with message for BAN and he joins the server immediately. I have fixed my GeoIP so now i can resolve IPS.. so no reason to fail banning. Through HLSW i can see the bans, but i dont see where they are listed, can you point me to that place? I dont see why the server fails to ban with IP. How to make amx_ban work only with "amx_ban #ID" (not to use min and reason) and still get auto-IPBAN from AMX... Any ideas? |
Re: admincmd.amxx
amx_ban
amx_addban amx_banip |
Re: admincmd.amxx
I know the commands but they dont work as good as they should...
I Mean.. i type amx_ban #ID and has no effect Then type .. amx_ban #ID min and reason and the user is only kicked.. but no added to ban list |
Re: admincmd.amxx
You need to add the minutes to ban, like amx_banip M2 "0"
This bans M2's IP address for 0 minutes (permanent) |
Re: admincmd.amxx
Quote:
|
Re: admincmd.amxx
Thanks ppl :) You really helped me!
|
Re: admincmd.amxx
You could always modify the admincmd.sma to default to a permanent ban. Thus making the minutes parameter optional.
Code:
|
| All times are GMT -4. The time now is 11:08. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.