-
Notifications
You must be signed in to change notification settings - Fork 79
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
Client error related to translations #1695
Comments
I have a loose idea of what might be going on here, but i haven't been able to reproduce this yet that player probably tried to pickup a radio/visualizer/decoy/beacon that didn't belong to them, could that be correct? |
Fixes #1695 We call `LANG.Msg` on the client which doesn't have a way to address a specific player, therefore we have used wrong parameters here.
Fixes #1695 We call `LANG.Msg` on the client which doesn't have a way to address a specific player, therefore we have used wrong parameters here.
Yes that could be it, there were beacons placed by a Detective who wasn't the player who got the error. |
Fixes #1695 We call `LANG.Msg` on the client which doesn't have a way to address a specific player, therefore we have used wrong parameters here.
We call `LANG.Msg` on the client which doesn't use the first parameter to address a player. This shifts all the parameters to the wrong places. Fixes #1695
Your version of TTT2 (mandatory)
Describe the bug (mandatory)
The issue appeared for the first time for only one player. He got an error which is related to translations. We don't know why this error happened because we only noticed it later on. Maybe it is an edge case like dying/disconnecting/... at the time the code tries to run or something in that direction. There could be a missing check at the code section.
To reproduce
Steps to reproduce the behaviour:
Expected behaviour
This error shouldn't appear for the player.
Context (please provide as much as you can)
Additional context
We never saw this error in prior TTT2 versions.
Maybe it is only an issue in TTT2 v0.14.0.
The text was updated successfully, but these errors were encountered: