Closed aarmastah closed 3 months ago
Same issue here, the problem seems to be related to the "connect" extension. Since stac requires it, the only "workaround" for now is to disable it. (Tested on Debian bookworm, 32bit server executable)
Here's the issue from the Connect extension: https://github.com/asherkin/connect/issues/19
Seems like there's not much to be done on the StAC side right now (maybe at all). Hoping an update to Connect fixes it 🤞
StAC could temporarily remove the Connect extension, but that does mean the validation it does is removed as well. Sub-optimal, but a stop-gap that might be worth considering if Connect takes too long to fix.
I personally managed to get past the message with a simple recompile of Connect, but I also am not entirely sure if it is doing what it's supposed to or was simply broken by doing that.
My compile was with this commit (asherkin/connect@7cc832e
(#15)) on Linux using these exact commands.
git clone --recurse-submodules --depth 1 https://github.com/alliedmodders/metamod-source/ -b 1.11-dev
git clone --recurse-submodules --depth 1 https://github.com/alliedmodders/sourcemod/ -b 1.11-dev
git clone --recurse-submodules --depth 1 https://github.com/alliedmodders/hl2sdk/ -b tf2 hl2sdk-tf2
python configure.py --enable-auto-versioning --enable-optimize --sdks="tf2" --mms-path="metamod-source" --hl2sdk-root="./" --sm-path="sourcemod"
ambuild```
The other possibility is to downgrade to StAC v5.4.3 which doesn't use connect yet. Not ideal either, but better than nothing.
Connect is being actively worked on by other members of the community and I have merge access to the repository, it will be ready when it is ready, just be patient please!
After yesterday's first update, when StAC is installed on a TF2 server and run (using the 32-bit executable), it results in the error message "STEAM validation rejected" shown to all clients:
(Tested using Ubuntu Server 22.04)
I tried reinstalling plugins on a clean SourceMod install one by one to isolate this issue to StAC. Additionally, nothing shows up in my server console when players attempt to join and receive this error. Let me know if anything else is needed for debugging/troubleshooting and I'll do my best to help.