Hello again!
Thank you for all of your feedback. I wanted to answer some of the FAQs I’ve seen here in the comments to help provide more color to this experiment.
First and foremost, why are we running this experiment?
In our research, we have gathered that bridging the language barrier gap will exponentially help us reach our goal of joining communities globally and we wanted to ensure that all of you were able to do so with the click of a button. Therefore, we want to test our automatic translation services at scale. We have already run a series of small scale experiments that have given us positive directional signals and believe that this large one will do the same. We want to assure you all that throughout the course of this experiment, our team will be monitoring metrics closely. We have your best interests in mind and want to make sure you all succeed so if we get negative signals, we will pull back our experiment!
For those of you asking, why is this experiment opt-out? For all of us to have the greatest understanding of the impact of automatic translations in game, we need this test to be run on a large percentage of playtime for international players. With more players and playtime coverage that we get in this test, we will be able to best accurately judge our translation features and worldwide impact.
How does this experiment impact existing localization systems and settings?
If your game has custom localization systems in place that use embedded tables OR you have already been managing a cloud localization table with existing translations, those will ALWAYS override translations in our experiment. Any translation work already done will not be lost and you can continue to add translations to your game which will override translations set by our experiment. Our experiment is meant to fill in any blanks and translate text that hasn’t already been handled by each developer. That being said, at this time, we will be overriding developer settings for Automatic Translations that may have been set in the Configure Localization page.
Also, if you have the AutoLocalize property on GUIs set to be false, we will be respecting that setting. If your game has custom chat capabilities, we ask that you set the AutoLocalize property to be false so that it will not get translated. More info available here.
What content will be translated?
At this time, this experiment will only extend to in-game text. So, it will not include images or content like game info/products. Additionally, we will not be translating system in-game chat although that is something we are exploring for the future.
What languages will this experiment run in?
Spanish, French, German, Portuguese, Japanese, Korean, Simplified Chinese and Traditional Chinese.
How does this impact translators?
Translators are, and will always be, a valuable part of our Roblox ecosystem. Their ability to provide contextual translations often yields higher quality results than an automated system. That being said, we know that not every developer has the luxury of outsourcing and paying translators for their services. To that end, we want to provide built-in product functionality so all developers can reach global players. If you are a developer that has the ability to hire a translator for your game, we encourage you to continue to do so. We previously built features specifically for human translator workflows (Web Translator Portal, translator contribution reports, etc) and will continue to keep them in mind as we develop our translation services going forward.
Thank you again for being a part of our international efforts. As Roblox looks to expand our global reach, we want to make sure you all are part of this journey.