One thing I would have liked to have seen was bubble order based on message order. It means you would see the most recent messages in front of older messages even if they are physically behind another older message. Still good work.
If you have the old bubble chat in your game and enable the new one as well, these 20% of mobile users who are running a client older than the 451 release will see the old bubble chat, and the rest will see the new one
That doesn’t sound like a guarantee to me that there won’t be plans in the future for removing this support and I don’t like that very much. I’m not a fan of the fact that the bubble chat script has been moved to a CoreScript and I very much prefer the old chat due to being snappy and more fitting to my game’s aesthetic than the current one which feels too cartoony to fit.
If in the future there are plans to remove backwards compatibility, how exactly am I expected to continue self-supporting the old bubble chat with compatibility for ChatService’s Chat function (the one that allows NPCs to chat)? I should still be able to do that. This also includes writing my own bubble chat handler.
I don’t want or like the new chat nor its restrictiveness of customisability and I’m expecting to have it disabled on almost every single game I currently work on. That’s a hill I want to die on. If I absolutely have no choice with the new bubble chat, I am expecting to have it forked, along with the CoreScripts responsible for making it work just so I can change the code functionality myself.
This is one of the most exciting updates I’ve seen! I am so glad that you and your team were able to give more customization features that everyone has requested. The best parts of this update in my opinion is the ability to enable it with a toggle instead of the coding aspect and the customization features. Thank you so much!