aboutsummaryrefslogtreecommitdiff
path: root/building_guide/courses.md
diff options
context:
space:
mode:
Diffstat (limited to 'building_guide/courses.md')
-rw-r--r--building_guide/courses.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/building_guide/courses.md b/building_guide/courses.md
index e5deb32..5e92318 100644
--- a/building_guide/courses.md
+++ b/building_guide/courses.md
@@ -6,7 +6,7 @@ Agility courses are defined in `data/courses/<id>.yaml`. Each course defines a s
> Editing courses is done from the **Map screen** in the admin web GUI: select an obstacle room and use its **Course** side-panel tab to create a course, add the room as a step, edit all of its parameters, or remove it. The legacy standalone "Courses" editor tab has been removed.
>
-> When a room is added as a course step, the admin GUI auto-creates **hidden one-way exits** between consecutive obstacle rooms so the in-game map can lay them out correctly. The direction of these hidden exits is chosen by the builder. Hidden exits are invisible in `look` output and cannot be traversed — they exist solely for map rendering. On the map, course links appear as blue dashed one-way arrows (colored via the `map_course` theme token).
+> When a room is added as a course step, the admin GUI auto-creates **always-blocked one-way exits** between consecutive obstacle rooms so the in-game map can lay them out correctly. The direction of these exits is chosen by the builder. Always-blocked exits are impassable to players but visible on the map — they exist solely for map rendering. On the map, course links appear as blue dashed one-way arrows (colored via the `map_course` theme token).
### Course YAML