Content and History

#New material is visible too early

Choose GM only while creating or preparing material. A new page or record can inherit a type's initial permission, so verify the access state rather than assuming every new item is private. Use Player View before a session when the distinction matters.

#Showing a page did not open it for everyone

Check the presentation target and that the selected page still exists. Presenting raises the needed access and opens the page for its recipients. Ending the presentation removes it from their screens but does not silently revoke the access that was deliberately granted.

#A Roll Table result is refused

The table must be readable, non-empty, and valid when the server rolls it. /table accepts an exact name or unique prefix; ambiguous prefixes are refused. A private preview expires and posting it rechecks access.

#A write was rejected

The document may have changed since the client based its edit, permission may have changed, or the new value may fail its schema. Keep the rejected message. Reloading can refresh the revision but does not grant permission or make invalid data valid.

#Undo is blocked or missing

Open History and read the row's state. Replay requires the same target, permission, and compatible current value. A conflicting later change makes the step blocked or invalidated rather than overwriting it. Some operations, including vector-drawing deletion and explored-fog reset, are permanent or outside personal History and say so before they run.