Exporting and running a module

In order export your edits and changes for a level to the game there are several steps involved. When working in a collaborative environment you should generally not check in resources until you have exported and tested them in game.

Setting the starting area

The starting area and starting waypoint within that area are a property of the module. To set this property you'll need to open the object inspector for the module itself.

To get there, select the "Manage Modules" command from the file menu:

This will bring up a list of all the available modules:

Select the one you want to set the start area for and click the "Properties" button. This will open the object inspector and allow you to set the "Starting Area" and "Starting Waypoint" properties.

Overriding the starting area in a test export

If you're exporting an area just to give it a test run it can be convenient to be able to override the module's start area on an export-by-export basis.

Save the area you are working on and choose tools from the menu:

Navigate down to the “Export options” choice:

You will see a window that will define the starting area and the starting waypoints for the export. Choose the corresponding starting area and waypoint by clicking on the fields and making your choice.

Choose a starting area.

Choose a waypoint.

Exporting the module

When this is completed, close the Export options window and select the Export with dependent resources or export without dependent resources option.

Either option will export the level to the game. Once the export has completed you should be able to start a "New Game" (if editing the main campaign) or select your module under "Other Campaigns" (for stand-alone content). You should start in the level that you have exported at the waypoint that you have set as your starting point.

Export Options

Export with dependent resources: This will export the currently selected resource, as well as any other resources that it depends upon. For instance, if you have created an area with a creature in it, this option will export the area, the creature, the creature's inventory, the scripts, etc. It would then grab any dependencies for the creature, inventory, or scripts and continue until it exhausted all of their dependencies. Doing this is a good way to make sure you get all of the needed pieces for any particular resource, but it can also quickly multiply to the point where it is picking up half of the module.

Export without dependent resource: This will only export the currently selected resource. This is a quick and efficient way to update your module when you have modified parts of a resource that only affect that resource.

Export all resources of type: This will export every resource of the same type as that which is currently selected in the palette. For instance, if you select a creature and choose this method, it will export all creatures in the module.

Full export: This option exports every resource associated with the module. It is the most comprehensive, and takes the longest to run.

Locations where resources are exported to/read from

See Source directory priorities for a list of the directories that resources can be stored for the game and toolset to use.