Hi,
This issue is related to the Updating Marketplace Policy for Heads campaign.
here is a link to that devforum article. HERE
I’ve been going through my existing bundles to make sure their Dynamic Heads are updated for the new validation requirements, and I noticed that some of my bundles were never included in the update submission process.
In particular, I found this happening with several bundles that I published on January 26, 2026. The heads used in these bundles do not pass the current validation requirements, so I need to replace them with updated versions. However, I never received a submission or update link for these assets where I can provide the new Development Item Asset ID.
For example:
Tall Slim Blocky
Bundle ID: 17282011459977
link to the bundle in the marketplace. HERE
This bundle is still active, but I cannot find its head in any of the update forms that were provided to me.
I specifically noticed this with bundles I uploaded on January 26, but there may be other affected bundles that I have not identified yet, so I’m concerned that some existing heads may have been missed when the update campaign lists were generated.
On August 27 it was announced that September 1st was the last day we can manually submit changes, so I only have a couple days to get this issue sorted out.
I already have the ability to create corrected versions of these heads that meet the new requirements. The problem is that without an update link for the original assets, I don’t have a way to submit the replacement Development Item Asset IDs.
I also found another creator who appears to be experiencing a similar issue with Dynamic Head assets being missing from the update process, so I’m including that as additional context in case the issues are related. link to their bug report. HERE
Could someone please check whether these assets were omitted from the Marketplace head update campaign and provide the appropriate submission links, or another way for me to submit the updated asset IDs?
Thank you.
A private message is associated with this bug report