AssemblyLinearVelocity multiple bugs (or intentional?)

[EffBeeCee]

First thing:

AssemblyLinearVelocity does not save in studio.

When I set the AssemblyLinearVelocity of a regular BasePart in studio, save my game, then reopen studio, the AssemblyLinearVelocity is reset back to 0, 0, 0. I’m not sure if this is a bug or is intentional.

Next thing (pretty sure its a bug):

AssemblyLinearVelocity cannot be set by setting the X, Y, or Z property. For example,

<Part>.AssemblyLinearVelocity.X = 3 -- Output: "X cannot be assigned to"
<Part>.AssemblyLinearVelocity.Y = 3 -- Output: "Y cannot be assigned to"
<Part>.AssemblyLinearVelocity.Z = 3 -- Output: "Z cannot be assigned to"

[wastbo (DanCodes)]

Any vector type is immutable by default. It’s the same across all engines. So not a bug.

You should really only be setting velocity in a script anyways. Letting it be set in studio could just lead to all sorts of issues.

[EffBeeCee]

@wastbo

Any vector type is immutable by default. It’s the same across all engines. So not a bug.

Ah, I see, that makes sense.

@wastbo

You should really only be setting velocity in a script anyways. Letting it be set in studio could just lead to all sorts of issues.

Yeah, makes sense, weird that they would even have the option in studio anyways then. (It does work in studio - at least in testing - and I don’t think it would cause that many issues if the part is anchored)