Asset Update Manager
InvestigatingRoblox · Studio Plugin
A plugin that remembers which Studio objects map to which published asset IDs, and lets you push updates, keep a history, and check things before publishing.
This is a score we use to sort ideas, not a chance of success.
The problem
Updating an asset you already published means going through the same upload and configuration steps again, even though Roblox has an API that can just push a new version.
Demand
A few examples
24 likes · 829 views
28 likes · 998 views
30 likes · 1,351 views
2 likes · 66 views
2 likes · 47 views
Likes and views just show attention, not how many people would pay for this.
What already exists
We searched the Creator Store for plugins that could compete with this and looked closely at 13 of them.
This tracks reusable assets and pushes changes to model instances, which covers part of the pain. It does not look like it publishes new Creator Store versions by asset ID, checks things first, or keeps a history.
What might still be missing
We found a plugin that tracks reusable assets and updates model instances when they change. We have not found one that also handles asset ID mapping, bulk publishing, checks and history together.
Can it be built?
Roblox has an API, CreateAssetVersionAsync, that publishes a new version of an existing asset. That is exactly what this idea needs.
This is our best guess from reading the public APIs, not a guarantee. Roblox can change its APIs at any time.
Commercial notes
These are guesses, not proof anyone would pay.
- Why it might be worth it
- This solves a specific, recurring job for professional developers, and the API for it already exists.
- Who it's for
- Developers and studios who publish and update a lot of shared assets.
- How it could make money
- Paid plugin, likely aimed at professionals or small studios.
- What would make it different
- Instead of one button that updates one asset, this remembers your assets and can update several at once, with a record of what changed.
- How much work it'd be
- The core publishing API already does the hard part. Most of the work is safe mapping, clear upload feedback, and handling several assets at once.
- What could go wrong
- Roblox could change publishing permissions or the API itself. Needs careful handling of ownership, asset types and failed uploads.
Current take
We found a plugin that covers part of this job. We have not found one that combines asset ID tracking, bulk publishing, checks and history in one place. Worth asking developers before building.
This status reflects the current evidence and can change as we learn more.
Know something we missed?
Found an existing solution, technical limitation, or stronger evidence for this opportunity?
Challenge this research →