Page 1 of 1
Ships leaving from the path?
Posted: Fri Jun 24, 2005 4:59 am
by olaf
Should this be flysprayed, or is this a usual occurrence?
Seen by my char, on the Dorian to Zhift Path, travelling from Baaak Hills (south) to Baaak (T 60 %)
1207-0: SD2 undocks, leaving travelling.
1207-0: You say: "Wow! *points* Look at that ship leaving the port... OOC - ???????"
(name of the ship slightly obscured because of the 4 day rule) But those affected will probably recognise the vessel...
Cheers,
Olaf
Posted: Fri Jun 24, 2005 5:03 am
by Talapus
Every few Cantr years it seems like there is a ship that departs that can be seen by anyone on a trail, and that includes everyone on every island. I had characters on both of the major continents see the ship depart at the same time. Don't know what causes it, but it is harmless and has been occuring for awhile.
Posted: Fri Jun 24, 2005 5:12 am
by west
I had a problem earlier wherein one of my boats was stuck in a harbour and it couldn't undock. Jos undocked it for me, but it undocked to "traveling" which was nowhere. I had to undock from there and wound up at sea somewhere, and all my characters on paths saw my boat undock, leaving travelling.
So that's how at least one boat got there.
Posted: Fri Jun 24, 2005 12:17 pm
by McManus
That had happened to me to but I think a different ships..I will check now. If the 4 day rule thingy doesnt apply here then I will name the ship.
Edit...same ship
Posted: Fri Jun 24, 2005 12:45 pm
by Surly
I always thought it was an error to do with ships undocking from other ships.
Am I wrong?
Posted: Fri Jun 24, 2005 4:07 pm
by Nick
Whenever I have one character travelling, and another undocks, everyone travelling sees my boat undock. *shrug*
In the middle of the dessert...
Posted: Fri Jun 24, 2005 10:48 pm
by NastySteve
WTF?
1204-0: Slashdot II undocks, leaving travelling.
1203-5: You are hungry.
1202-5: You are hungry.
1201-2: You are hungry.
1200-0: You leave Pok Desert (south), taking Pok Desert Routes to Moku (north).[/b]
Posted: Sat Jun 25, 2005 3:09 am
by Anthony Roberts
This error is caused when a boat undocks, and the person doing the undocking doesn't allow time for the page to load, and either loads another page, or attempts to undock once again.
I'm 95% sure this is the reason this has happened, as it's been discussed many, many times before.
I actually also thought it was fixed. As it hadn't happened for awhile...
No matter, just ignore such events. You seen nothing.