The Cathedral of Attnam

Changes

Jump to navigation Jump to search
2,841 bytes added ,  11:06, 26 April 2016
Created page with " == Introduction == === Welcome === Welcome to the world of IVAN dungeon building. It is a part of game development that is as interesting and intricate as the game itself...."

== Introduction ==

=== Welcome ===

Welcome to the world of IVAN dungeon building. It is a part of game development that is as interesting and intricate as the game itself. Designing and building a dungeon for IVAN presents many challenges and it can feel like a steep learning curve, however, the satisfaction of creating a world in which many enthusiastic IVANers can play in and feel part of is very rewarding.
This guide is aimed at those with little or no coding skills, but who are comfortably computer literate. Those who are already familiar with C++ will be advantaged by their programming experience, and will hopefully find the collection of examples on dungeon building suitably novel and interesting.

=== What we will look at ===

== Tools ==

=== A suitable text editor and font ===

When editing the dungeon file, it pays to have a good text editor. A nice program in Windows might be, for example, Programmer’s Notepad 2, but any program with suitable syntax highlighting will do. The script file text is based on C/C++ syntax, so you can set the syntax highlighting to this language. It is also highly prudent to select a mono-space typeface. A mono-space typeface means each character has the same horizontal length in the editor. Because we are also going to “draw” with ASCII characters in the script files, it would be good if the characters can properly align in a grid-like fashion, making it easy to identify the geometrical patterns. This is indispensable when it comes to laying out large rooms and even particular dungeons, helping to avoid confusion along the way. Suitable typefaces to consider for this purpose might include Courier New or Lucida Console fonts.
Always aim to implement your script using a minimal number of lines. If you write something that is really lengthy, then don’t panic, there’s always time to prune the code down later. Be warned that you will be tempted to leave things as they are once things are working smoothly, so try to write the script efficiently for posterity.

=== Backing up your work ===
This is really the most important step, and should be the first thing you organize. Make a copy of your dungeon file and store the copy somewhere else, that way, you can always revert to the original if you make changes all over the place. No matter if you lose original files, you can usually pick up an old file from a repository somewhere and revert back to it.

A more guru way to do this, would be to set up your own IVAN development branch, by cloning the <code>attnam/ivan</code> git repository and making changes in your own branch. You can make pull requests to merge you work into the main line of IVAN development! By using a version control system like GIT, you enable for yourself a great tool for maintaining your dungeon script file.

== A first dungeon ==
158

edits

Navigation menu