Reproduction Steps
Currently, as of v0.554.0.5540504
/ 12/6/22
, enabling team create resets some properties in various instances in the datamodel.
To reproduce:
- Open an empty local baseplate.
- Set
Players.UseStrafingAnimations
totrue
- Publish the baseplate to a place that has team create disabled.
- Observe that
Players.UseStrafingAnimations
is stilltrue
. - Turn on team create through the team create widget. Observe that
Players.UseStrafingAnimations
isfalse
now when it shouldn’t be. - Turn off team create through the team create widget. Observe that
Players.UseStrafingAnimations
istrue
again, like it should be.
Expected Behavior
It is expected that turning on team create would not manipulate the datamodel in any way, especially not randomly changing property values on objects present in it.
Actual Behavior
Turning on team create manipulates the datamodel and arbitrarily changes properties on objects present in it, namely Players.UseStrafingAnimations
.
Workaround
Not using team create
Issue Area: Studio
Issue Type: Other
Impact: High
Frequency: Constantly
Date First Experienced: 2022-12-06 00:12:00 (-05:00)