Bukkit

@Conorserver

I would like to find out more about your problem first. Is the problem that the ship never sinks? A common misunderstanding is that it calculates the sink percentage based on the remaining blocks in the ship, not the total. For example, if you had a ship where either the front half of the ship or the back half of the ship is capable of floating by itself, blowing off half of the ship will not cause it to sink, because the remaining half floats.

To sink a ship, you have to affect its percentages. So, in other words, eliminate the flyblocks while keeping the "dead weight" on the ship. If you blow off all of your targets guns and armor, it actually floats better than it did before you fired a shot. The most reliable way to make a ship sink is to set it on fire (assuming your flyblocks are flammable). That way the flyblocks are gone while the heavy non-flammable weapons and armor remain, causing the ship to sink.

EDIT: and if we are talking about ocean vessels, filling their ship with water will also affect the percentages, because it counts water blocks as "weight"

@PingPongBall52

I apologize, there seems to have been a typo in a section of the documentation. It is correctly spelled:

blockedByWater

I have corrected the place where the typo was.

@jeffro1001

Not yet. At the moment I'm waiting on AJCStriker to approve the previous dev build (for 1.7.5) before starting work on the next version that will support 1.7.9 (or possibly 1.8 if they come out with it).

You can use it in 1.7.9 if you set compatibilityMode: true in the config.yml file. However performance will suffer and you may get a few "cannot find sign.." errors.

@sequoia22

I would recommend against using the typed commands. They are intended mostly for debugging purposes. The intended method of control is using signs and the pilot tool. Refer to the tutorial or the quick start guide. One likely reason you may be having problems is not having .craft files. Again, refer to the quick start guide or the tutorial.

@PingPongBall52

Could you give me more details? In my tests it seems fine. The syntax / spelling in the .craft files must be exact. Check to make sure you aren't missing a ".0" on a number that requires it, like the speed.

@dragonzrmetal

Either of those options are possible, but would require a rewrite of the sinking code. Currently the sinking code is not craft specific, all sinking blocks are added to a generic heap.

I want to make sinking better, for example I want fighters to crash into things as they fall instead of just dropping slowly, and I want different sink speeds for different crafts. So I'll be re-writing the sink code anyway. It probably is a good idea to also give an option for overall craft damage to cause it to sink, although I personally prefer the current method. It encourages clever designs that mitigate and control damage. Fire has always been the reliable method of sinking a ship (like it was historically). As long as the flyblocks are flammable, and require a high enough percentage, airships will sink if you know how to kill them.

But, I can see why people would want a more simplified sinking engine. Particularly if they want flyblocks that aren't flammable. Not to mention that sinking becomes nearly impossible if fire spreading is turned off for anti-griefing purposes.

Anyway, I anticipate putting in those changes in the next release, after ACJStriker posts the current one. So it will be several weeks. Other changes I want to do are active sub-crafts (think turrets on a battleship), and the .craft file overhaul.

EDIT: Just so I'm clear, I meant to say I like your suggestions, and have added them to my list. Sorry, I've been working on the next Minecraft Airship Pirates video all day and my brain is a little fried!

@justin393

That error indicates you are trying to use a different version of Bukkit/Spigot than the one your version of Movecraft was built for. If you want a build for 1.7.5, use the download on the dev build video: https://www.youtube.com/watch?v=G_d-GVBC4vg

If you have a newer build than that, you will need to turn on CompatibilityMode, at least until the current build gets posted.

@sequoia22

I prefer not to use any typed commands unless absolutely necessary, as it is a less intuitive experience. To make a command sign, just put the name of the craft type as the first line of the sign. For example, to command an airship, just put:

Airship

The other lines can read whatever you want. Then right click the sign with an empty hand, and you should be able to pilot the craft.

@GodsDead

Yeah, 1.7.9 isn't supported. You can use CompatibilityMode: True and it will work, although in a reduced capacity.