Roblox is transitioning asset references from legacy string-based IDs to a new Content format starting November 11, 2026. While existing Luau scripts will remain compatible, developers are encouraged to use the new Content properties, and Rojo users must update to version 7.7.1 or higher.
Vibe score
-100 to +100
Thanks for the advance notice!
This topic was automatically opened after 10 minutes.
Penpen0u0: Reading and writing legacy property names in scripts (e.g., Decal.Texture ) remain fully supported and will not become read-only. However, we recommend using *Content properties (e.g. Decal.TextureContent ) as the source of truth moving forwar I am glad that this will not break old script
At first I was a bit concerned looking at this but since it’s gonna support legacy types this is good. I’m happy old games will likely not be broken. but hopefully it will soon support every documented format
I really appreciate the heads up regarding Rojo and external tooling - it’s great to see Roblox taking users of these kinds of tools seriously.
Thanks for the feedback! I tested this on my end and was able to successfully assign the example to a decal. Could you check if you are still able to reproduce the issue? .TextureContent should support everything that .Texture did! And Script-wise: game.Workspace.SpawnLocation.Decal.TextureContent =
This seems to be working now, I’m not sure when it got patched but it must’ve been done silently, thank you for confirming! Sorry about that.
does this improves performance in any kind of way (just wondering)
I much prefered when it was "ID’, not “Content”. The property names were shorter and easier to reference in scripts. Seems like another unnecessary change.
DoYouSeeMyHeart: does this improves performance in any kind of way (just wondering) Ghaucho: I much prefered when it was "ID’, not “Content”. The property names were shorter and easier to reference in scripts. Seems like another unnecessary change. Hi, this update is not performance-related, but it
Ohhhhn so this also means layered textures
Thanks for confirming! I’m glad to hear it’s working for you now.
How exactly can I extract what that asset ID refers to? From the post, this new “Content” is used to identify what that asset is. I believe this is good internally, but the Asset Manager already indicates what that asset is (image, mesh, animation, etc.), so I wanted to understand what I can do with
Hello! To clarify the first part of your post, Content doesn’t actually let you extract the asset type (like image vs. mesh) via scripts right now. It’s just a new container for the data, so the Asset Manager is still the place for identifying what an asset is. While this migration doesn’t introduce
Hmm, I understand, that seems interesting in the long term for new technologies in Roblox. Since you responded to my mistaken point, I believe it would be interesting if the Content returned the asset type. My question was to find out if this could be similar to the Asset Manager, which lists the as
Thanks for the feedback and the interesting idea! I will share this with the team, but since Content doesn’t support returning the asset type right now, you can use MarketplaceService:GetProductInfo(ASSET_ID) as a workaround to verify the Asset Type of an entered ID if needed. Hope this helps!
image 896×566 59.8 KB After updating to 7.7.1, deploying Jailbreak completely breaks the place file.
I’d prefer Id instead of content, but i understand the explanation. It will be nice to not clog the properties list with 2 types of ids now.
Hi, this error seems to be caused by bad format usage, potentially generated by external tools. Could you share more details about your deployment workflow? Is Rojo the only external tool you use for your experience, or are you also using other tools like Lune?