Age of Unity

the past few days i have been going LD constantly. During raids and when im just playing in general. Anyone else having this issue or is it something on my end? I have a new desktop and a good internet connection so im not sure what it is?

It's hard to know at the moment since we are all going LD a lot when zoning due to server problems.

For many years I have never gone LD except when internet goes down, but I did last night. This was because the zone time took forever, and I had to kill EQ task and restart.

Others will know better things to check, but you should try this when the server is in a quiet state (not main server raid times) and see if it happens then. If yes, then it may be a problem your side as well as the server.

Last night, as you went LD in Lceanium, it must've been on your side only.
Both Frod and my two chars had no issue.


Ofc i don't know how you define a "good internet connection".
And to give advice where to look we lack information really.

First thing to check is always your router's error log - did perhaps the ISP "interrupt" service for a short while?
(It doesn't happen often, but even here in the first world of Germany some ISPs do random "maintenances" or remotely force-reset the modems or force-disconnect after 24/48hrs as the IP-lease runs out...)


Problematic pieces of equipment might be the router, the cables (lacking or weak EMS might allow interferences from cordless or mobile phones or similar to cause packet loss and lead to LD's) and the connectors.
Another possible (but VERY much unlikely, since EQ doesn't use much) issue might be bandwidth;
If you share bandwidth in the house for example, wrong setup of the priorities while other occupants are doing some heavy downloading might again lead to issues.

In my old flat, with my land-line-bound Provider, i had even to use a "keep alive" script to prevent them from disconnecting me after like two hours of "inactivity"
(e.g. during nights, in tradermode, when only a very few packages were exchanged)

The more latency you have, and the more steps from your home/provider to the server, the more prone you are to 3rd parties influences too ofc.
Doing a tracert might help to identify some of those issues.
For example, we had (a decade or more ago) a period in Europe when some "backend" provider (one connecting internet nodes) had issues.
Of course this didn't remain undetected for long as a tracert readily identifies such a case.

These days though, the most likely cause of such issues are to be found in the "last mile", from your provider's utility box to your computer.
And aside from any logical issues (found in the router most likely), it's most likely interferences (CB and other electrical equipment with lacking/broken shielding) and/or shoddy cables.
Not knowing where in the US you live but knowing how badly the cabling is done there by providers sometimes, i wouldn't rule that out - but only if you have general connection issues, e.g. with interrupted long downloads besides EQ as well.

Lots of people are going LD when others don't Morrok..

I have had on several occasions where I would 3 box and one box would suddenly go LD and others not, theres no soubt AB has some serious issues at the moment.

Vaako wrote:I have had on several occasions where I would 3 box and one box would suddenly go LD and others not, theres no soubt AB has some serious issues at the moment.

Yes, AB has issues.
Not really but it feels as if the problems were with AB.
Actually i am pretty sure the problem is with the login-server/handshake.
And no insisting make it true that it's "only AB" either - in basically every thread or jira-ticket there's talk of other servers with the same problem, only to a much lesser (noticeable) extent.

If you re-read the above post, i referred to a specific LD by him, where no zoning and no zonecrash was involved.
It had, tbh, any signs of simply "pulling the plug".
I box too.
And outside of the zoning issue, like at yesterday's raid, i have never experienced a "sudden LD" of just one of the boxes while all were in the same zone.
Practically, that can not be the server's fault if that should even happen.
Once successfully zoned, that AB instance handles the char - as it handles all chars.
IF there were some LD'ing going on during normal operations, then more than AB had an issue - that would be a general bug in the instance-handling or internal packet-routing.
I think we can take it for granted that they do NOT keep two code-branches around, one for AB and another for the rest of the clusters.

Don't get me wrong - i do not doubt that one of your boxes crashed ("went LD") when others didn't and no zoning was involved.
But if that happened, then you should check your memory for possibly defect RAM-areas rather than blame AB.
i just can't think of any half-serious architecture server-side that would allow such a scenario.
But who knows.. perhaps the german in me is simply not imaginative enough...

It turns out that it was a very simple solution...the cable from my router was bad...thanks everyone for the help