Over the past couple of months, the community has observed Roblox pushing out changes that negatively impacted workflows immensely, and this has to stop. As Roblox grows, so does the responsibility to treat the community right. I have gone ahead and listed numerous cases where they seem minor, but hurt developers like myself trying to use the platform full time (I am a current accelerator). Communication & transparency are key factors towards preventing issues with disrupting workflows - and I’m sure the community would be glad to help describe their workflows to help.
Script Editor String Highlighting
Not long ago, a Roblox update broke string syntax highlighting in the script editor. This is an extremely important feature as otherwise, the script becomes a blend of white that is painful to read. This bug was extremely pervasive, as it happened for every string in every script, and there was no workaround. a way to fix this was eventually discovered on the day of release, but Roblox had originally said that it could only be fixed in 2 weeks. There was a mismatch in importance where Roblox judged that the bug was minor enough to wait 2 weeks while for users this was something that needed to be fixed ASAP (it was the 2nd most upvoted studio bug this quarter). Had the impact of the bug been better assessed, perhaps Roblox would have considered an emergency release rather than waiting 2 weeks?
Asset Manager
A couple of months ago, Roblox took the Asset Manager out of beta & got rid of the Game Explorer, without listening to the community or providing the same functionality as the game explorer. Bugs & general UX feedback was provided in the thread during the beta feature period, but the feature was released without a resolution to that feedback. Ultimately the feature had to be rolled back because there was a misalignment on Roblox’s assessment of Asset Manger’s bugs/benefits vs users’. If this was better assessed, the feature would have had a smoother rollout without changes that negatively impacted users being prematurely rolled out on a global scale. This rollback was met a week after this was deployed.
Some Asset Manager Reports
Reports/features dating back before the asset manager was moved out of beta and were never solved:
Asset Manager is Here (BACK IN BETA) - #23 by filiptibell
Asset Manager is Here (BACK IN BETA) - #114 by Kullaske
Asset Manager is Here (BACK IN BETA) - #112 by DobDobDev
Asset Manager is Here (BACK IN BETA) - #107 by Quenty
Reports talking about their workflows being hindered:
Asset Manager is Here (BACK IN BETA) - #145 by michaelvanderfin
Asset Manager is Here (BACK IN BETA) - #169 by Veldaren
Asset Manager is Here (BACK IN BETA) - #180 by pa00
I could go on and on linking various threads and replies, but for the sake of everyone here, I won’t.
Packages & LinkedScripts
Packages were meant to supersede LinkedScripts, but to this day Roblox is forced to continue supporting them because Roblox and users did not agree on the importance of Packages shortcomings. Now LinkedScripts and games keep breaking because Roblox does not support them first-class anymore, and Roblox has also not allowed us to switch away from LinkedScripts to Packages because not all features of LinkedScripts are adequately supported by Packages. Had Roblox better determined the importance of these shortcomings of Packages and features of LinkedScripts, perhaps we would have had a more gracefully transition period where LinkedScripts and games were not broken until Packages were a viable alternative.
Changes to Non-ReplicatedFirst Loading Order
Earlier this summer, an update to the loading order of rendering UI occurred, and this directly affected me & my games. I received numerous reports about UI being wack and not displaying correctly. To my surprise, Roblox had pushed an update without an announcement. I replied to the thread along with others talking about my issue. Shortly after reports started to fall in, this change was reverted. There seems to have been little testing since I was contacted directly after about my issues so Roblox could understand it - which is fine, but this was pushed to production. It negatively affects developers when we have no control over things like this and have to manually go in and fix the issues.
My game interface:
The broken version:
Notice the Text Shadow I have going on at every text element:
The original version:
See how this is fixed?:
Loading issues were also a problem with this change. Reports of longer join times started to appear across the forum - but nothing was announced. Transparency with this would resolve a lot of these issues & not let us think that we messed up.
Studio closing for updates
Currently, a raised issue that persists & gets posts a whole year later has had little feedback towards making this work better. This especially impacts our workflow. For example, I often need to copy code from one place to another, so I need to have multiple studio windows open. However, if studio updates while I am opening a place, all my other windows are closed and any unsaved work I had is lost. It’s frustrating and I must stress how this negatively affects not just me, but everyone who has replied to the thread.
Overall, the miscommunication and lack of transparency presented here can be fixed by working together. We should be able to help out by presenting our workflows & how we use tools when asked. Over the summer, I, along with some others, was invited to talk to product about issues we had - and it was fantastic. I loved meeting with them and showing my workflows & how I use tooling. This transparency felt great and I know not just me would love to help Roblox by describing their workflows & how they use tools.
Transparency shouldn’t just be focused on the DevForums, either. There are thousands of developers who don’t actively use the forums and remain using the What's New
button in studio located on the top right. This would be the most efficient way to reach out to everyone - and not just quiet announcements on the forum.
Opinion: Following a Community-based Model
Some of the biggest issues with how Roblox communicates with the community comes down to transparency with future updates & not completely understanding how developers work - which is ok because we can improve upon this with transparency. Being aware of what workflows developers have and how we use the tooling provided is a great step towards moving in the right direction!
A framework that follows a similar pattern is STRIDE, used within security software. As such, STRIDE modeling provides a little preparation that can help you identify blind spots in your application’s security. This is a great idea to focus on, giving preparation to what is expected of in our workflows and how these changes impact our workflows.
TL;DR: Read the post and reply with some of your frustrations - we should be transparent to help Roblox be transparent.
Special thanks to @codes4breakfast and @LMH_Hutch for the help in organizing feedback & reviewing.