Page 1 of 1
EQ2Emulator bug?
Posted: Sun Jan 15, 2012 7:50 am
by Chrisworld
Is there some sort of bug with the EQ2Emulator server and using the /zone feature? I was logged in last night on my downpatched 6118 client for a bit, then I got the live client to work following Xinux's post here:
http://eq2emulator.net/phpBB3/viewtopic.php?f=26&t=2928. Well I tried logging in this morning and I was in Antonica exploring the NPC-less landscape the night prior so I tried to zone to the Queens Colony where there is content only to be met with the forever-never loading "Connecting to Zone server". So I manually closed the game and came back, it told me there is a character in the world and to wait... like when you go linkdead in live. So I waited, nothing. Infact, I waited an entire hour and he's still stuck in the game logged in preventing me from logging in. What gives? Bad client version? How can he be stuck in the game with no connection? I thought it would be terminated when it times out, unless eq2emu has a super high timeout rate.
Re: EQ2Emulator bug?
Posted: Sun Jan 15, 2012 9:40 am
by Zcoretri
See if you can change your characters location in the database back to where is was before you zoned.
I suggest you use the safe coordinates when you do this.
Re: EQ2Emulator bug?
Posted: Sun Jan 15, 2012 12:26 pm
by John Adams
If this is a spawn-populated world, yes. There is a known issue with disconnects causing a zone to become unresponsive. If you are using the DB Milestone 1 content + scripts, you can see this at the console by the NPCs no longer attacking each other.
World restart is the only solution.
Re: EQ2Emulator bug?
Posted: Sun Jan 15, 2012 12:32 pm
by xinux
Must be it since i'm having no issues zoneing between Queen's colony and Timorous Deep
Re: EQ2Emulator bug?
Posted: Sun Jan 15, 2012 5:01 pm
by Chrisworld
Yeah but this is on your server guys, I don't know where yet to mess with the DB... it's not on my copy of the 1.3 repack.
Re: EQ2Emulator bug?
Posted: Sun Jan 15, 2012 6:18 pm
by xinux
Eq2emulator server was having some lock up issues so you may have been trying during that time.