A service for saving Studio specific objects

[metatablecatmaid (metatablecat)]

As a Roblox developer, it is currently too hard to persist Studio-only objects such as template items for a plugin, or debugging tools that would only be usable in Studio.

The issue lies in the lack of a reliable storage service that persists in the place that isn’t also usable by a live game (only loaded in Studio).

StudioService can be used to store objects from plugins but it does not persist between sessions since StudioService doesn’t save its child members.

If Roblox is able to address this issue, it would improve my development experience because I could save studio-only objects in a place file and keep it around for future usage.

[SomeScripter3]

Maybe put your studio-only models outside the playable map or save it as a different model you can insert and delete when no longer using?

Still would be cool if there was a seperate storage for that

[Doomcolp (dxxmed)]

This sounds really cool! I hope they consider it!

I have a bunch of ideas on what I could do with this service if it is released!

[metatablecatmaid (metatablecat)]

Felt like bumping this after this just happened

Important changes for the Animation Clip Editor AnimSaves folder

Hello Developers, In January 2024, we will be making changes to how the Animation Clip Editor saves local animations and how published animations are handled to improve experience loading times. The Animation Clip Editor currently saves its animation data under the animated rig in the data model. Unfortunately, those saves can add significant weight to an experience’s size and load time, resulting in a weakened player experience, especially on lower end devices. So, we are making three changes…