You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think I found a little bug. Hard to test alone though ;)
If players connect after .setup is already completed, they first get a [NOT READY]/[READY] as clantag.
When the game is live, their original clantag isn't restored.
All players, that were on the server, before the initial .setup is done, get their original clantag back. Just the ones connecting, when ready-process is already ongoing, have this issue.
I'm using the latest commit and SourceMod Version: 1.7.3-dev+5290
Would be cool, if you can fix it somehow 👍
The text was updated successfully, but these errors were encountered:
I know why this occurs: the plugin saves the clan tag right before setting the "Ready" or "Not Ready" text, but the client doesn't always have their original clan tag set when that happens. Presumably it happens after the normal connection/authorization period.
It just needs some logic for checking when the tag is originally set, and to save it there. One fix would be the suggestion in splewis/csgo-multi-1v1#117 but that requires being on the dev/1.8 sourcemod branch.
I think I found a little bug. Hard to test alone though ;)
If players connect after .setup is already completed, they first get a [NOT READY]/[READY] as clantag.
When the game is live, their original clantag isn't restored.
All players, that were on the server, before the initial .setup is done, get their original clantag back. Just the ones connecting, when ready-process is already ongoing, have this issue.
I'm using the latest commit and SourceMod Version: 1.7.3-dev+5290
Would be cool, if you can fix it somehow 👍
The text was updated successfully, but these errors were encountered: