From 100152c21df9a5508936e31a3971aea71a280165 Mon Sep 17 00:00:00 2001 From: "Eric S. Raymond" Date: Fri, 7 Jul 2017 15:34:32 -0400 Subject: [PATCH] Comment cleanup. --- make_dungeon.py | 107 ++++++++++++++++++++++-------------------------- 1 file changed, 48 insertions(+), 59 deletions(-) diff --git a/make_dungeon.py b/make_dungeon.py index 3a78d4e..f8b3147 100755 --- a/make_dungeon.py +++ b/make_dungeon.py @@ -6,43 +6,7 @@ # # 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 unpacks 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 0500 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