[@LeX]

Originally Posted by mlibre disabled admin.amxx

no... please... no
admin.amxx has the role of assigning the admin degree.

he asked for amxbans to work for him on mban function

if amxbans registers the same command as admincmd (ie 'amx_ban', 'amx_banip')
then amxbans must be put in plugins.ini above the admincmd plugin because the first plugin that defines the function will execute the function first

the format of `amx_ban` in admincmd is `<name or #userid> <minutes> [reason]`
in amxbans is `<Time in Minutes> <SteamID | Nickname | #userid> <Reason> <SteamID> <IP>`

big difference between the two

so the statement `server_cmd( "amx_ban 1440 #%d ^"[^x03TEST^x01] hack (#2221) detected!^"", get_user_userid( id ) );` was correct, only that amxbans was under the admincmd plugin
either leave amxbans above admincmd or modify admincmd and remove all defined functions related to banning players so that amxbans can then register these functions instead

off: @popilas
`[^x03TEST^x01]`, No need for color here

p.s. I don't know exactly if it also needs ip/steamid to ban a player (I've never used amxbans)
but it can be solved in the statement