Extremely happy these have finally been released! Can’t wait to refactor my game to use these instead of messy value objects!
Yes, this is such an amazing update!
So if your making a gun for example, before you had to do values etc now all you got to do is use these and instead of calling for the value you call the attributes? Nothing else is really changed? I’m still learning about scripting, changes like these kinda throw a bump in the path sometimes so I want to clarify that this isn’t that different. I had watched AlvinBlox’s video on them, they seem to be great.
Also
what about exploiters being able to change values etc. Is there any way to stop that or is the “is changeable” property a way to not allow it to be changed… Then again that could be disabled probably.
Or does this mean something else.
This is one amazing update and I have full support on it BUT there is one issue I am seeing, there is not a “Object” type with what I have seen from this new feature.
This would fix a few issues with having several ObjectValues being used and adding new a new “Object” Type to “Attributes” would be great!
Yeah, building off of what @WallsAreForClimbing said, you should see performance improvements and better gameplay if you are using “Value” alot and and better game function. Also a quick question for you, how’s the carriages going for “The Wild West”?
Attributes aren’t replicated from the client to the server, only the server to the client. However, that doesn’t mean a client can’t change an attribute locally. This is the same for existing properties and value objects.
Could we get subsection for attributes too it could be really handy dividing different values but this is super useful otherwise!
Awesome! Will objects ever be available in attributes though?
Do you plan to let us separate attributes using a scope or namespace? I’d like to put attributes in different scopes for instances that have more than one collection tag.
Can we get Object type attributes? An alternative for Object Values?
I have discovered a bug with this new feature. If you use GetAttributes() it gives you an array of all the attributes, however, if you use #GetAttributes() it always returns 0.
I myself don’t access to #bug-reports:engine-bugs, but if someone who does is reading this, please report this. Thanks!
That’s expected behavior because GetAttributes
returns a dictionary and not an array. The length operator doesn’t work on tables that do not have a numerical index.
Been getting “Attributes are not currently enabled” in my error log even though this feature is live. Happens very rarely though, maybe a player with an old Roblox app version?
Is anyone else having a problem where they get the script analysis warning:
Key 'Value' not found in class 'Instance'
My object is a StringValue. It seems like it’s trying to find an attribute and then when it doesn’t find it it tosses that warning instead of checking to see if it’s a property.
#AttributeOrNothing lol
Edit: Same thing happens with events of certain instances. (BindableFunction)
Hey,
Attributes are for sure one of the best thing - no more ObjectValues and making my workflow overall better! But what I really want to see are array attributes. I know that there has been suggestions about it many times but it would be really good to actually get it also with IncrementAttribute and some kind of event to change Attribute relies on its type (without overriding Attribute type) because right now SetAttribute overrides Attribute type.
That’s all for now thank you for reading.
Sincerely,
-caviarbro!
(PS. I know that @RuizuKun_Dev made module for it and I think its amazing but I would really want to see some of these features built-in)
whats the point of num values?
Can there support for attributes with an instance value? I want to set a target part that an NPC should focus on, because studio doesn’t support instance references it makes doing this more complicated
What’s up with clients that don’t have attributes enabled being allowed to play?
Getting a few errors stating “Attributes are not currently enabled”, which I assume are from users playing on older versions of Roblox. Don’t think this is something I should be expected to work around to keep everything functional
Suggestion: Add object values as custom attributes, shame that is not a custom attribute yet.
i dont have the ability to post in feature requests so ill put this here:
a script im making works with a lot of number value instances, which are tweened regularly ingame
id like to use attributes for this instead, as they are more performant and use less memory, but unfortunately tweenservice isnt compatible with attributes at the moment…
i suggest tweenservice be updated to support attributes instead of just properties