Bukkit

@Secretbryan23

Yeah, its that old 3.1.32 build you're running. Best way to fix it would be to get the newest build. If you don't want the new build for some reason, you can also turn compatibility mode on.

@Secretbryan23

No, that shouldn't be happening. Make sure you aren't getting any errors when the plugin disables itself during server shutdown. On a clean shutdown it will write crate inventory to your plugins/movecraft/crates/inventory.txt file. If you see any errors on your console during server shutdown, let me know what the errors are.

That being said, crates are an imperfect solution. While the problem you are having is not a known problem, there are other known issues with crates. Firstly, because other plugins can't use crates you may have plugin incompatibility problems. Also, some servers have problems with the inventory.txt file becoming bloated over time. Overall I would recommend using dispensers for on-board storage.

@HaltsLongBow

the sign for rotation should read:

[helm]

Including the brackets ([ and ]). Then you right click on it and it turns into something resembling a ships wheel. With your hands empty, right click to turn right and left to turn left.

@HaltsLongBow

There is one for the old style torpedoes, which required redstone components to make tnt come out for the explosion. The new style works with a CollisionExplosion feature that is in the new version working its way to the approval system. I'll get you a video tutorial for that as soon as its out.

@thief001

Well, moving and then disappearing is a new one. If you get no errors in your server console, then we don't have much to go on. What server are you using? It could be a plugin conflict, what other plugins are you running?

@RagingKittyCat

Glad you were able to get things working. The .craft files you downloaded were intended to be mainly examples, I would encourage you to start messing around with them. I made them with airships in mind, because thats my personal obsession. But you might make a copy of the airskiff one, change its name to Airplane or something, and replace the wool requirement with a wood one and remove redstone, or something like that.

Basically, I'm saying you shouldn't feel limited to the deffinitions in the .craft files. Come up with something that works for you and your server.

@RagingKittyCat

Excellent, so we can see that the plugin loaded, and it found the craft files. Next we look at basic function and permissions.

Place a sign somewhere that says [helm]. Right click it. If it turns into a wheel, then you know the plugin is basically working. If that works, but you still can not pilot an Airskiff, check permissions. The easy way is to make your minecraft account an op on the server. Add your account name (not email address) to the ops.txt file. Alternatively, you can give yourself the following permissions:

movecraft.Airskiff.pilot

movecraft.Airskiff.move

movecraft.Airskiff.rotate

@RagingKittyCat

Unfortunately I need more information before I can really troubleshoot this. Does your server mention Movecraft on startup? If not the plugin is not installed correctly. It should tell you how many .craft files it detects. If its not more than 1 (it always claims to find 1), you may not have your .craft files installed correctly. You may also not have permissions, which is easiest to test by making sure the Minecraft user account you are using is in the ops.txt file.

@GodsDead

Chests won't crash the system or anything like that. But they do not work for storing items. My best recommendation is to use Dispensers for ship-board item storage. I might try to tackle chests "soon", but there are lots of different items requiring attention with the plugin.

There is no limit to the number of ships you can create, but ships do not exist as far as the plugin is concerned until they are piloted. So they do not consume resources on the server or anything like that.

Some color "fluff" might be fun to put in, that may get a place somewhere in the list of things to work on. I see combining block types as a lesser concern (IE: counting stairs or slabs as "wood"). Also, in that example I could float a brick ship since brick slabs are the same block id as wood slabs. I think it is best to estimate the blocks involved and tweak the numbers until you find something that works for your server.

You can use the bukkit /reload command, that's what I use when I'm tweaking .craft files. I don't like plugins that have a lot of commands, so I avoid them whenever I can. The only command that exists is /release, which is admittedly poorly documented. The most common way of releasing a craft is to walk off it. Right clicking the pilot sign forces the plugin to re-calculate its borders. This is by design for crafts with borders that change for various reasons like launching torpedoes / missiles.

The "unable to locate sign" errors are caused by failures in the communication chain between the Minecraft Client and Server. Usually, changing CompatibilityMode to false (only on Minecraft 1.6.4) resolves most of these problems.

It would be difficult to prevent users from placing blocks on a craft, I think this is a matter better addressed through instructing your users. All they have to do is right click their pilot sign whenever they make changes, and the system will recalculate the ships borders.