Create an “ObjectValue” attribute

Feature Requests Engine Features
#3

Thanks, but in practice, regardless of any justifications, the fact is that if it is currently possible to store an instance inside an ObjectValue property, it is not difficult to do the same for attributes. It’s just a matter of goodwill

13 Likes
#4

This feature would be very useful with package configurations. Currently, using ObjectValue as a child of the package marks the package as modified. :confused:

6 Likes
#5

Bump since this is very good addition and saves alot of time.
so its back on the radar.
just very convenient.

2 Likes
#6

huge bump, having to deal with using modules and item tables to point towards objects in-game when this could’ve already been a thing

3 Likes
#7

Looking forward for this to be added, would be useful for my project I’m working on right now! :pray:

2 Likes
#8

Would love this to be added
yea bump

2 Likes
#9

Another bump - pleaseeeeeeeeeeeeeeeeeeee add this

I’m trying to use attributes more in my coding to utilize user-friendliness, their replication efficiency and their compatibility with Streaming Enabled. But the major flaw is not being able to set an instance as an attribute.

2 Likes
#10

Same. I also struggle to think of substantial barriers to adding the feature. I may be mistaken but given that objects are already properties, such as in constraints, I think most of the work is done already.

1 Like
#11

The issue is the “initialisation state”. How do you define it on an Instance in the properties window.

The default state of the Instance property type is null, which conversely, undefines an attribute. For ObjectValue its not a problem because Value is a fixed property which handles null as expected.

2 Likes
#12

Easiest solution would be to just make it scriptable only, like Enum attributes, or make it so you have to select an object on attribute creation.

1 Like
#13

The staff member said there’re different solutions they’re considering. Since he didn’t specify what the different considerations actually are, we’re left to guess. Nevertheless, clearly there are multiple solutions, the engineers just need to agree on which one to employ.

1 Like
#14

This is the main reason why I can’t use packages.

2 Likes
#15

Attributes were added 2-3 years ago and they’re still missing this feature. What a shame

4 Likes
#16

Bumping cause I need this so bad!

1 Like
#17

just ran into this issue, and was appalled to see that it does not exist, would really be useful.

3 Likes
#18

this is extremely useful, pls roblox add!!!

#19

Was looking into something similar, would be very grateful for this to exist.

1 Like
#20

bump! this would definitely be good

1 Like
#21

bump still needing this - :slight_smile:

1 Like
#22

This NEEDS to be added.

ObjectValues are a necessity in some cases to Packages, for example, which will cease auto-updates if users that wish to set up settings for Packages modify anything of that package excluding the attributes linked directly to the Package’s base Instance. A solution to this would be creating a string to directly loop through from a directory, splitting descendant names and running FindFirstChild() through each of them, let’s say “ReplicatedStorage.Modules.Shared.Config”, you’d have to remove all the dot operators via gsub I believe (haven’t run over the exact method recently) and iterate through, which is less efficient than directly using an ObjectValue…

1 Like