Bukkit

@serpental

That's weird. Both the task 9 error and the obstacle on the course errors are old Ships plugin errors. Could you copy the exact error from your server console and send it to me in a PM using the mail feature of this site?

The new torpedoes are actually supposed to leave signs behind, so that is normal. For torpedoes to work underwater they have to be fired from tubes or your ship would flood. I had a hard time designing a tube that would fit both the torpedo and the signs that command it until I realized the simple solution: Don't make the signs part of the torpedo. It works much better now.

@serpental

Getting any errors on the console? The entry in your .craft file should read exactly:
canCruise: true

And the sign should say on the first line:
Cruise: OFF

You can have anything else after that first line, like Torpedo Launch or whatever.

Ok, new code from mwkaicz has been added to the other changes for the beta. There is some new features for you guys to try out, let me know if you have any problems.

Here are the new features from mwkaicz, please let me know if I get something wrong:

- Ships don't sink through the void anymore
- New craft options:

1. canHover - For Hovercraft, which follow the contours of the land
2. canHoverOverWater - Same as above, but over water
3. moveEntities - if false, the craft will not move players or entites on it (IE: for torpedoes or rockets)
4. useGravity - if true, the craft will fall over time
5. hoverLimit - if set to a number (say... 2), is the distance above the ground the craft will hover to. Keep this number low.
6. harvestBlocks - list of materials through which the hovercraft will move (IE: grass and flowers). Does not affect non-hovercraft.

This is in addition to the other changes already in the beta, including:

- single chest support (double chests will throw an exception)
- spawn points on ships will move with the ships (if you are logged in when the ship moves)
- optional staticWaterLevel setting in the craft files, if set then it will use that rather than determine the water level from surrounding terrain

You can download the beta for this here: Link removed

Please note this has not been tested by the dev.bukkit.org staff, and should be used at your own risk.

@ricturd

Actually I would recommend against using crates. Single chests are now supported with the beta build, which you can download from this link:

https://dl.dropboxusercontent.com/u/11164014/movecraft_beta.zip

I would recommend you use single chests. Double chests will cause problems and should be avoided.

Also, could you please refrain from putting the little "HELP"s and "PLEASE"s in all caps at the end of your question? It's a pet pieve of mine, it makes it seem like you are shouting at me. While I do sometimes miss questions, Serpental's for example, I assure you the all caps don't affect the chances of your's being noticed or missed.

@ThinkOnTheEdge

Interesting. Is this with the new beta build? If so, I think I might know why. I found a bug I will fix and get you a new beta build momentarily. If not, check for errors in the server log right before it happened. That usually happens if the plugin crashes or is reloaded while translating a craft. It could also happen if the server shuts off while a craft is being translated (IE moved)

@grdgyyr

Virtually all blocks are supported. In the current release version, chests don't work. But in the beta release chests do work. Double chests do not work though. I have noted some random problems with pistons and would discourage their use. You can use the bukkit /reload command, thats what I use when I am testing crafts. There is no movecraft specific reload.

@ricturd

I'm afraid there are currently no plans to introduce trains.

@serpental

In order to get the other options in your config file, like the pilotTool option, you have to manually put them in there. I think I will change this in the next version though, and include all options by default.

The [helm] sign is a very basic function and if that doesn't work something is seriously wrong. Make sure you are typing the sign correctly. The first line should read:
[helm]
And that's the only thing that should be on the sign. Include the [ and the ]. Right click it with an empty hand and it should change into an icon for a ships wheel. If its still not working, check for errors when the plugin initializes.

@jeffro1001

Glad you have enjoyed it so far, I think you will find cruise will add alot to give your crafts a more realistic movemet feel. So lets get it working. The correct syntax is:

Cruise: OFF

on the first line. The other lines dont matter. It sounds like you have this right but it can't hurt to double check. Other things to check off the top of my head:

use a right click, not a left click
make sure your hands are empty when right clicking the sign
make sure you are using a version of Movecraft later than 3.1.36
you do have to be in command of a craft for the sign to do anything, but you don't have to be in order to create the sign, the sign is just a normal sign, nothing special
if it works, the sign should change when you right click it into Cruise: ON

The last thing I can think of is to make sure that the craft type on the command sign you use to pilot the craft is the same as the craft type name specified within the .craft file that has cancruise on. Not the name of the .craft file itself, a mistake I still make from time to time.

@WolfeBersahd

I believe mwkaicz may have already fixed that bug, right now we're trying to get his changes integrated with the most recent changes I've got. Expect an update in the next day or so.

@ThinkOnTheEdge

deleting all thinks was unnecessary, problem was only in localisation/

And what you describe below I fixed yesterday morning :) ... there was problem in code, wait for next release.