Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Does anyone else have any problems with source sleuth not working correctly? We are on Windows Server 2008 and I've had the ban multiple accounts that are coming from the same IP address that is permanently banned. Can someone who has a working set up post their config?
|
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Hello
I have a big problem with SourceBans Code:
[Server Specs] BTW SourceBans web rcon console doesnt work (Can't connect to the server) I tried SourceBans 1.5.3 and 1.5.4 same problem PHP Code:
|
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Quote:
|
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Hi,
I have following problem that when I mute a player, and a mapchange he is unmuted again. I use the !mute command. The same, if he joins to another server. I dont know when the problem was happen, some times ago it worked without problems. |
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Quote:
No offense, but as I read your post, you said SourceBans++ wasn't working? MariaDB is the problem, not SourceBans++: MariaDB claims to be a drop-in replacement for MySQL. If it really was a drop-in replacement, how would you explain that MariaDB breaks functionality of other things, which works perfectly with MySQL? That's not what I would call a "drop-in" replacement. Anyway, SourceBans++ is totally open sourced, ... so if you want it MariaDB to work together with SourceBans++, feel free to make it the required adjustments and submit a pull request. If I misunderstood you, and that you would really like to help constructively rather than running around with that selfish attitude you were showing above, then offer your assistance for the future development. |
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Quote:
Quote:
|
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Quote:
Quote:
SourceBans++ claims to support MySQL 5.0+, which includes all versions of MariaDB as a fork of MySQL 5.6 without any compatibility-breaking changes, so that statement is clearly incorrect. |
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
Quote:
Refusing to work on and refusing to accept contributions are two different things to me, I have only seen the first one. Quote:
However, if you can send one command to MySQL, and that works fine, but you can't send it to some fork of the MySQL; I wouldn't ever call that a drop-in replacement. If it was a drop-in replacement to me, it would either silently have discarded or eventually produced a warning with the hard-coded check. |
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
I'm on my phone so can't look it up again, but the closed PRs are in the repo for anyone to see.
That's it, you CAN send the same "command" - but SourceBans++ DOESN'T send it at all due to the buggy version check. There is absolutely nothing that could be changed in MariaDB (other than pretending to be MySQL, and a specific version at that), the problem is squarely in SourceBans++ – if it just sent the query it would work fine – and the query in question is just working around other bugs in SourceBans++ and is required by BOTH MySQL and MariaDB 5.6+, but SourceBans++ doesn't consider 10 greater than 5 so doesn't work with current versions of MariaDB, it'll probably break MySQL on the next major version bump as well. |
Re: [RELEASE] SourceBans++ (v1.5.3) [Updated: 2015-10-07]
https://github.com/Sarabveer/SourceB...d07bcad1ce7e93
Going back to sleep. Zzzzzzz........ EDIT: Quote:
|
All times are GMT -4. The time now is 11:19. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.