One aspect of the “migration” component that’s worth delving into more detail is the mechanics on how it is intended to work.
The current strategy is not to simply set the TextChatService.ChatVersion to TextChatService, as that has a potential of breaking and disrupting many older experiences.
Instead we are exploring a “compatibility mode” that will continue running your old legacy chat scripts in the background but preventing them from being visible. This will work most often if your chats are integrated well into the top bar’s chat button. In case we cannot hide your old chat, we also plan to no-opt the ChatService:FilterStringAsync and TextFilterResult:GetChatForUserAsync responses to be an empty string. The plan is to instead show the default TextChatService UI in place so users can still socialize in experiences that were not able to be updated in time.
Running two versions of chat in an experience is non-ideal, even if one is hidden, so we do ask that if creators can they manually migrate to TextChatService for the best results, however Roblox is committed to backwards compatibility.