From 20a645bdf42e494262e897210100d8a1f8f9dd18 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Tue, 27 Jun 2017 00:57:36 -0400 Subject: [PATCH] Move the travel rule documentation to newdungeon.py. --- newdungeon.py | 69 ++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 65 insertions(+), 4 deletions(-) diff --git a/newdungeon.py b/newdungeon.py index b27e5c7..a4b230e 100755 --- a/newdungeon.py +++ b/newdungeon.py @@ -3,6 +3,46 @@ # This is the new open-adventure dungeon generator. It'll eventually # replace the existing dungeon.c It currently outputs a .h and .c pair # for C code. +# +# The nontrivial part of this is the compilation of the YAML for +# movement rules to the travel array that's actually used by +# playermove(). This program first compiles the YAML to a form +# identical to the data in section 3 of the old adventure.text file, +# then a second stage packs that data into the travel array. +# +# Here are the rules of the intermediate form: +# +# Each row of data contains a location number (X), a second +# location number (Y), and a list of motion numbers (see section 4). +# each motion represents a verb which will go to Y if currently at X. +# Y, in turn, is interpreted as follows. Let M=Y/1000, N=Y mod 1000. +# If N<=300 it is the location to go to. +# If 300500 message N-500 from section 6 is printed, +# and he stays wherever he is. +# Meanwhile, M specifies the conditions on the motion. +# If M=0 it's unconditional. +# If 0