Boat issues
 

It happened to me today for the 2nd time. I have quite a serious issue with boats on CP Island.

I recently tried to use a boat I've found on the beach and as a result I was warped into a ridiculous level made of sand.
Then I tried to use a boat from the harbor, I got on it fine, took it out from the storage and when I got outside, I was standing on the black water, with everything of course black around it, and the boat was going, going.. I was not even on it !

I unsticked and got on it a bit later again, and same happened but I was now warped from where I was (north of the castle) to the complete north of Westford !

What the hell is wrong ?

I've made a few screenshots so you can see what really happened.

This happens mainly on cp but has happened to me on almost every isle. Boats need an upgrade in general. The fact that their main everyday use is to be unstickme vessels proves they fail. They're for sea travel but are so slow people can run to islands via dungeons about 15x faster than it would take to make a boat and take it to your destination. Also, boats have 0 security, unlike houses. After 2k hours most players have made 100's of ships which amounts to ALOT of wood yet it's all wasted on a slow, unprotected vessel which is better used to abuse the unstickme command. Sure, they're useful in events of the ship kind and ship wars (im not a fan) but that's basically it.

There should be weaponless, small and fast ships for simple travel (you run the risk of being sunk by larger ships alot higher if hit. I also think metal or some stat should make whichever boat you make travel faster, have higher durability and, in the case of the basic warship, more cannons.

Wow I absolutely agree, small boats for fast travel would be fun.

I'd also love to see the glitch where you are constantly kicked off from steering the ship. It's really annoying in boat wars (which are awesome, by the way).

Lmao you should see a boat i found at Cove town. It called gk_snowmanmouth0.png

I walked on it, Got warped to unknown.

I think Stefan posted this was fixed in a v6 update... so it looks like it's a client bug, and not a scripting one.