[VPPGamingNetwork]

Originally Posted by RumbleFrog Update completely, this means, OVERWRITE the config files with the new ones.

[8guawong]

is there a changelog somewhere?

[`666]

https://sbpp.github.io/blog/1.6.3_release/

[MyWarthog]

I have a question. Under new EU Data Protection laws (the GDPR)... it is now a legal requirement that data protection must be built into software by default. Ban database downloads can no longer be allowed, old bans have to be automatically purged from the database, bans can not be listed publically unless opted in by the user to display their profile information to the public, and must be concealed if a user changes their Steam privacy settings to hide information.

Please tell me that SourceBans has no intention of actually complying with this bullshit...

[paulo_crash]

Originally Posted by MyWarthog I have a question. Under new EU Data Protection laws (the GDPR)... it is now a legal requirement that data protection must be built into software by default. Ban database downloads can no longer be allowed, old bans have to be automatically purged from the database, bans can not be listed publically unless opted in by the user to display their profile information to the public, and must be concealed if a user changes their Steam privacy settings to hide information. Please tell me that SourceBans has no intention of actually complying with this bullshit...

If it's law like you say, I think you're bound to.

But this can be bypassed very easily, after all your server, or any place that it accesses concerning your server, has rules, that is, it agrees on your your information collected and divide or shared if necessary.

So I believe...

[Lubricant Jam]

Originally Posted by MyWarthog I have a question. Under new EU Data Protection laws (the GDPR)... it is now a legal requirement that data protection must be built into software by default. Ban database downloads can no longer be allowed, old bans have to be automatically purged from the database, bans can not be listed publically unless opted in by the user to display their profile information to the public, and must be concealed if a user changes their Steam privacy settings to hide information. Please tell me that SourceBans has no intention of actually complying with this bullshit...

Under my understanding, GDPR changes nothing other than what you do with the data. If you're collecting IP, Username, SteamID, etc from a ban it is needed in order to combat and ban evasions for your service etc as well as gives you evidence for charge backs if they let's say buy something from you.

What SourceBans does in terms of storing data is nothing remotely illegal in terms of GDPR, all you must do is NOT display people's IPs on your ban page as that is TECHNICALLY personal information you're giving out to public figures. Steam ID & Names are not personal data and therefore you can display publicly as they are already forced public as it is.

You will also not need to delete information about people if they request you to do so as it is within your best interest to cover yourself from any means of harm to your servers (business let's say if you run yours as a business, take me for example).

I've had a few meetings in regards to GDPR standards and it changes absolutely NOTHING other than what you actually store data for & the best ways to combat data breaches.

TLDR: You do not need to worry about what SourceBans are doing, just do NOT display IPs.

[Grainz]

Since upgrading to 1.6.3, I am receiving "Error connecting" to every server I have added. Games include Left 4 Dead 2, Team Fortress 2, and Counter-Strike: Global Offensive. I did an upgrade at first then I tried a clean install.

[Grainz]

Originally Posted by Grainz Since upgrading to 1.6.3, I am receiving "Error connecting" to every server I have added. Games include Left 4 Dead 2, Team Fortress 2, and Counter-Strike: Global Offensive. I did an upgrade at first then I tried a clean install.

Solved this on my own.
To query Source based servers, PHP requires the GMP module.
It was commented out in my XAMPP environment inside of php.ini where SB is installed to.

extension=php_gmp.dll

[Xenoadria]

Hey guys I was wondering if it's possible to make a ban message like this:

https://imgur.com/FYcQUwV

Boompanel used this type of ban message. Is it possible to make this kind of message with sourcebans++ ?

[DarkDeviL]

Originally Posted by Xenoadria Hey guys I was wondering if it's possible to make a ban message like this: https://imgur.com/FYcQUwV Boompanel used this type of ban message. Is it possible to make this kind of message with sourcebans++ ?

It is not completely impossible to do:

Every place where SB has "Banned Check Site", you need to adjust things, and it may become a little bit more tricky as not all callbacks and such where the phrase is used, may contain al the data that you want (such as fo example admin name and reason).

If that's the case, you need to rewrite the SQL queries to also fetch that data for you, or the natives to pass the data along every time...