Badlands will take a configuration file badlands.src from the game directory. You can use badlands -dc on an empty directory to print a list of configuration options with defaults.
DefaultAction (list of drain, passivize; default: drain)
Defines the default action what a badland will do when entered.
Badland (list of X, Y, radius, and optional actions)
This option can appear any number of times. Each assignment defines a circular badland. As an example,
Badland = 1000, 1500, 500
defines a 500 ly badland at 1000,1500, that does whatever is configured in DefaultAction.
Badland = 1000, 1500, 500, drain
defines that badland to drain fuel, independant of DefaultAction.
FirstUfo (integer; default: 800)
Badlands will be reported as Ufos. This parameter specifies the first ID to be used. The maximum number of Ufos is 1000. Badlands beyond ID 1000 will not be reported.
ShipVisibilityRange, PlanetVisibiltyRange (integer; default: 5000)
Defines the visibility range from ships and planets, respectively.
Badlands is intended to be run with a fixed configuration. The configuration file can be shared with players.
Variation 1: By default, badlands are visible from the entire map. Using lower values for the visibility range parameters, you can require players to explore badlands. In this case, do not share the configuration file.
Variation 2: If you want to move badlands, you can update the configuration file mid-game. In this case, you need to make sure to never reduce the number of badlands; reducing the number would leave orphan Ufos in the UFO.HST file which player still see but are not maintained by Badlands anymore. If you wish to delete a badland, you can set its radius to 0, which will deactivate it.
