Shirts not applying to ShirtTemplate

I’m putting a shirt’s id into a shirt template and it stays blank. Like it literally won’t change no matter what I do.

Expected behavior

I expect the shirt to be applied…

5 Likes

Hey @hothead522, this is a really common issue. Here’s likely what’s going wrong:

You’re probably using the Shirt item ID from the catalog, like:

https://www.roblox.com/catalog/123456789/Shirt-Name

But ShirtTemplate doesn’t use that. It needs the image asset ID, which is often different.

Here’s how to fix it:

  1. Go to the shirt’s actual asset page (click the shirt, right-click the image, and open it in a new tab).
  2. The image URL will look like this:
https://www.roblox.com/asset/?id=987654321
  1. Use that ID (987654321) in the ShirtTemplate, like:
shirt.ShirtTemplate = "rbxassetid://987654321"

That should work immediately — just make sure the shirt is approved and not private.

Let me know if it still doesn’t show up and I can help further.

4 Likes

I second this bug, there is an underlying issue you might not see if you don’t have the output open:
Failed to load image. User is not authorized to access asset.

I just uploaded the asset so I definitely have permission to use the shirt

1 Like

Same thing here!

Normally you’d get the ID from the URL and paste it in the Shirt (or Pants, or Shirt Graphic) instance and it’d automatically apply the shirt onto the character.

image

Instead I’m somehow getting this in my output, regardless of whether it’s uploaded by me or not
image

Dunno why and since when this is a thing, but it’s again complicating more things in the studio workflow…

1 Like

Roblox recently released an update which makes it so users have to have access to an asset, an announcement was made not to long ago: Expanded Sharing for Assets

1 Like

Thank you for the report. This is an acknowledgement message. We have assigned to our team for further review.

1 Like

Hello, @starhiker13!

Just a question because I am unsure is this new update I listed above a possibility that could be effecting this?

We’re glad to let you know our team has resolved this issue and deployed a fix! Please check on your side and let us know if you are still encountering this issue. Thanks!