[MasterOfTheXP]

Originally Posted by goodman854 Every so often on our Saxton Hale Server. Everyone loses admin power and the Saxton hale queue for everyone is zero and the same persons hale every round. This happens until the servers reset any idea why?

Are you sure it's VSH that's causing that? And by "loses admin power" do you mean that no one can use admin commands, not even the server console?

[napalm00]

Originally Posted by FlaminSarge VSH 1.39 beta. For anybody that wants it. FF2 is messed up in places.

Thanks!
And I agree, FF2 will be usable in a few months, maybe.

[x6herbius]

@goodman: if everyone loses their admin powers, that sounds like something non-specific to VSH.

[goodman854]

Originally Posted by MasterOfTheXP Are you sure it's VSH that's causing that? And by "loses admin power" do you mean that no one can use admin commands, not even the server console?

Consoleworks however it also breaks VSH because the same person is saxton every round and everyone has zero que points.

[FlaminSarge]

goodman, the issue is that your server is losing access to your clientprefs database. You have your admins in that database, as well as the VSH queue points. An easy way to fix the queue points would be, in databases.cfg (find it) set your "clientprefs" database to use sqlite, which is stored on the server.

[Eggman]

Originally Posted by MasterOfTheXP If ff2_enabled is set to 0, players are still moved to RED Team upon death on BLU. Unloading the plugin fixes this and it looks like unloading the plugin doesn't cause any glitches if you do it as soon as the map starts.

I'm not sure, but bug of FF2 may be in VSH too. You can try /hale command when VSH is loaded but disabled. If this command allowed, then bug exists.

[goodman854]

Originally Posted by FlaminSarge goodman, the issue is that your server is losing access to your clientprefs database. You have your admins in that database, as well as the VSH queue points. An easy way to fix the queue points would be, in databases.cfg (find it) set your "clientprefs" database to use sqlite, which is stored on the server.

"Databases"
{
    "driver_default"        "mysql"
    
    // When specifying "host", you may use an IP address, a hostname, or a socket file path


    "sourcebans"
    {
        "driver"            "mysql"
        "host"                "**********"
        "database"            "**********"
        "user"                "**********"
        "pass"                "**********"
        //"timeout"            "0"
        "port"            "****"
    }

    
    "default"
    {
        "driver"            "default"
        "host"                "localhost"
        "database"            "sourcemod"
        "user"                "root"
        "pass"                ""
        //"timeout"            "0"
        //"port"            "0"
    }
    
    "storage-local"
    {
        "driver"            "sqlite"
        "database"            "sourcemod-local"
    }

    "clientprefs"
    {
        "driver"            "sqlite"
        "host"                "localhost"
        "database"            "clientprefs-sqlite"
        "user"                "root"
        "pass"                ""
        //"timeout"            "0"
        //"port"            "0"
    }
    
    
    "stamm_sql"
    {
        "driver"            "mysql"
        "host"                "**********"
        "database"            "**********"
        "user"                "**********"
        "pass"                "**********"
    }
    
}

That is how it is right now ^, so does it have to do with the sourcebans or something?? Although to be honest when this happens Stamm doesn't work either so it sounds like database.cfg just randomly doesn't work at all. I don't really get why that is happening though.
Because sqlite is already set for clientprefs. AHHH Why is our server derping all of a sudden haha.

[FlaminSarge]

I guess all your databases decide to go down. It does happen randomly, I've noticed it too. Nothing I can do. Try updating SM.

Relevant to Invisible CBS:

Originally Posted by FlaminSarge I've come up with a fairly good fix for some clients having invisible players when using custom skins. I'm going to copy all of the stock TF2 models and rename them to <class>_stock.mdl. I'm going to have them download to clients. Any custom skins will reference these stock models instead of models/player/scout.mdl or whatever. That way, if the client has a custom scout skin, it won't break the custom models from Model Manager/VSH/etc. If all servers use these stock models, then all servers will have the fix, and a client will only need to download the models once.

[nineteeneleven]

L 04/17/2012 - 20:27:27: [SM] Native "TF2_AddCondition" reported: Failed to locate function
L 04/17/2012 - 20:27:27: [SM] Displaying call stack trace for plugin "saxtonhale.smx":
L 04/17/2012 - 20:27:27: [SM]   [0]  Line 2727, C:\sourcemod\saxtonhale.sp::ClientTimer()
L 04/17/2012 - 20:27:27: [SM] Native "TF2_AddCondition" reported: Failed to locate function
L 04/17/2012 - 20:28:34: [SM] Native "TF2_AddCondition" reported: Failed to locate function
L 04/17/2012 - 20:28:34: [SM] Displaying call stack trace for plugin "saxtonhale.smx":
L 04/17/2012 - 20:28:34: [SM]   [0]  Line 2819, C:\sourcemod\saxtonhale.sp::HaleTimer()
L 04/17/2012 - 20:28:34: [SM] Native "TF2_AddCondition" reported: Failed to locate function

constant error spam in console after the new update

[pac_man0]

Originally Posted by nineteeneleven L 04/17/2012 - 20:27:27: [SM] Native "TF2_AddCondition" reported: Failed to locate function L 04/17/2012 - 20:27:27: [SM] Displaying call stack trace for plugin "saxtonhale.smx": L 04/17/2012 - 20:27:27: [SM] [0] Line 2727, C:\sourcemod\saxtonhale.sp::ClientTimer() L 04/17/2012 - 20:27:27: [SM] Native "TF2_AddCondition" reported: Failed to locate function L 04/17/2012 - 20:28:34: [SM] Native "TF2_AddCondition" reported: Failed to locate function L 04/17/2012 - 20:28:34: [SM] Displaying call stack trace for plugin "saxtonhale.smx": L 04/17/2012 - 20:28:34: [SM] [0] Line 2819, C:\sourcemod\saxtonhale.sp::HaleTimer() L 04/17/2012 - 20:28:34: [SM] Native "TF2_AddCondition" reported: Failed to locate function constant error spam in console after the new update

TF2 Items is currently broken I think.