From 3f7a25cdf237b9f18f85ae9d211e7af60fac770e Mon Sep 17 00:00:00 2001
From: "Eric S. Raymond" <esr@thyrsus.com>
Date: Thu, 22 Jun 2017 11:24:00 -0400
Subject: [PATCH] locbit.py: Can't set a FORCED attribute in the YAML...

...it has to be computed from the travel arrays.
---
 locbit.py | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/locbit.py b/locbit.py
index b50c7ef..5b37461 100755
--- a/locbit.py
+++ b/locbit.py
@@ -8,8 +8,6 @@
 #
 # When in doubt, make the code dumber and the data smarter.
 #
-# It bothers me that I don't know why FORCED is checking the fluid bit.
-#
 import sys, yaml
 
 # This is the original location-attribute data from section 9 of adventure.text
@@ -52,7 +50,7 @@ attrnames = (
     "FLUID",	# 2
     "NOARRR",	# 3
     "NOBACK",	# 4
-    "FORCED",	# 5	# New
+    "",		# 5
     "FOREST",	# 6	# New
     "ABOVE",	# 7	# New
     "DEEP",	# 8	# New
@@ -96,10 +94,7 @@ def genline(loc):
             if props[0] not in attrs:
                 attrs.append(props[0])
     # Adod new attributes.  These are computed the same way as the
-    # INDEEP(), OUTSID(), and FORCED macros in advent.h.
-    # FORCED is on only if COND == 2
-    if attrs == [2]:
-        attrs.append(5)	# FORCED
+    # INDEEP(), OUTSID(), and FOREST() macros in advent.h.
     if "FOREST" in name:
         attrs.append(6)	# FOREST
     # 167 is the sapphire's start location
-- 
2.31.1