rename flags to global_flags (differentiate from player_flags)

1 files changed, 5 insertions, 5 deletions

diff --git a/building_guide/rooms.md b/building_guide/rooms.md
index 35fd85a..f77aa42 100644
--- a/building_guide/rooms.md
+++ b/building_guide/rooms.md
@@ -46,7 +46,7 @@ exits:
   southeast: 4
 ```
 
-Conditional exit — blocked until a world flag is set:
+Conditional exit — blocked until a global flag is set:
 ```yaml
 exits:
   north:
@@ -66,7 +66,7 @@ exits:
     blocked_message: "The vault door is locked. You need a key."
 ```
 
-Conditional exit with compound condition — requires both a world flag AND a player flag:
+Conditional exit with compound condition — requires both a global flag AND a player flag:
 ```yaml
 exits:
   north:
@@ -78,7 +78,7 @@ exits:
     blocked_message: "The bridge is out, and the toll collector blocks the path."
 ```
 
-Exit that sets flags when used — `set_flags` / `set_player_flags` are applied
+Exit that sets flags when used — `set_global_flags` / `set_player_flags` are applied
 only when the player actually moves through the exit (not when it's blocked):
 ```yaml
 exits:
@@ -215,7 +215,7 @@ on_enter:
 ```
 
 **Timed sequences.** A step may also carry a `delay` (ticks to wait before it
-fires) and/or set flags (`set_flags` / `set_player_flags`). If any surviving step
+fires) and/or set flags (`set_global_flags` / `set_player_flags`). If any surviving step
 has a delay or sets a flag, the whole sequence runs as a scheduled enter sequence;
 plain message-only scripts still print instantly.
 
@@ -300,7 +300,7 @@ mobs:
 
 ### Room triggers — scripted events when flags change
 
-A room can carry a `triggers:` block. Each trigger watches a player or world flag
+A room can carry a `triggers:` block. Each trigger watches a player or global flag
 and fires a sequence of timed steps when that flag's value changes. See `triggers.md`
 for the full reference.