I’d first like to clarify that Failed to translate string with key: InGame.ConnectionError.DisconnectClientRequest is unrelated to the Invalid entry error you mentioned in the previous thread.
Are you still encountering the Invalid entry error? We believe we’ve made changes that should fix this long-term for new localization table entries, but please provide additional details if you’re still seeing this.
But the previous thread did also report the Failed to translate string with key: InGame.ConnectionError.DisconnectClientRequest, which disappeared after the last fix, but has returned (and confirm still appears in the last day).
Hey @RuizuKun_Dev - this seems like a separate issue from what was reported in the initial post. If you’re still encountering this problem, please file a separate bug report so we can track appropriately. Thank you!