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.
Last checked:
The problem
Keeping track of existing asset IDs and publishing controlled updates can still require repetitive setup. Reimporting an external file is not the same workflow as publishing a new version of an existing asset.
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
The existing Asset Manager competitor covers part of asset reuse and model-instance updates. The remaining investigation concerns existing asset IDs, controlled bulk version publishing, validation and history.
The original targeted Creator Store search reviewed 13 plugins. Plugin prices, votes and update ages below are from that original search where recorded. Later findings are described alongside 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.
Native platform overlap
Roblox Auto-Reimport Beta watches external files and reimports them when they change. It currently creates new asset IDs rather than versioning existing assets. Roblox has indicated work toward asset versioning for meshes and images, which could reduce this remaining gap.
What might still be missing
The remaining gap is narrower than before. Roblox now provides Reimport and Auto-Reimport workflows, but Auto-Reimport currently does not provide the full existing-asset versioning workflow proposed here. Asset ID tracking, controlled bulk version publishing, validation and history may still provide value.
Can it be built?
CreateAssetVersionAsync supports publishing a new version of an existing asset. Reported failures for models containing unions are a current implementation risk worth testing, not a permanent platform limitation.
This is our best guess from reading the public APIs, not a guarantee. The confidence estimate concerns technical feasibility only. Roblox can change its APIs at any time.
Commercial notes
These are guesses, not proof anyone would pay.
- Why it might be worth it
- Asset ID tracking, controlled bulk version publishing, validation and history may still save recurring work, but the remaining gap is narrower as Roblox expands its native tooling.
- 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
- The remaining hypothesis is controlled publishing to existing asset IDs, with bulk operations, validation and history. Roblox already provides Reimport and Auto-Reimport workflows for changed external files.
- How much work it'd be
- CreateAssetVersionAsync supports publishing a new version of an existing asset. Asset ownership, supported types, failed uploads and reported union-related issues need practical testing before relying on a bulk publishing workflow.
- What could go wrong
- Roblox native tooling is moving toward this workflow, and future mesh/image asset-versioning improvements could substantially reduce the opportunity. CreateAssetVersionAsync has reported issues with models containing unions; treat these as current implementation risks to test, not permanent platform limitations.
Current take
Roblox now provides Reimport and an Auto-Reimport beta for keeping external files synchronized with Studio, but Auto-Reimport currently creates new asset IDs rather than providing the full existing-asset versioning workflow proposed here. Roblox has indicated that asset versioning improvements are being developed. A workflow around existing asset IDs, bulk version publishing, history and validation may still be useful, but the native tooling is moving quickly toward this problem.
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 →