Bukkit

This is not required, and defaults to true. If set to false ("allowHorizontalMovement : false"), then Movecraft will ignore any pilot-induced horizontal movement. IE: pointing your pilot tool left or right and right clicking will not move the craft, and will not result in any failure messages. Other vertical movement, like from useGravity or sinking, will still be processed as normal. This is typically used for ocean going ships.

This is not required, and defaults to true. If set to false ("allowVerticalMovement: false"), then Movecraft will ignore any pilot-induced vertical movement. IE: pointing your pilot tool up in the air and right clicking will not move the craft, and will not result in any failure messages. This is typically used for elevators or turrets.

This is not required, and defaults to false. If set to true ("canCruise: true"), then the craft is allowed to have an automatic cruise command sign. Do this by placing a sign on the craft which reads "Cruise: OFF". The sign must be placed on another block, and can not be a free-standing sign. Then pilot the craft and right click the sign. The craft will then continue to attempt to move forward until you right click the sign again.

This is not required, and defaults to true. If set to false, (canDirectControl: false) the pilot can not use Direct Control to pilot the craft. Direct Control is a method where, as opposed to using the pilot tool to control the craft, the pilot's player movements control the craft directly. When the player moves forward, the craft moves forward. When the player moves left, the craft moves left. To move up, right click with the pilot tool. To move down, hold down shift and right click with the pilot tool.

This is not required, and defaults to false. If set, (canHover: true) the craft can hover a certain distance above terrain. Use this for a vehicle that should follow the contours of the landscape, for example a hovercraft or car.

This is not required, and defaults to true. If set, (canHoverOverWater: true) the craft can hover a certain distance above water. Use this for a vehicle that should follow the contours of the landscape, for example a hovercraft.

This is not required, and defaults to false. If set to true ("canStaticMove: true"), then the craft is allowed to have a move command sign. Do this by placing a sign on the craft which reads "Move:" on the first line, and the second line reads "0,0,1000" with the corresponding desired x,y,z amounts to move the craft by. Note that there are no spaces in the sign text. This also enables "Rmove:" command signs for the craft. This behaves exactly like the "Move:" sign, except the direction will rotate as the craft rotates. If a player is facing the sign, then the X coordinate will indicate how far the craft will move to the player's left or right, where a negative number moves left and a positive number moves right. Similarly, the Y coordinate moves down (-) and up (+), and the Z coordinate moves backward (-) and forwards (+).

This is not required, and defaults to false. If set to true ("canTeleport: true"), then the craft is allowed to have a teleport command sign. Do this by placing a sign on the craft which reads "Teleport:" on the first line, and the second line reads "100,87,300" with the corresponding desired x,y,z coordinates to teleport the craft to. Note that there are no spaces in the sign text. This is a very powerful ability, as the ability to easily teleport anywhere you like basically bypasses about 1/3 of the game. Accordingly, it is recommend you restrict a craft with this ability to certain users, or make them extremely expensive, or both.

This is not required, and defaults to False. If you put "CompatibilityMode: true" in your config.yml file, the engine will use generic CraftBukkit calls rather than the faster build-specific Minecraft calls. The result is that for a slight drop in performance the plugin will work for a wide variety of Minecraft or CraftBukkit builds.

This is not required, and defaults to 0.0. If set to a number (collisionExplosion: 4.0), then if the craft collides with any block it will cause an explosion of the magnitude indicated. An explosive value of 4.0 is roughly equivalent to TNT. This can be used to create ship collisions and ramming, as well as aerial and naval torpedoes.

This is not required, and defaults to false. If set to true ("cruiseOnPilot: true"), then when you right click the command sign for the craft it will immediately begin moving in the direction indicated by the command sign. IE: it will move in direction opposite the facing of the sign. It will also not release whatever craft you previously had piloted. Note that this means multiple such crafts could be launched simultaneously by one pilot. One use of this would be torpedoes.

