summaryrefslogtreecommitdiffstats
path: root/crawl-ref/docs/level_design.txt
diff options
context:
space:
mode:
authordshaligram <dshaligram@c06c8d41-db1a-0410-9941-cceddc491573>2008-11-23 18:58:31 +0000
committerdshaligram <dshaligram@c06c8d41-db1a-0410-9941-cceddc491573>2008-11-23 18:58:31 +0000
commitbe8748fa444e6813e09ef959f5ee4b88b67dd68e (patch)
tree0ed8640d1756cbfbd02091d0c74d7b47a7b0eec8 /crawl-ref/docs/level_design.txt
parent1392155c0cb7acb6224a39611102e46460a06e5b (diff)
downloadcrawl-ref-be8748fa444e6813e09ef959f5ee4b88b67dd68e.tar.gz
crawl-ref-be8748fa444e6813e09ef959f5ee4b88b67dd68e.zip
More steps toward ziggurats.
git-svn-id: https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/trunk@7553 c06c8d41-db1a-0410-9941-cceddc491573
Diffstat (limited to 'crawl-ref/docs/level_design.txt')
-rw-r--r--crawl-ref/docs/level_design.txt14
1 files changed, 12 insertions, 2 deletions
diff --git a/crawl-ref/docs/level_design.txt b/crawl-ref/docs/level_design.txt
index 0615d49ec6..744a71445d 100644
--- a/crawl-ref/docs/level_design.txt
+++ b/crawl-ref/docs/level_design.txt
@@ -366,7 +366,7 @@ CHANCE: <priority>:<roll> or <roll>
That is, if you have a set of maps that use CHANCE and are
tagged chance_xxx, then one map of that set will be used
when the chance is met.
-
+
WEIGHT: (number with 10 being default)
For entry vaults and any other vaults randomly picked from among
@@ -611,6 +611,16 @@ MONS: (list of monsters)
The available modifiers are "zombie", "skeleton",
"simulacrum" and "spectre".
+ If a monster is a member of a band, you can request that it
+ be eligible for band members by adding the keyword "band" to
+ the name. For instance:
+ MONS: orc warlord band
+
+ Specifying "band" doesn't force bands to be placed - it
+ requests that the game use the normal chances of creating a
+ band. If you use "band", leave some empty space around the
+ monster for its band members to be placed.
+
A monster can be given specific items by following the monster
name with a semi-colon and then with an item list as described
in ITEM:, but with slashes replaced with pipes and commas replaced
@@ -1286,7 +1296,7 @@ description ("A portal to places unknown") and a destination
In case you want to make sure that the portal vault entry is only used
once, you add a TAGS: uniq_BAR line. It should be noted that the label
-BAR may *not* end in _entry (otherwise the level builder assumes that
+BAR may *not* end in _entry (otherwise the level builder assumes that
the vault is a branch entry).
This will produce a portal, but attempting to use it will trigger an