As a Roblox developer, it is currently too hard to:
Identify when and how specific changes were introduced, especially when features in Release Notes are often marked with statuses like “Pending” or “Live.” This makes it extremely difficult to track down the change that caused issues in my game, such as the one that recently broke all “baby” characters,
even in save files from months ago. I had to go through dozens of Release Notes, many of which still list features as “Pending,” without being able to pinpoint the issue.
^^ Note: This has already been fixed by me in our game, an unknown change made all babies alot lighter, normally the baby should be able to easily open the door
If this issue is addressed, it would improve my development experience because:
A centralized website tracking update history, feature rollouts, and changes to statuses like “Pending” or “Live” would allow me to quickly determine the root cause of issues stemming from updates. This would save significant debugging time and reduce player disruption. It would also provide more clarity of changes.
Use Case 1:
An unidentified change recently broke all “baby” characters in our game, even in save files that are months old. The bug likely stems from a recent update, such as a physics or animation-related change. However, tracking this down is nearly impossible because the Release Notes contain dozens of entries with unclear statuses, and no historical context for when pending features went live or were adjusted.
Use Case 2:
While reviewing the Release Notes to identify the cause, I encountered a large number of notes where features are marked as “Pending” or “Live.” This lack of detail and tracking history makes it challenging to correlate changes with issues in my game.
(I went through a dozen release notes before giving up)
Additional Feedback:
It would be helpful if there were a dedicated website that not only listed Release Notes but also provided an update history. This would include:
A clear timeline of when features marked as “Pending” transitioned to “Live.”
Details on whether features were later adjusted, rolled back, or changed further.
Maybe including DevForum posts/ Documentation links to changes if present
They used to have “hidden” FFlags inside of the release notes until earlier this year (inside the raw release note JSON files). I would usually look (and sometimes track) the value of those flags. It wasn’t perfect (sometimes changes didn’t list a flag, weren’t behind a flag, or became superseded by a different flag), but it was far easier to pinpoint these issues.
Now, I have to search for FFlags based on keywords from release notes, which while possible, isn’t something I should have to do.
