Can't change certain workspace properties

Help and Feedback Scripting Support
1

So recently I was making some tweaks to my game and noticed that I was using signal behavior deferred for some odd reason.
So I tried changing it back, only to realize it would always default to using deferred once again.
Then I noticed this also happened with StreamingEnabled and PhysicsSteppingMethod
I’m not familiar with the way signals and physics work with Roblox so I gotta ask…
Did Roblox push out a change that forces this?

Things I tried

  • Disabling Team Create
  • Opening a local file of the same game
  • Tweaking other properties in hopes it would allow me to change these 3.
  • Disabling all plugins

Older versions of the same game don’t seem to have this issue.

2

Weird glitch with your studio, it works no problem for me. Make sure you save, and then re-install Roblox Studio.

3

I’ve already reinstalled like 3 times and the result is the same.
Besides this only happens with one specific place file.

4

So if you want to a different place it would change no problem?

5

Any copies I make of this placefile will have this issue but other placefiles wont.

6

No clue, possible corruption, or conflicts. The property is not scriptable so it’s not a plugin or script. If you want, you could invite me to teamcreate and I can try and change it.

7

It might’ve been placefile corruption if I’m being totally honest, but I fixed the problem by just copying over my work to an older placefile and saving it to the current one from there.
(Also I don’t exactly entertain the idea of giving a stranger access to my game sorry.)

8

Perfectly understandable, glad you figured it out.

9

I did find some new restrictions.. Steaming
And I found this: The StreamingEnabled property is editable only in Studio. However, once a place is created, the setting may become locked based on the template or engine version used.

This means that for newer projects or templates, the StreamingEnabled setting might be enforced and cannot be altered through the Studio interface. Older versions of the same game may not exhibit this issue because they were created before this restriction was implemented.

10

Interesting. Doesn’t exactly explain why other seemingly unrelated properties exhibit this behavior but interesting nonetheless, great find!

11

It did say this.. Exactly what you’re showing here.