Tutorials/Programs and editors/Tectonicus/TectonicusConfigFormat

When running from the command line the preferred way to configure Tectonicus is to use a config file. For the most up-to-date information, see the example config file here: http://code.google.com/p/tectonicus/source/browse/trunk/tectonicus/Docs/fullConfig.xml

Tectonicus config files are stored as XML. If you are unfamiliar with XML, then see this basic tutorial: http://www.w3schools.com/xml/xml_syntax.asp

When starting Tectonicus, to get it to parse the config file, pass a "config=" option. For example:

java -jar Tectonicus.jar config=layerConfig.xml

If you're new then it's easiest to just take the example config file and modify the file paths so they point to your world folder and output folder.

Remember that config options are case sensitive!

= Overview =

The basic structure of the config file looks like:

These can be in any order. Only 'layer' and 'map' may be present more than once, these nodes will be covered later.

= Example configuration file =

Here’s a minimal config file for creating a single map:

 

 

= Configuration file defined =

Config node
Here's an example config node: 

This controls the basic setup you need to change for your computer.

Rasteriser node
Here's an example rasteriser node:  These values are used to configure your graphics card when drawing the map.

Layer
This controls how the map layers appear in the final rendering. Here is an example layer node:

			     

Markers
A sub-node of the layers node, these options control which markers appear on the final rendered map. The data is formated as

   <spawn show="true" intiallyVisible="true" /> <beds initiallyVisible="true" />

Subset
Another sub-node of the layers node, this will limit the rendering to a circular area of the world map of specified location and size, rather than rendering the entire map. This is useful when testing Tectonicus options to drastically reduce rendering time. It is formatted:

<CircularSubset radius="200" />

Tweeks Node
Here's an example tweeks node: <tweeks extractLwjglNatives = "true" forceLoadAwt = "false" force32BitNatives = "false" force64BitNatives = "false" >

These are options you shouldn't need to change, but can workaround quirks on some machines.

Debug node
Here's an example debug node:

<debug maxTiles = "-1" >

These are debugging options not intended for general use