UGC emotes are currently failing to submit because newly published animations are reported as missing a valid UGC emote marker.
When uploading an animation as an Avatar Item > Emote, Studio initially shows “Validation Succeeded”. However, after submitting the emote, the submission fails with the following error:
“Content does not pass validation rules: The published animation is missing a valid UGC emote marker. Please republish the animation.”
Republishing the animation does not resolve the issue.
Steps to reproduce:
Create a new standard R15 Mannequin rig.
Open or import the animation in Animation Editor.
Make sure the animation is a CurveAnimation.
Publish the animation as a completely new asset.
Enable “Create Animation Object In Workspace”.
Set Animation Type to “Emote”.
Use the newly published Animation object.
Upload it using Avatar Item > Emote.
Studio reports “Validation Succeeded”.
Submit the emote.
Submission fails with the “missing a valid UGC emote marker” error.
I have reproduced this with multiple animations and completely new animation asset IDs.
I have also tested:
A brand new standard R15 Mannequin
CurveAnimation
Animations under 10 seconds
Animation Type set to Emote
Completely new animation asset IDs
Newly created Animation objects
Republishing multiple times
The same error occurs every time.
This issue is currently affecting multiple UGC emote creators, not just my account. Other UGC emote creators are reporting the exact same issue here:
I started experiencing this issue after the recent Animation Editor / UGC emote publishing changes.
Beta Features:
No relevant beta features are required to reproduce the issue.
Expected behavior
A newly published CurveAnimation using a standard R15 rig and published with Animation Type set to “Emote” should contain the required UGC emote marker and be accepted for submission as an Avatar Item > Emote.
After Studio reports “Validation Succeeded”, submitting the emote should complete successfully instead of failing because of a missing UGC emote marker.
There hasn’t been an update to Roblox Studio—I’m still using version 0.736.0.7361346 (64bit). So Roblox must have changed something on the backend in the meantime.
Glad it worked, but once you’re on 737, you will have to publish your animation with Create Animation Object In Workspace and have asset type set to Emote