Howdy!
I’m the current maintainer of the backend parsing libraries used by Rojo. It’s involved a lot of work on our end to reverse engineer Roblox’s file formats and I was wondering if going forward we can expect more support on that front.
One of the main issues has been that historically, Roblox operates as if they are the only consumers of files. This has caused us a lot of stress over the years because it means we have to quickly react to unexpected and breaking changes in the file formats that directly impede the ability of our users (which include the teams behind Adopt Me! and Jailbreak). This has happened before but happened recently with the new font system and model scaling. Had it not been for an engineer touching base with us outside of his work, we would have had no warning and models would have broken for all of our users. Fonts did break.
While I know Roblox’s policy has been to develop things in house to make things easier for their users, that solution is a ways off still. I’d like to know if Roblox would be open to engaging with a more friendly dialog with Rojo and it’s maintainers than it has historically (I’m more than open to discussing this in DMs if you don’t feel comfortable commenting publicly, as I know there are some complex feelings towards Rojo at Roblox).
If that’s not possible, what does the future of Roblox’s own tooling look like and can we expect compatibility with Rojo at least?