One of my developers of our system Guardsman (MainModule) recently was debugging a workflow we have on our Git repository to automatically push the latest RBXM from source to the asset. After the workflow sent the request, we noticed that our asset had been converted to a package randomly. We’re unable to revert it to a model, even using an old version from version history, and it doesn’t show up as a model anymore when overwriting an existing asset from Studio.
The RBXM that’s being uploaded is built via Rojo. The source does not have any PackageLinks within it. The type on the creator page displays as a Model, however it’s also marked as updateable.
Expected behavior
Typically we’d expect the model to be uploaded as normal.
I’m also able to reproduce the bug, I tried uploading a model through the Assets API on a test account and it uploaded as a Package. (Also shows as Updateable)
Hey there, we have fixed the issue with PATCH requests to the Assets API changing the package status. Updates will now keep the same package status as the original model. Please let us know if you encounter any issues.
By default, all models initially uploaded through the Assets API (POST request) will be uploaded as packages. We are in the process of allowing users to configure this behavior, but we don’t have a timeline on that yet.
Perfect, thanks! Is there any way to have our MainModule reverted from a package? Its used in our loader asset that previously was distributed on the marketplace, so there’s a lot of people who are using our backup module at the moment. (https://create.roblox.com/store/asset/125399000917510)
Sorry for the delay. Unfortunately, we don’t have a good way of reverting from a package. We are working on a method to enable this functionality but not sure on how long it will take.
