Changed pausing-and-disabling-systems.md.

Author: svermeulen

docs/advanced/pausing-and-disabling-systems.md

@@ -24,21 +24,19 @@ public enum EnableChannel
 }
 ```
 
-Game-host / editor code calls these on a `WorldAccessor` (typically a long-lived `AccessorRole.Unrestricted` accessor created via `world.CreateAccessor(AccessorRole.Unrestricted)`):
+Game-host / editor code calls these on a `WorldAccessor`:
 
 ```csharp
 accessor.SetSystemEnabled(systemIndex, EnableChannel.User, false);  // disable
 accessor.SetSystemEnabled(systemIndex, EnableChannel.User, true);   // re-enable
 bool enabled = accessor.IsSystemEnabled(systemIndex, EnableChannel.User);
 ```
 
-`SetSystemEnabled` doesn't gate on `AccessorRole`, so any accessor can call it — but in practice you'll want a non-system `Unrestricted` accessor since channel toggles are host-side concerns.
-
-Channel state defaults to "all enabled" at world init and is **not part of snapshot/restore or recording state**. Anything that sets a channel disable is responsible for re-applying it across world resets — `BundlePlayer` does this automatically when playback (re)starts.
+Channel state defaults to "all enabled" at world init and is **not part of snapshot/restore or recording state**. This is likely to cause desyncs.
 
 ## SetSystemPaused — deterministic pause
 
-`SetSystemPaused` is a per-system flag that **is** part of serialized world state, so it survives snapshot/restore and round-trips through recording playback. Use it for any pause that affects the simulation and must replay identically.
+`SetSystemPaused` is a per-system flag that **is** part of serialized world state, so it survives snapshot/restore and round-trips through recording playback. Use it for any pause that affects the simulation and must replay identically (eg. pausing for UI menu popup).
 
 Called from inside a system or from initialization code, via `WorldAccessor`:
 
@@ -60,7 +58,7 @@ bool willRun = world.IsSystemEffectivelyEnabled(systemIndex);
 
 ## Building your own grouping
 
-Trecs deliberately doesn't have a built-in `[SystemGroup]` concept. Instead, the framework exposes the per-system metadata you need to build whatever grouping makes sense for your game (also available on both `World` and `WorldAccessor`):
+Trecs deliberately doesn't have a built-in `[SystemGroup]` concept to do a bulk pause/unpause. Instead, the framework exposes the per-system metadata you need to build whatever grouping makes sense for your game (also available on both `World` and `WorldAccessor`):
 
 ```csharp
 int count = world.SystemCount;
@@ -70,41 +68,6 @@ SystemMetadata meta = world.GetSystemMetadata(systemIndex);
 //   meta.DebugName      — human-readable name
 ```
 
-A typical pattern: walk all systems once at init time, bucket their indices by some criterion the game cares about (a custom attribute, a type lookup, a config asset, anything), then drive `SetSystemPaused` or `SetSystemEnabled` calls against those buckets.
-
-```csharp
-// One-time setup: collect indices of systems tagged "gameplay".
-var gameplayIndices = new List<int>();
-for (int i = 0; i < world.SystemCount; i++)
-{
-    var meta = world.GetSystemMetadata(i);
-    if (meta.System is IGameplaySystem)
-    {
-        gameplayIndices.Add(i);
-    }
-}
-
-// Later, when the pause overlay opens (called from a fixed-update system):
-foreach (var i in gameplayIndices)
-{
-    accessor.SetSystemPaused(i, true);
-}
-```
-
-The pause overlay's UI systems aren't in the gameplay bucket, so they keep running while the gameplay systems are paused.
-
-## When to use which
-
-- "I want to disable some systems while a debug menu is open" → `accessor.SetSystemEnabled(..., EnableChannel.User, false)`.
-- "I want to silence input systems while playing back a recording" → already done by `BundlePlayer` via `EnableChannel.Playback`. Don't reimplement.
-- "I want the editor to let me toggle systems for inspection" → already wired through the [Trecs Hierarchy window](../editor-windows/hierarchy.md) via `EnableChannel.Editor`.
-- "I want gameplay to pause when a UI overlay is up, and have that pause survive a save / replay deterministically" → `accessor.SetSystemPaused` from a Fixed-update system.
-- "I want a kill switch that doesn't need to replay deterministically" → `EnableChannel.User`. It won't show up in checksums or recordings.
-
-## Threading
-
-Both APIs are **main-thread only**. Neither is exposed on `NativeWorldAccessor`, so jobs cannot toggle systems. Reads and writes happen at main-thread sync points (between ticks, or inside a system's `Execute()`).
-
 ## Related
 
 - [Accessor Roles](accessor-roles.md) — why `SetSystemPaused` requires a `Fixed`-role accessor and `SetSystemEnabled` doesn't.