BALMUNG SERVER GARUDA INSTANCE

bumping up

Question can you still log in with other char in your account? can anyone try this out who have other char? it could be the same issue few people have for over 5month that there char files got corrupted. Because if you can't still log in and the servers are up it mean A: files are corrupted or B: The servers don't know where the hell you are in game. lol

Yes, we can log with other characters.

Quote:

---

Originally Posted by Pietro

Yes, we can log with other characters.

---

So it's the same issue like that other guy who can't log on his char for over 3+months now. It seem when the game d/c while doing garuda the char file could have been corrupted if you can log on other char in the same account but not that one then sadly it seem that it was indeed corrupted.

Let's hope now that more players have this issue they would find a way to recover all your chars back.

Quote:

---

Originally Posted by Zenaku

So it's the same issue like that other guy who can't log on his char for over 3+months now. It seem when the game d/c while doing garuda the char file could have been corrupted if you can log on other char in the same account but not that one then sadly it seem that it was indeed corrupted.

Let's hope now that more players have this issue they would find a way to recover all your chars back.

---

It isn't corrupted it's just the location is lost..

yup location is all screwed up

Quote:

---

Originally Posted by madbadger00

yup location is all screwed up

---

or it could be that happen to me a while back but i could log in i just every time i talk to a npc it mess up and could not leave the airship area then when i did i was stuck and could not teleport.

Has anyone on Balmung run Garuda since this? Is it still crashing?

Hope it get fix soon :(

yes. People can still go in. It's been buggy as hell for the past few days. On some parties, before we got stuck, we would crash/r0 as many as 3 out of 10 fights.
The 8 of us who got locked out were in a PT the day before it happened. We almost called the PT off, because we were having a hard time not DCing or crashing or having something on the server go wrong in the instance.