Release Notes for 657

Hey creators! Here are the release notes for 657!

63 Likes

can’t wait to use the new string requires

9 Likes

When can Plugins open the color picker? :sob:
And is the Roblox storybook gone yet?

13 Likes

I’m excited for the new Decal.TextureContent property! Also cannot wait for EditableImage/EditableMesh replication to be announced.

5 Likes

Turns out that wasn’t a very long wait!

15 Likes

I can see this being abused to ban group owners and claim the group by untrustworthy developers.

24 Likes

I say revert this before it even goes live.

5 Likes

Its nice but moderation should be done on the person who has uploaded the asset, not the person who owns it

5 Likes

what does this even mean

4 Likes


I don’t see why this is a thing but it’s cool

3 Likes

TL;DR: We’re gradually migrating all of the asset reference properties from string → Content type.

This lets us reference content in more ways going forwards (the content property can reference a cloud asset, a WIP editable object in the place, or any number of other potential future sources such as a file on your disk)

Previously the only tool we had to work with was asset protocol formatting such as rbxthumb:// which was not scalable and semantically poor for tooling to interact with.

10 Likes

This doesn’t mean that rbxthumb:// will be removed, right? It’s currently the only reliable way for Players to set Custom Images without the Image asset id and not the decal asset id. Now that we have spoofed asset ids, incrementing to find images isn’t possible anymore so I hope this protocol remains intact or we receive something that supersedes it that can give Players the ability to enter their own Decal ids that get converted to the Image one automatically. This is used for numerous features like customization game passes and the like. In a game I work on, we use rbxthumb:// to retrieve custom nametag icons for players with access to the feature.

3 Likes

Ok, this is actually really cool.
Thank you tnavarts and the whole Roblox team for doing this.

2 Likes

It will stay, the content scheme isn’t to replace the asset protocols but to open up new possibilities we couldn’t accomplish with them.

FYI we implemented a replacement solution for this: Non-sequential Asset ID Generation Coming Soon - #103 by tnavarts

4 Likes

Got the potential ETA on texture instance types getting the content support?

1 Like

Why are there two of the same announcements?


1 Like

This can be SOOO useful though.

2 Likes

Exactly, either this should be reverted or they should definitely add the option for the place owner to decide whether they should get ownership or the user that uploads them

2 Likes

Editable decals AND a visual audio compressor editor is AMAZING!!
Love the bug fixes as well

3 Likes

Hi! This was a non-user facing bug in the Luau New Type Solver Beta that I mistakenly marked as developer facing. If you are not using the New Type Solver Beta, this won’t affect you. I will amend the release notes to remove this line item.

5 Likes