Configuration

Configuration files are located in config/superpiston/configs. The file config/superpiston/map.conf associates the configurations with the worlds. This way, different worlds can share the same configuration. You can specify a default configuration per dimension and globally.

By default, SuperPiston automatically generates a single configuration for all dimensions. Here’s what the configuration looks like:

Config {
    BlockReactions {
        .....
    }
    MaxBlocks=12
    StickyBlocks {
        .....
    }
}
Version=1

This example shows you the general structure of a configuration file. (..... represents a more or less long list of items).

Structure

As you can see a configuration file is currently divided in two parts.

Version

This field is used to hold a number that will indicate to SuperPiston whether the configuration is outdated or not. You should never modify this number. If the configuration is outdated, SuperPiston will make a backup of the file and try to update the structure to a newer version. If it’s not possible a new one will be generated.

Config

This part always has the same structure. Here are the different fields:

• BlockReactions is a mapping of block ids to reactions. It allows to override the vanilla behavior of some blocks, all possible reactions are NORMAL (like most blocks by default), DESTROY (like grass by default), BLOCK (like obsidian by default) and PUSH_ONLY (like glazed terracotta by default).
• StickyBlocks is a mapping of block ids to booleans. It allows to override the vanilla behavior of some blocks, set to false to disable the sticky behavior or to true to enable it.
• MaxBlocks determines the maximum number of blocks that can be pushed at once by a piston (12 by default).

Example

Here is an example of a configuration that make obsidian moveable, lapis block sticky and slime block no longer sticky:

Config {
    BlockReactions {
        obsidian=NORMAL
    }
    MaxBlocks=12
    StickyBlocks {
        "lapis_block"=true
        "slime_block"=false
    }
}
Version=1

Please avoid making blocks with tile entities moveable (chests, furnaces, etc..), it hasn’t been tested correctly and might be bugged.