I think the current confusion comes from the dev mixing three concepts in the instance settings design. Here’s how I see it:
- #1: Control as World Mechanics
- Built into the world via layers, colliders, Udon code, etc. (fine-tuned, runtime-specific control)
- Checkboxes on the website/SDK (simple on/off, easy to set up)
- #2: Control as Instance Moderation
- Toggling features (e.g., drones) off for moderation
- On-the-fly switching added in the last update
- #3: Players’ Wish to Use Features Freely
- Requests to flip features off=>on for fun
- Expectation to always use them (“Why tie us to the world author?”)
This update forced #2 (moderation) into focus, especially for drones. They can annoy players if misused, so instance owners need an off switch, even if creators enabled them. Fair enough.
Before, we had just #1 in the settings: a binary setup (on or off) as world mechanics. Adding #2 should’ve meant three states: “on as mechanics,” “off as mechanics,” “off for moderation.” Instead, the dev stuck with two values (on/off) and didn’t redesign the system. Then the instance creation UI (those checkboxes) blended in #3: “on” now also means “players want it on.” That’s where the lines blurred.
Now, “off for mechanics” and “off for moderation” aren’t distinct. The “instance settings” screen feels like a mashup — we can’t tell what it’s controlling anymore. Creators lose clarity on how their worlds will work, and players argue over freedom vs. rules. That’s the root of this mess.