Bukkit

@Pitsols12

Yeah, in the default crafts file there is an ASM.craft that may interest you. ASM = Air to Surface Missile. Basically it goes diagonally downward. To make it go straight down, just change cruiseskipblocks to -1. Its wierd, but it works.

Sadly, I think the fireball behavior will have to be global. I don't have an easy way to tell which ship fired the fireball.

I haven't used dynmap, but overviewer works fine with movecraft, showing all the crafts where they were at the time you rendered the map.

@Pitsols12

Hey Pitsols12, I have been thinking about your previous question, about fires not sticking with crafts. What do you think of making it so fire charges have a chance, say 25%, to replace a flammable block they strike with a fire, rather than starting a fire on its surface? That way it guaruntees at least some damage to the target, plus the fire would be carried away when the craft moves because it would be on it replaced one of the craft blocks.

This would only affect flammable blocks, not armor. So still no punching through armor with fire guns. And it would be a setting in config.yml. Defaults to on, but can be disabled.

@Pitsols12

Yes, with the Remote Signs. The only downside is the silo itself must be a craft that is being piloted. Otherwise the plugin would have to search the entire world for a target sign every time you use a remote sign. So that is why it must be a piloted craft, so it only has to search within that crafts blocks.

@GodsDead

The permission list on the PMC page (http://www.planetminecraft.com/mod/movecraft-reloaded---loraxe42s-fork/) is up to date. It's not currently possible to grant access to /release but not /cruise. If you create an "issue" requesting that as a feature on the github page (https://github.com/msummers123/Movecraft-3/issues), I can see about adding it, possibly next week. I would also like to discuss how it should work. For example, possibly leave in movecraft.commands, and add movecraft.commands.cruise and movecraft.commands.release?

@Pitsols12

This happens primarily to surface fires.

Its because the fire sits on other blocks. If you move a ship, the ship moves away from the fire, but the fire stays still, now standing freely in the middle of the air. Then minecraft removes the fire because it no longer has a block to burn nearby.

It is not total immunity, however. It only works with surface fires, and only if the craft can move away from the fire. If the fire is large enough they will not be able to move away, because the fire itself will block them. Also, fires that burn in the interior of a ship will move with the ship and not go out. Another major issue is the speed the craft moves at. A slow craft will burn much more readily than a fast one. A common mistake with Movecraft is to make crafts move too quickly, which causes all kinds of havoc and makes them impossible to damage.

On fires, I am currently evaluating if this behavior should be changed. One possibility would be to make it attach any nearby fires to any moving ship, so the fire always moves with it. Although fast moving crafts would still never burn just due to Minecraft mechanics.

EDIT: also, it would be a lot of work...

Ok, another major Movecraft annoyance has been removed. For a long time if you cruised in an airship for an hour or 2, or if you were battling for about 30 minutes, your client would run out of memory and crash.

This was due to a bug in the Minecraft client, and the way chunks were sent from the server to the client. I can't fix the minecraft client, but I figured out a way to bypass the normal method of sending chunks by writing my own system for updating certain blocks. It only works in compatibilityMode, which is the default.

The new system is also more efficient, requiring less data to be sent to the client.

So NO MORE CLIENT CRASHES!

Also there are a number of bug fixes in this latest version and other new features, like the ability for fighters to take off from carriers without the carrier first being released.

I have submitted the file here, and you can always get the latest version on my PMC page.

@billdcat21

So, I would recommend you use the cruise signs to move more quickly, and leave the default movement speed low to reduce lag and encourage realistic movement. IE: your airship can move at a decent speed straight forward, but not sideways.

I show how to make a ship along with its cruise sign in the tutorial, I'll link the exact time I show it: https:www.youtube.com/watch?v=8dVEul7hG78#t=1505

That also shows the helm sign on the ship, so you can turn it. After I make the ship I make a submarine, and talk about why you want to use the cruise sign instead of moving with just the stick.

@GodsDead

Honestly I'm not sure. I would guess not. But give it a try and let us all know what happens.

@Guthixlord1

It could be you have a block in the ship somewhere that is not on the allowedlist in your airship.craft. If you can get me a schematic of the craft I may be able to tell you where it is.