Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Version 1.6.1 has been released.
Please Backup your database and files before updating! Changelog:
All changes here Download |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Thank you.
Downloaded, using this on 6 servers. |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Quote:
Problem:
Temporary Fix:
|
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Quote:
|
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Spoiler
Change the salt function to this Code:
$password = crypt($_POST['password'], SB_NEW_SALT); After you done that you might need to login through Sourcebans and change ur password to rehash your PW in the database. |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
I am having trouble getting comms bans to actually appear on my bans page.
I've just upgraded from Sourcebans 1.4.11 to Sourcebans++ Version 1.6.1 -git495. I am using Sourcemod v1.8.0.5992 and MetaMod v1.10.7. I can gag, mute and silence people as before, with it now preventing players from reconnecting to avoid a gag/mute/silence. Regular server bans are also working as normal, and they appear on my servers sourcebans page. My problem is that none of the comms bans appear. I can see the gags and mutes have been added correctly to the database, as when I access the database itself I can see them. I have checked the error logs, and it does show this error: Code:
05/16/2017 - 14:23:35: [sbpp_comms.smx] You must set valid `ServerID` value in sourcebans.cfg! Code:
// This is the ID of this server (Check in the admin panel -> servers to find the ID of this server) How do I fix this? |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Quote:
The problem was my Sourcebans Theme. I was using a custom theme that was made for Sourcebans 1.4.11, not Sourcebans++. As soon as I changed theme, they were visible. |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Out of curiosity, does anyone have an issue with CONSOLE muting players randomly (permanently). I've had this issue for a few days now and I've only really updated SB++ from 1.5.7 to 1.6.1 (CSGO update also happened).
EDIT: I found the solution out myself. It seems that between 1.5.7 to 1.6.1, the handling of BaseComm_SetClientMute() by sourcecomms was changed. I simply updated my plugin to use the relevant SourceComms natives if the sourcecomms library was loaded and the issue wen't away. The plugin was a priority speaker (which mutes/unmutes T's if they try to speak over a CT player). |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Quote:
Does anyone else have in-game or web rcon access? Never hurts to double check permissions, could be someone trying to be funny, or a compromised account. |
Re: [RELEASE] SourceBans++ (v1.6.1) [Updated: 2017-05-06]
Quote:
|
All times are GMT -4. The time now is 00:55. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.