If I upload an image and it’s slightly off on my ImageLabel, now I have to go redesign it in PDN and re-upload as a new asset. If I upload audio that’s too quiet, I have to increase its volume and re-upload as a new asset. Every time I re-upload as a new asset, I now have to go through all instances of my game that use that asset and replace it with the new asset, potentially have to pay 100 ROBUX to upload small modifications to existing audio, and end up spamming my inventory with duplicate assets which don’t disappear from Develop even if I remove them from my inventory.
We should be able to update assets while they’re awaiting moderation and haven’t been reviewed yet. It won’t affect moderation, and nobody except you should be using them in their games, so there shouldn’t be any issue.
That’s a good idea, but it may make moderation hard, as moderators would have to accept every update of the asset. People could abuse this feature by constantly updating it, making it impossible for the mods to review it.
Moderators would only have to review one asset – assets would only be able to be modified before they’re reviewed. Once I upload an asset, it goes into the moderation queue. Moderators have to finish reviewing all other items in the queue before they even look at mine. If I change my asset 50 times before they look at it, they’re still only seeing one asset (the latest change) when my asset finally comes up on their screen. This change would make it easier on moderation since now they only have to review one asset instead of the four or five revisions I upload.
Or just let us update assets altogether, regardless of it being pre or post moderation. Then expose some kind of API to get a specific version of an asset in case you want to use someone else’s image/sound/whatever without the risk of them changing it.
If it will be possible to revert to previous versions, then moderators should review all versions. If not, they should just review the newest version up to that point, and all subsequent new versions after that.
> Uploaded really funny image a year or two ago
> Tons of people use it in their game now even though it’s private
> Image predates API for version so now it’s defaulting to using the latest
> I update the image to an advertisement of my game
Even if we did have an API, how would developers know to make sure to use that in their games? It’d have to default to the first version to prevent abuse, and then it wouldn’t be as useful because now you’re still having to manually update all occurrences of that asset in your game to use assetId&latestVersionNumber.
It could just create a new Image and link the new Image to the Decal instead of the old one, then the Decal keeps track of current/past Images so you can revert for example.
The only issue with that is that you can no longer do -1 continuously til you get to the Image, but that’s a gap in the API/website to begin with. Maybe the Decal configuration page could show a “Get!” button after each version that would copy the Image link to your clipboard or something. Either way, that has to be visible somewhere.
I don’t know how it would work for other types of assets, just suggesting that it may be useful if we can always update assets like that.
How would that work? Would decals only automatically update to the new image in my game? What if someone using a public decal of mine wants to opt-in for auto-updates?
No I’m literally talking about keeping an overview of your Decal assets in Develop by letting you update their Images. Instead of having i.e. 100x “Spritesheet v1”, …, “Spritesheet v100”, you could just have “Spritesheet” and then update it whenever you need to, it would create a new Image and link that as the current one. Then we can do your idea on top of it where you can freely update the Image as it is getting moderated. Perhaps we could even have a special type of asset link where you just link the decal ID and it would give you the latest version always.
Probably getting too far off-topic regarding the original suggestion though.
No this is fine. It would be weird to have one type of asset updating while they’re pending and another type of updating when they’re already approved, so it’s good to discuss and potentially discover a good middleground or even debunk the usefulness/feasibility of one so we’re only having to worry about one feature.
But then I would have to manually update all occurrences in my place. You suggested a special asset link that uses the latest version, but what if I release a model using that special asset link and then change an image in that model to something different when it gets popular?
I could see it work along these lines: the special asset link can only be used in the places by the owner of the asset (user/groups), and the individual links to the actual versions of the assets could be used by anyone like the way it is right now. I think this would mostly be a feature used by the owners of the assets anyway rather than other users. Those other users probably don’t even want the update thing like you mentioned before.
The link itself could be something as simple as rbxdecalid:// for decals (redirects to latest asset always), and then still use rbxassetid:// for the base assets that make up the different versions of the asset, if you want to link to a particular version. Audio etc don’t have a redirection yet while Decals do, so for newly updated audio they would need to make a similar redirection to a base asset, then they can do the same there. (and it would still be backwards-compatible)
That may even be more user-friendly/simpler for (new) developers, because they can just grab the decal id instead of the asset id, and if they update the decal it will automatically update in their games.
I’ve done that before and been burned where I restart studio and there’s an update or I leave it part-way done and studio updates before I finish and all of my assets are deleted. It wouldn’t be so much of an issue if I could put assets in My Documents or something, but anything in the content folder gets purged on update.
“[non-place owners couldn’t use rbxdecalid since other they don’t want it]”
At that point you should just use the game explorer and game assets. Upload an image as a game asset, and if you want to change it, delete the old one from the game explorer and upload a new one with the same name. All instances of that asset in your game will now be using the new asset.
What you can do is set up a simple program to copy a folder in the desktop to the latest version content, that way it’s organized and fast. Though I know this sounds crappy, if the only problem was your files getting deleted then this should be simple enough.
This is more of a feature request for making the usage of test assets a less painful process for users in general, so even though I could do that (I already have a custom launcher to mod in custom ribbon/reflectionmetadata xmls), it’s not scalable, and couldn’t be relied on by most users.
Honestly I think a dedicated folder where you can test your assets before uploading would be a better fix than yanking assets on the website around. Your problem was the sounds and images not looking right and then causing you to have to upload again. That could easily be remedied by a dedicated feature that lets you test your assets until they are perfect, thereby saving the mod team time and giving you more power and also saving you time and robux.
You should be able to update assets regardless if they are being reviewed. If you update lets say a decal it will go through moderation again to get approved. But still even if you can update them during the moderation period it would still be nice.
