Selbina to Mhuara Boat instantly warps you! Huge Glitch!

[Koosey]

Hello!

While fishing these past few days on the Selbina to Mhuara boat. I noticed the following:

When I go on board the boat in Selbina to Mhuara. I will go on the ship then
I see the animation that leads to the Selbina boat ship ride. Now I see the same animation then I will be instantly warped to Mhuara. Right at the same place where the Selbina boat normally drops a player off.

This has only happened to me during the Selbina to Mhuara boat ride.
Never during the Mhuara to Selbina boat ride. Also I play on PC.

Please fix this soon because I do not like being warped to Mhuara missing my boat ride.

Thank you,
Koosey

[Qeepel]

Thank you for bringing this to our attention. I'll be happy to escalate your report to the developers for testing. However, they will need the following information for testing. While some information may seem unnecessary, it is needed to help reproduce the problem. Can you please fill out the template below? Thank you for understanding:

Thread Title:
Short outline explaining what sort of issue you are experiencing.

Platform:
Specify which platform was in use to play the game.("PlayStation2", Windows, and/or Xbox 360)

ISP:
Name of ISP you use to connect to the Internet.

Type of Internet Connection:
Specify the type of connection. (dial-up, DSL, CATV, Optic Fiber, Other)

Internet Connection Speed:
Specify the speed of internet connection. (Example: 768Kbit/s, 5Mbit/s)

Date & Time:
Date and time of when the issue occurred. Please be sure to state the time zone of your region. (Example: Pacific Time = PST/PDT)

Frequency:
State how frequently the issue occurs. Please select from the following.
1. Always
2. Sometimes
3. Once (did not reproduce)
4. Unknown

Character Name:
Which character did the issue occur with?

Race:
Race of your character when the issue occurred.
(Hume M, Hume F, ElvaanM, ElvaanF, TarutaruM, TarutaruF, Galka, Mithra)

World:
World where the issue occurred.

Main Job:
Main job and level of your character when the issue occurred.

Support Job:
Support job of your character when the issue occurred.

Area and Coordinates:
Area and map coordinates where the issue occurred.

Party or Solo:
If you were solo when the issue occurred, please write "Solo". If you were in a party, please write "Party". With alliance, please write "Alliance."
*If you wrote "Party" or "Alliance", please also include the number of members.

NPC Name:
Name of NPC that your character was interacting with when the issue occurred.
*If you were not interacting with any NPC, then please write "None".

Monster Name:
Name of monster that your character was battling against when the issue occurred.
*If you were not battling against any monster, then please write "None".

Steps:
Detailed steps on how the issue occurred.
*Please try to include the following details.

* What you were doing when the issue occurred. (Example: Battle, mission, quest, crafting, synthesis, etc.)
* Please do your best to write using official terms for item names and skill/ability names. Please avoid any abbreviations or improper terms.
* If you were using macro commands when the issue occurred, please include the details of the command.
* In case the error message appeared when the issue occurred, please include what the message said.


*In case you cannot post all of the information in a single post due to character limitations, please make multiple posts.

SQUARE ENIX MODERATOR

[Daniel_Hatcher]

That's kinda cool, though it doesn't happen for me.

[Dsherman]

This may be a problem just on your world. I did observe a problem like this once on Siren with the ferry from Whitegate to Nashmau. A short time later, I noticed the Vana Time in Whitegate was set about 1 earth minute fast (or about 25 Vana minutes). The clock on the area server for Whitegate was wrong. It was fixed the next time the servers were taken down for maintenance.

If it is still happening, it could be that the clock for the Selbina area server, or the Ferry area server is wrong on that specific world.

It is possible that SE may have never noticed the problem. If servers are re-booted as part of bringing them back up for normal service, the clock will have been corrected as part of booting without anyone else ever noticing the clock was wrong.