== Three key resources steps ==

Anything you put in <code>You will need to define.dat</code>, you can refer to in your other the name that the IVAN script files. This is a general rule and is applicable will use to any of the data filesrecognise your dungeon. For example, if Therefore you want will need to create another config of a guard, then you just put include a new <code>#define</code> with the other dungeon names in <code>define.dat</code>, and you can now refer to it in <code>char.dat</code> and your dungeon data file.

Anything you put in <code>define.dat</code>, you can refer to in your other script files. This is a general rule and is applicable to any of the data files. For example, if you want to create another config of a guard, then you just put a new <code>#define</code> in <code>define.dat</code>, and you can now refer to it in <code>char.dat</code> and your dungeon data file. So it follows that you can <code>#define</code> your own dungeon name, which will be essential when we come to link the dungeon data file to the terrain data file.

Stick to upper case lettering when adding a new <code>#define</code>, and be sure to put an underscore when separating words. Dos and don'ts: be Be sure items that are enumerated follow a nice numerical sequence e.g. <code>1, 2, 3, 4, 5;</code> or <code>2, 4, 8, 16, 32;</code>, rather than <code>1, 2, 5, 7, 8;</code>. If Note that if we wish to refer to a particular dungeon in the code itself, say in <code>game.cpp</code>, then the code will need to know about it, and so a <code>#define</code> will need to appear in <code>ivandef.h</code> before compiling the game.

Pictures Here are some pictures showing famous owterrains: {| class="wikitable"! New Attnam! Attnam! Gloomy Caves|-| [[File:ownewattnam.png|160px]]| [[File:owattnam.png|160px]]| [[File:owgloomycaves.png|160px]]|}