[animalnots]

the prev worked ?

[SanKen]

I have not checked, I thought if you did something like this can do it Then check and find problems.

[animalnots]

I did not check either, you should check, if everything works, ill try do what you proposed (aka amx bans)

[SanKen]

does not work "You have been banned. Reason check site, Banlength check site, check <sitename> for more info"

[animalnots]

try this one

	"Banned Check Site"
	{
		"#format"		"{1:s},{2:s},{3:s}"
		"en"			"You have been banned. Reason: {1}, Banlength: {2} minutes, check {3} for more info"
	}

Print to console unfortenaly does not work, it seems that client is kicked too quickly before any message could be printed to him.

[SanKen]

Disconnect: You have been banned. Reason: Aimbot, Banlength: 10 minutes, check test for more info.

work, but (L 01/10/2013 - 14:418: [sourcebans.smx] Verify Ban Query Failed: Unknown column 'sb_admins' in 'field list')

A different solution that was similar to amxbans?
maybe PrintToConsole and after 10sec kick

[animalnots]

This should not throw error. The idea with timer is not new, I thought about it, but I don't know how to call a timer function with params (reason, time, etc.) without creating datapacks.

[SanKen]

When bans and wants to join the server

L 01/10/2013 - 17:19:09: [sourcebans.smx] Verify Ban Query Failed: Column 'authid' in where clause is ambiguous

Can you make a new line example:

You have been banned. Reason: Aimbot. Banlength: 10 minutes. You can complain regarding your ban @:

[animalnots]

Checked that query. Try now.
New line ? Ill try that in 2-4h.
Try to edit sp file adding \n in message.

PS: I don't like that the kick box is too small to show reason, length, admin name, website and etc. It would be cool if there's a way to enlarge it.

[SanKen]

L 01/10/2013 - 18:279: SourceMod error session started L 01/10/2013 - 18:279: Info (map "de_dust2") (file "errors_20130110.log") L 01/10/2013 - 18:279: [SM] Native "SQL_FetchString" reported: Current result set has no fetched rows L 01/10/2013 - 18:279: [SM] Displaying call stack trace for plugin "sourcebans.smx": L 01/10/2013 - 18:279: [SM] [0] Line 1509, sourcebans.sp::VerifyBan()

All the time the problem of verifying ban

PS: I don't like that the kick box is too small to show reason, length, admin name, website and etc. It would be cool if there's a way to enlarge it.

Not all ... Mainly reason, length, website