SourceBans 2.0 Alpha (2013/09/04) - Page 10

Rytis · 07-06-2013 , 14:07 Re: SourceBans 2.0 Public Preview (2013/07/01)

Quote:

Originally Posted by lyric

is it normal for the "View steam profile" link when you right-click on a person to not do anything at all?

Yes, https://github.com/GameConnect/Sourc...rk-in-progress

DJ Tsunami · 07-07-2013 , 10:00 Re: SourceBans 2.0 Public Preview (2013/07/01)

Quote:

Originally Posted by lyric

is it normal for the "View steam profile" link when you right-click on a person to not do anything at all?

I don't have a public test server, so I can't test if it works.

The Night Fury · 07-07-2013 , 13:44 Re: SourceBans 2.0 Public Preview (2013/07/01)

Yep, confirming: "view profile" does not work.

ppalex · *Last edited by ppalex; 07-09-2013 at 01:51.*

guys, can you explain to me why you are using sql query REGEXP for steam-id in the plugin? This is very slow on the large databases.

**Peace-Maker** · 07-10-2013 , 12:20 Re: SourceBans 2.0 Public Preview (2013/07/01)

Quote:

Originally Posted by ppalex

guys, can you explain to me why you are using sql query REGEXP for steam-id in the plugin? This is very slow on the large databases.

That's been introduced when proper steam universes were used in the rendered steamid. STEAM_0: vs. STEAM_1:
To be future proof, we just did STEAM_[0-9]:

In SourceBans 1 we couldn't just leave out the STEAM_X: part completely in the database due to legacy reasons, but here we should reconsider that.

ppalex · 07-10-2013 , 15:14 Re: SourceBans 2.0 Public Preview (2013/07/01)

Quote:

Originally Posted by Peace-Maker

That's been introduced when proper steam universes were used in the rendered steamid. STEAM_0: vs. STEAM_1:
To be future proof, we just did STEAM_[0-9]:

In SourceBans 1 we couldn't just leave out the STEAM_X: part completely in the database due to legacy reasons, but here we should reconsider that.

why not get on the use of steamid64? it is independent from the steam universe, in addition, this approach greatly speeds up the database and provides another benefits

FlyingMongoose · 07-10-2013 , 15:29 Re: SourceBans 2.0 Public Preview (2013/07/01)

Quote:

Originally Posted by ppalex

why not get on the use of steamid64? it is independent from the steam universe, in addition, this approach greatly speeds up the database and provides another benefits

SteamID64 didn't exist when SourceBans 1 was first released. It does seem a more viable option now. The conversions can be handled in plugin code or in PHP code when entering bans. Allowing the user to still place STEAM_X:X:XXX but storing the STEAMID64 instead.

ppalex · 07-10-2013 , 16:26 Re: SourceBans 2.0 Public Preview (2013/07/01)

Yes. I doesn't talked about "let's change steamid to steamid64 in sourcebans v.1".

Let sourcebans version 1 will remain in history, and 'db scheme' will be done in the best way in second version.

niar82k · 07-14-2013 , 07:52 Re: SourceBans 2.0 Public Preview (2013/07/01)

Can it be that will not take over the sourceban v1 database? I have specified the database from the v1 but it is not included in the v2.

**Peace-Maker** · 07-14-2013 , 16:28 Re: SourceBans 2.0 Public Preview (2013/07/01)

Quote:

Originally Posted by niar82k

Can it be that will not take over the sourceban v1 database? I have specified the database from the v1 but it is not included in the v2.

Quote:

Originally Posted by DJ Tsunami

As this is an early preview, there is no upgrade path for SourceBans 1 yet.

If you want to test this now, you have to apply all your settings again manually. If you don't want to do that, wait for the release.