For the past 2 months (more perhaps, haven’t kept track)
These (client-sided) warnings have been constantly outputted and I’ve been looking everywhere for the source of this.
Hoping to get an update on this. This warning appeared 5.4 million times in my game within the last day…
Additionally, it clogs up the console and makes it harder for me to read debug messages.
I believe these are old messages from my admin command logging system which uses UI to display logged commands. The error occurs both in studio and in game, and on both the client and server.
This error first occurred roughly around the same time I installed Roblox Studio Mod Manager (so I could do units tests in studio), so perhaps the two are somehow related? The only thing I did was enable “FFlagEnableLoadModule”.
After loading into the main menu, press the Play button (topmost button on the left). You will be teleported to a server with an ongoing battle (or a new server will be made). Then check F9.
I suspect that this is happening because some entries in your localization table contains strings with bad parameterization.
For example, there is a double closing bracket }} in this string: {player1} set om{number1}r_obj's loadouts to {nat: {number2} reg: {number3} rnk: -{number4} uni: {number5}}.
If you delete the badly formatted strings from your table the warnings should go away.
I also understand that this string was automatically ingested so we are looking into fixing this bad parameterization in our pipeline as well.
Again, sorry for the bug and thanks for flagging it!
Thanks for looking into this! Some additional things I noticed:
I recognize some of the people that pop up in these warnings, and they haven’t played the game in a very long time; aren’t the automatic translations supposed to be cleared if not used for a while?
Additionally, I tried deleting the entire localization table a few days ago, but it did nothing and these warnings still appear.
Yes, the entries should periodically be deleted. I’ll look into why the warnings are still appearing if the entries have been deleted. I would also suggest turning Autolocalize off for the labels that contain usernames to prevent the entries from cluttering up your localization table.
I would like to advocate for the removal of these warnings entirely. The practice of Roblox inserting information into the output without a way to opt out is causing a lot of friction. They’ve made warnings in both studio (even running from just rbxl files) and the live dev console almost entirely unusable at boot - we have missed actual problems because our initial console is now just warning spam.
While it is of course good practice to resolve localization errors / remove instances from autolocalization, it is frustrating to have our hands forced on how much to prioritize it. I don’t want improvements to automated parsing, I want my output to only have errors, warnings, and prints from the code I wrote. I shouldn’t need to hunt down every instance in the game with a parsing issue in order to debug unrelated code.
I have had to delete localization entirely from our dev game just to be able to see my own warnings again, something which is less than ideal as our QA team is multi-lingual. Please fix this.
