bump, this is still super needed
1 Like
please add. been wanting this for years now.
1 Like
I’ve been wanting this for so long time now. So I am going to bump this since this is still not added
2 Likes
I’m still waiting for this, this is super useful to set custom assets to Components, sucks to need to use an ObjectValue instead
1 Like
I agree, attributes really need support for near all types, it’s such a good feature that is done so terribly by the limitations its put into
While Roblox hasn’t fully supported this feature yet I have made something that you can use in the meantime
couldn’t the attribute just reference itself or workspace when its created?
That would lead to undefined behaviour (aka, your code doing what it was never intended to do), other instances should never be used as a “missing instance” value
I just ran into this and it creates a weird disjunction between my code which relies on attributes, and some parts of my codebase which now relies on ObjectValue children.
1 Like
This really should be a feature, it’s weird having to mix Value and Attributes.
4 Likes
The problem with instance attributes is using them inside of Studio, I’m just saying put a placeholder when you create it in Studio.
I’m struggling to find the words but basically, if Instance attributes were only created/edited through code there wouldn’t be an issue here, therefor the problem isn’t with Instance attributes its with Studio.
I see it as no different than numbers defaulting to 0 or Color3s defaulting to white.
This would be useful, for in game, I had to resort to generating unique IDs for everything and using that to reference an object but if they could somehow get this into studio/engine, it would definitely be beneficial and time saving.
2 Likes
That would just be an Enum attribute type, and allowing users to create custom Enums.
It’s been years and it’s still not added. It’s fine tho, we got AI generated avatars. I’m sure that’s what Roblox needs right now
Why not make this a scriptable only feature, like Enum attributes? It would solve the issue of not being able to unassign an object from the attribute without removing it altogether.
I think it makes the most sense to just have the attribute be gone when the instance is nil, that makes the most sense. If you’re not assigning an initial instance it should just be done through code.
To this day I am still waiting for this 
. The only way to get around this is to class a objvalue value and parent it to the instance you want to have the instance attribute, then you can create a string attribute with the name of the objvalue, and get that.
3 Likes
ROBLOX WAKE UP!! It has been years we have been waiting for you to add a single TYPE to attributes that will be GAME CHANGER!
Still confused as to why this isn’t added.
Please prioritise this.
Wait you can save tables to attributes?! my life is a lie. Why did it never work for me then I’m such an idiot.