EZ Server

I have spoken with everyone that I talk to and no one else has reported the same issue.

Basically when I create any instance of Abyss and zone into the zone, the first pull is just the bridge to the door, the second is 5 or 6 mobs past the first door. The first corpse to have a item on it I can loot is when I stop pulling.
As soon as I loot I desync every character and have to /exit and relog.
After I relog the zone is stable and does not crash again.

About 30 seconds after I log back in I see Zone connect: The Abyss

What I do is log everyone into public, create the instance and zone in my main or if I still have a instance zone in my main. After I zone in on Felony I zone in the groups one by one until everyone is in the zone.
/bct g3 //say enter guild
Wait until the 5 alts are in and repeat for G2 and then G1.
I never zone more then 5 at a time into a instance to prevent my characters from locking up and to not lag the public zone.

I have tried guild and raid instances. I have tried waiting up to 20m after I zone in my warrior before I do anything. I have tried without MQ2 loaded.

I have no clue why this happens and without access to the log file for the zone can not provide any more information or debug what is going on.

I never had this issue before waypoint change which was last time I went into abyss but I doubt that is the reasoning and we have not had a source update and no one else is reporting this same issue.

Basically I just zone in, set the raid up and pull once or twice and let the zone crash on me and relog. Sucks to have to relog every client but my .bat file handles that for me.

Hunter if I get exact <Date|Time|InstanceID> is there any chance you can take a look at the log file or shoot me a copy of it.

I doubt I can replicate the exact condition of the zone or I would debug it on my server.

does it happen if your grouped or in a raid with another individual and they create the instance and you zone in from there or only with instances you create on all your accounts?

It has been just my groups so far.
If anyone has ideas for me to test to see if I can narrow this down let me know.

Sometimes zones do bug out. Worse case wait for server reboot, that tends to fix it. Usually happens when I'm editing the database while server is up and running at same time.

This has been happening for the last week. I'll keep trying new ways of doing things and see if I can narrow it down but doubt I can. As is I just have a routine where I log in, zone in, crash, /q, relog and go about my business.