We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Teams type "!ready", -> game starts.
Game doesn't start after both teams have written "!ready".
Console.log throws: L 11/06/2018 - 20:00:24: [SM] Exception reported: Failed to lookup SetClanTag signature. L 11/06/2018 - 20:00:24: [SM] Blaming: get5.smx L 11/06/2018 - 20:00:24: [SM] Call stack trace: L 11/06/2018 - 20:00:24: [SM] [0] CS_SetClientClanTag L 11/06/2018 - 20:00:24: [SM] [1] Line 259, ./scripting/get5/readysystem.sp::UpdateClanTags L 11/06/2018 - 20:00:24: [SM] [2] Line 635, ./scripting/get5.sp::Timer_CheckReady
Nothing to note in sourcemod-logfile (addons/sourcemod/logs).
All and any information/suggestions appreciated :)
The text was updated successfully, but these errors were encountered:
Sourcemod issue.
Wait for alliedmodders/sourcemod#922 to be resolved.
Sorry, something went wrong.
No branches or pull requests
Expected behavior
Teams type "!ready", -> game starts.
Actual behavior
Game doesn't start after both teams have written "!ready".
Steps to reproduce
https://raw.githubusercontent.com/bryggemesel/angrytesti/master/match2.json
Console.log throws:
L 11/06/2018 - 20:00:24: [SM] Exception reported: Failed to lookup SetClanTag signature.
L 11/06/2018 - 20:00:24: [SM] Blaming: get5.smx
L 11/06/2018 - 20:00:24: [SM] Call stack trace:
L 11/06/2018 - 20:00:24: [SM] [0] CS_SetClientClanTag
L 11/06/2018 - 20:00:24: [SM] [1] Line 259, ./scripting/get5/readysystem.sp::UpdateClanTags
L 11/06/2018 - 20:00:24: [SM] [2] Line 635, ./scripting/get5.sp::Timer_CheckReady
Nothing to note in sourcemod-logfile (addons/sourcemod/logs).
All and any information/suggestions appreciated :)
The text was updated successfully, but these errors were encountered: