actually bruh

docs/06_Operations.md

@@ -5,7 +5,7 @@
 1. `/networkcore status` - confirm "Database: ok" and "Network: connected".
 2. Connect a staff alt. Run `/lookup <your-main>`. You should see your own UUID and online status.
 3. Connect a non-staff alt. Have a staff member run `/warn <alt> test`. The alt receives a chat message; nothing crashes.
-4. `/sc test` from staff. Every other online staff member sees it. No non-staff sees it.
+4. `/sc` from a staff alt to toggle staff-chat-mode ON, then type a message in chat. Every other online staff member sees it; no non-staff sees it. Run `/sc` again to turn off.
 5. Look in MySQL:
    ```sql
    SELECT * FROM staff_punishments ORDER BY issued_at DESC LIMIT 5;
@@ -14,9 +14,9 @@
 
 ## A staff member can't run staff commands
 
-1. Check what groups Hytale shows for them. There's no direct command for this in Staff; have them run `/lookup <theirname>` - if it works, they're staff. If it doesn't, the group is wrong.
-2. `PermissionsModule.get().getGroupsForUser(uuid)` is the source. Confirm the group name they're assigned matches one in `permissions.staff_groups` in `config.json` (case-sensitive).
-3. Group changes typically require the player to reconnect.
+1. The plugin checks `PermissionsModule.get().hasPermission(uuid, "networkstaff.<command>")`. The error message includes the exact node that was checked - read it.
+2. Confirm their group has either the specific node or `networkstaff.*`. See [03_Commands.md](03_Commands.md#permissions) for the full list.
+3. Permission changes typically require the player to reconnect.
 
 ## A ban isn't propagating