Area File Layout

From The Final Challenge Wiki
Revision as of 13:53, 12 February 2011 by Thor (talk | contribs) (Created page with "An area file is laid out using a series of BLOCKS. Each block starts with a control structure that tells the MUD what kind of data is contained in the block. Following the contro...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

An area file is laid out using a series of BLOCKS. Each block starts with a control structure that tells the MUD what kind of data is contained in the block. Following the control structure are the records holding the data. After the final record in a block, a control marker occurs indicating the block is finished.


All blocks are optional, and you may have only ONE of each type. However, some blocks force the use of other blocks. For example, if you have a block of mobs or objects, you are forced to have a block of the resets to load them into the area. Or if you have rooms in the file, you MUST have an area header block.


There are 10 kinds of blocks:

  • The area header
  • The helps block
  • The mobiles block
  • The objects block
  • The rooms block
  • The resets block
  • The shops block
  • The specials block
  • The triggers block
  • The rspecs block


For ease of reading, they MUST be used in the order listed above.

Following all the blocks, the last line of the area file must contain the control marker signifying the "end of file". This is the string "#$" on a line all by itself. If this is omitted, the area will NOT load.


An area file is laid out like this, then:

BLOCK

BLOCK

BLOCK

BLOCK

.

.

.

#$