-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WCS doesnt work on brand new server - CSGO #93
Comments
I'm having the same issue and my server was working fine yesterday. I think it may be useful to open a issue on the Source.Python repo since the problem is with SP and not the mod per se. |
TL:DR for the other issues: Use SourceMod 1.10 not 1.11 |
I'll test with SourceMod 1.10, thank you! |
wcs menu seems to work now @Phoross thats great! I am struggling with autoexec'ing my es emulator.. My autoexec: (as per the guide i followed) |
There was a change on the autoexec due to this bug! You just need to redownload the autoexec from the EventScript repo and it should be fine! |
Hello @eriksen080499, What is going wrong in your installation is probably caused by the autoexec.cfg.
If this solved the problem then let me know. Also you can get help on the Warcraft-Source discord server, if you are not already in it then here is a link to join it😄 |
As this has been solved, I'm going to close it. Use SourceMod 1.10 until there's a new stable release. |
Hi, i am not sure if this is the correct place to ask for help, but here goes.
A friend and i just installed a new CSGO server.
We followed the installation manual as described, but WCS doesnt work at all when using it.
As soon as i type "wcs" ingame server console begins spamming this error:
I have tried removing/uninstalling everything and doing it again, and reinstalling C++ 2010 and 2015 as per instructions from source python, and sourcemod/metamod. Originally we tried with Eventscripts as well, but as that didnt function at all, we tried with just the CSGO server and WCS provided by here.
Any help?
The text was updated successfully, but these errors were encountered: