Configuration

The plugin is configurable via a configuration file. The file is automatically created as config.yml in the RetractableBridge subdirectory in your plugins directory. Just in case you have an older version there, here is the current default, including documentation of the various options:

# Whether or not to move entities on the bridge along:
entityMoving: true

# The speed of the bridge. The number is the number of "ticks" between
# movements of the bridge. A tick is 1/20 second. In other words, the
# default value of 30 means 1.5 seconds between movements.
#
# If you set this too low your server load may increase exponentially,
# especially if you have many bridges on your server!
#
# Also don't forget that this is a server wide setting for all bridges.
# Make sure that your users have a say and know about it if you change
# this setting:
movingDelayBase: 30

# The allowed materials for the bridge. This is a list of block ID's. You
# can find a list of all possible block ID's at
# http://www.minecraftwiki.net/wiki/Data_values
#
# Be very careful when adding block ID's to this list. You don't want any
# flat surface which just happens to be next to a bit of redstone to
# start flying around!
#
# Also don't forget that this is a server wide setting for all bridges.
# Make sure that your users have a say and know about it if you change
# this setting:
bridgeMaterials: [43, 44, 125, 126]

# The maximum number of speed boosts allowed by having multiple power
# blocks (the support blocks beneath the bridge through which the
# redstone power is delivered to the bridge).
#
# If you set this too high your server load may increase exponentially,
# especially if you have many bridges on your server!
#
# Also don't forget that this is a server wide setting for all bridges.
# Make sure that your users have a say and know about it if you change
# this setting:
maximumBoosts: 2

# Whether to allow "floating" bridges; which in this case specifically
# means bridges that are not touching any solid blocks directly
# underneath. You can use this to prevent people from having bridges fly
# away uncontrolled, either by accident or on purpose.
#
# Note that water or lava counts as a solid block for this purpose, so
# you can still create ferries if you disable this.
#
# If you set this to "false", bridges will stop moving if they would
# lose contact with all solid blocks directly underneath them. In other
# words, it will always remain in contact with at least one solid block
# underneath.
#
# Note that it can still lose contact with its power block(s). This means
# that it is still possible to bridge large distances or to have two
# power blocks at the extreme ends of the bridge's travel.
#
# Also don't forget that this is a server wide setting for all bridges.
# Make sure that your users have a say and know about it if you change
# this setting:
allowFloating: true

# The allowed materials for the power blocks (the support blocks beneath
# the bridge through which the redstone power is delivered to the
# bridge). This is a list of block ID's. You can find a list of all
# possible block ID's at http://www.minecraftwiki.net/wiki/Data_values.
# If it is empty (the default), any solid block is allowed.
#
# By default, the power blocks can be of any solid type. This setting allows
# you to restrict that, in order to make it harder to build bridges. It
# may also slightly improve the performance of the plugin.
#
# The value is a list of block ID's between brackets, separated by
# commas. For instance, if you want to limit power blocks to diamond or
# lapis lazuli blocks, use the value [22, 57]. If you want to allow any
# solid block ID, the list should be empty.
#
# Note that only the power blocks need to be of this type, not *all*
# frame blocks!
#
# Don't forget that this is a server wide setting for all bridges. Make
# sure that your users have a say and know about it if you change this
# setting:
powerBlocks: []

# Whether sound effects should be played if SpoutPlugin is installed
# on the server *and* the user is using Spoutcraft.
soundEffects: true

# The URL to load the sound effect from when sound effect support is
# enabled. Sound effects are available when SpoutPlugin is installed on
# the server *and* the user is using Spoutcraft. Note that the length
# of the default sound effect is tuned to the bridge speed. It is
# played once for every movement for the default speed and once per
# two, four, etc. movements if the speed is boosted. If you change the
# speed, and you use SpoutPlugin, you will probably want to use your
# own customised sound effect, or turn off sound effects using the
# soundEffects setting above.
slideSoundURL: http://mc.pepsoft.org/plugins/retractablebridge/sounds/bridge_slide.wav

# The distance in blocks for which the sound effects can be heard.
soundEffectDistance: 24

# The volume in percent at which the sound effects are played.
soundEffectVolume: 75

You can edit this file to change the settings according to the instructions. Please note: if you change the movingDelayBase or bridgeMaterial settings, you will void your warranty! In other words, if it causes problems on your server you're on your own, don't come complaining to me. Be especially careful about allowing new block types for bridges. You don't want any flat surface on your server that happens to be next to a bit of redstone to start flying off! Don't use common materials such as planks, stone, cobblestone, etc.