This is not required, and defaults to 0. If set to a number ("cruiseSkipBlocks: 4"), then the craft will skip the specified number of blocks when attempting to move the craft forward while cruise is on. The effect is that it moves significantly faster. For large crafts, it is recommended to have a low "speed" and put a number in here to compensate. This helps lower server lag and encourages more realistic forward movement instead of ships that move as quickly in any direction.

This is not required, and defaults to 0.0. If set to a number (fuelBurnRate: 1.0), then the craft will require fuel loaded into a furnace somewhere on the ship in order to move. It burns coal, charcoal, or blocks of coal based on the number of items the fuel could smelt/process. For example, with fuelBurnRate set to 1.0, a craft could move 8 times from a single piece of coal. With fuelBurnRate set to 0.5, the craft would move 16 times with the same piece of coal. Note that a "move" could be a cruise, which could be skipping blocks. The effect is you may move far more blocks on the same fuel supply if you are cruising than if you are maneuvering.

This is not required. If set, hover type crafts will allow the vehicle to move through the listed blocks. Blocks must be strings, not integers, similar to the following: http:jd.bukkit.org/rb/apidocs/org/bukkit/Material.html Typically this would be set to grass or flowers so your ground vehicles are not obstructed by them.

This is not required. If set, (hoverLimit: 1) it will control how high a craft can hover above the terrain. 1 would be appropriate for cars or trains. There are performance implications to setting this too high, so a small number is recommended.

This is required. This controls what language the engine will use for notifications. By default it is specified as en (English). Current supported languages are en, cz, and nl.

This is not required, and defaults to having no limit. This specifies the maximum height the craft can operate at. For water based craft, you may want to set this to just above the ocean level of 62. Note that you don't have to, and a submersible or surface ship can actually fly if you set this high enough. Many users report experiencing extra server lag as airships fly higher. You may want to limit this accordingly.

This is not required, and defaults to having no limit. This indicates the furthest distance that can be traveled with a single click of a Move: or Rmove: sign. This is to prevent abuse of the static movement system.

This is not required, and defaults to having no limit. This specifies the minimum height the craft can operate at. For water surface ships, you may want to set this to just below the ocean level of 62. Note that it does not check this limit unless you actually try to move up or down, so surface ships can operate at high altitude lakes if desired without changing this value. Submarines should have this value set low or not set at all so that they can dive below the water.

This is not required, and defaults to true. If set (moveEntities: false), the craft will not move entities on top of it. This is usually used for weapons like torpedoes or rockets.

This is not required, and defaults to 280. This specifies what tool you use to pilot crafts. For example, if you put "PilotTool: 288" in your config.yml, then instead of using a stick to move crafts, you could use a feather.

This is not required, and defaults to 100. This specifies how frequently the engine checks to see if a ship has been damaged enough to start sinking. It is also in Minecraft ticks, or 20 per second. For example, if you put "SinkCheckTicks: 200" in your config.yml, then it will only check to see if a ship should be sinking every 10 seconds instead of 5.

This is not required, and defaults to 0.0. If set to a number (sinkPercent: 90.0), then if the craft drops below that percent of its required flyblocks, then it will begin to sink. Usually this is due to damage by fire or explosives from enemy ships. Once the ship starts sinking, it will sink through air and water until it hits bottom.

This is not required, and defaults to 20. This specifies how rapidly sinking blocks from damaged crafts will sink. The number is in Minecraft ticks, of which there are 20 per second. For example, if you put "SinkRateTicks: 40" in your config.yml, then damaged ships would sink at a rate 1 block every 2 seconds. If you get lots of server lag while big ships are sinking, this is the number to play with.

This is not required, and defaults to 0. If set, the watercraft system will always use the indicated water level when it fills in water behind the ship. The default behavior is for the system to scan the nearby terrain and determine the water level from that.

This is not required, and defaults to false. If set, the vehicle will fall as it moves until it reaches its hoverLimit above the terrain. It will also cause any craft above its maxHeightLimit to fall. This can be used, among other things, to make torpedoes that can be dropped from aircraft and run underwater.