Page 1 of 1

LDON glitch?

Posted: Wed Aug 24, 2011 3:36 pm
by soakked
I have experienced two problems with LDON recently:

1) Sometimes the bot that I zone in with stays still and doesn't do anything even when I attack, causing me to relog the bot which negates sune buffs and wastes sometime (3 min relog)

2) Sometimes when I start a quest (boxing) one character would get the window alerting me of the quest and the character (leader of the group) that started the quest wouldn't get the window alerting me that I am on a quest. When I try to zone in to start the quest it gives me a message stating that I have no current adventures (with the leader of the group, the quest starter). I would then check to see if I have any quests in my quest log and it would say no. When I go back to the Orc NPC that gave me the quest originally to start a new one, it says that I already have one quest active. The only way for me to solve this is by relogging the character and trying again.

Anyone else have these problems with LDON?

Re: LDON glitch?

Posted: Wed Aug 24, 2011 4:59 pm
by Deadspirit
I only can help with #1 - I havent found a solution to #2.

For #1: instead of camping the bot and losing buffs just disband the group and re-invite. They will promptly follow you and assist. I have this problem in 50% of zones but I don't consider it anything more than a minor inconvenience.

DS.

Re: LDON glitch?

Posted: Wed Aug 24, 2011 5:19 pm
by soakked
Cool thanks, I'll try that next time.

Re: LDON glitch?

Posted: Wed Aug 24, 2011 5:24 pm
by Deadspirit
Also, I heard this doesn't happen with SOD client. Not sure.

Re: LDON glitch?

Posted: Wed Aug 24, 2011 9:34 pm
by Lumpa
For #1, you can prevent this bug from occurring if the character that owns the bot zones in before the rest of the group. This bug affects all zoning, not just ldon.

Thanks to Javel for telling me this little tip!

Re: LDON glitch?

Posted: Tue Aug 30, 2011 4:34 pm
by Snorks
Deadspirit wrote:Also, I heard this doesn't happen with SOD client. Not sure.



You can still get this issue with the SoD Client.