Bukkit

Version 0.9.0 introduces staggered loading of all dungeons. The default value is to load 3000 blocks at a time separated by intervals of 3 seconds.

However, depending on the capabilities of the server this value may need to be adjusted up or down to produce the desired effect. The value for this can be changed by editing the "dungeonbuilder.cfg" file in the plugins folder and adding/editing the line:

loadChunkSize=3000

where 3000 would be replaced with whatever number you think is suitable.

Some servers have other plugins that control the location the player will respawn at when they die. By default the behavior of DungeonBuilder is to respawn the player at the start of the dungeon or the previous savepoint when they die. Often these two plugins will conflict over where the player respawns.

To help resolve this conflict server administrators can configure the respawn priority for the DungeonBuilder plugin by adding the following line to the plugins/dungeonbuilder.cfg file:

setRespawnPriority=*

where * is one of the following values:

HIGHEST
HIGH
NORMAL
LOW
LOWEST
MONITOR

For example, setting this to "HIGHEST" would ensure the player always respawns at the dungeon start or the last savepoint while setting it to "LOWEST" would ensure the player would respawn at the location set by other plugins.

Setting this to "MONITOR" has the effect of disabling the respawn altogether, meaning the player will be booted from the dungeon and no longer flagged as running it.

Version 0.7.4 introduces support for superperms. However this functionality is disabled by default in order to maintain the pre-established behavior of the plugin which is:

1. If the permissions mod is installed then use that to check permissions. 2. Otherwise check to see if the player is an operator.

To enable superperms support you will need to edit the configuration file (plugins/dungeonbuilder.cfg) and add the line:

enableSuperperms=true

to it and restart the server.

Starting with version 0.6.6 the plugin will not allow players to wander too close to a dungeon unless they are the owner. This functionality is enabled by default but can be disabled by adding the line:

disableProximityChecks=true

to the dungeonbuilder.cfg file.

Dungeon files are stored by default in a folder named "dungeons" in the "plugins" directory. Should you want to store dungeon files in a different location you can perform the following steps to change the target directory.

In the server plugins directory create a file named "dungeonbuilder.cfg". This file will also be generated on first startup with the default dungeon root. Add a line to the file created in step 1 that reads:

rootFolder=foldername

Where "foldername" is the name of the folder that you want to store dungeon files under. This value is a path relative to the directory the server is running from.

By default monsters will not naturally spawn inside dungeons. To re-enable this functionality you can add the following line to the file "dungeonbuilder.cfg" that reads:

enableMonsters=true