SourceBans-Fork [MOVED] - Page 20

Sarabveer · 02-01-2015 , 11:41 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by DarkEvil

@Sarabveer It's Localhost as well

Here is my database;

Code:

"Databases"
{
	"driver_default"		"mysql"
	
	"sourcebans"
	{
		"driver"			"mysql"
		"host"				"localhost"
		"database"			"bans"
		"user"				"****"
		"pass"				"****"
		//"timeout"			"0"
		"port"			"3306"
	}
	
	"storage-local"
	{
		"driver"			"sqlite"
		"database"			"sourcemod-local"
	}

	"admins"
	{
		"driver"			"sqlite"
		"database"			"admins-sqlite"
	}
}

try replacing localhost with 127.0.0.1

also, this is a linux box, right?

DarkEvil · 02-01-2015 , 14:19 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by Sarabveer

try replacing localhost with 127.0.0.1

also, this is a linux box, right?

Yeah It's a VPS with a linux system. I'm going try this soon

asherkin · 02-02-2015 , 16:49 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by 2NASTY4U

If you did not remove it, b flag admins can not ban somebody permanently.

This is intended functionality that is inherited from SourceMod's ban command, it really shouldn't be changed - if you want to give people access to permaban, let them unban.

Sarabveer · 02-02-2015 , 16:50 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by asherkin

This is intended functionality that is inherited from SourceMod's ban command, it really shouldn't be changed - if you want to give people access to permaban, let them unban.

Ok, undid that commit.

2NASTY4U · *Last edited by 2NASTY4U; 02-02-2015 at 17:06.*

Quote:

Originally Posted by asherkin

This is intended functionality that is inherited from SourceMod's ban command, it really shouldn't be changed - if you want to give people access to permaban, let them unban.

No. I want to let them permaban cheaters etc. But I will not give them access to unban flag. They have access to unban there own bans in SourceBans.

So removing this line is okay.

Quote:

Originally Posted by Sarabveer

Ok, undid that commit.

OMG. Why?

Sarabveer · 02-02-2015 , 17:06 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by 2NASTY4U

No. I want to let them permaban cheaters etc. But I will not give them access to unban flag. They have access to unban there own bans in SourceBans.

So removing this line is okay.

well you can remove the line by yourself, and compile yourself.

2NASTY4U · 02-02-2015 , 17:10 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by Sarabveer

well you can remove the line by yourself, and compile yourself.

Why are you removing this? Very bad, seriously. Your way with if(CheckCommandAccess(client, "sm_unban", ADMFLAG_BAN|ADMFLAG_UNBAN|ADMFLAG_ROOT)) was okay too.

Sarabveer · 02-02-2015 , 17:11 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by 2NASTY4U

Why are you removing this? Very bad, seriously. Your way with if(CheckCommandAccess(client, "sm_unban", ADMFLAG_BAN|ADMFLAG_UNBAN|ADMFLAG_ROOT)) was okay too.

As per asherkin's post, you have to have the unban flag to permban, I want to keep SourceBans similar to the SourceMod ban system.

2NASTY4U · 02-02-2015 , 17:15 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by Sarabveer

As per asherkin's post, you have to have the unban flag to permban, I want to keep SourceBans similar to the SourceMod ban system.

Recompiling every time is very annoying. If somebody wants to have some similar, they can use regular SM ban system.

Please fix the bugs kick / ban via website and the log bug as I told you.

Sarabveer · 02-02-2015 , 17:16 Re: SourceBans 1.5.1F [FORK] (Updated 2015/01/29)

Quote:

Originally Posted by 2NASTY4U

Recompiling every time is very annoying. If somebody wants to have some similar, they can use regular SM ban system.

Please fix the bugs kick / ban via website and the log bug as I told you.

The kick bug is something wrong with the server executing the kickid command. Please check your logs.