Return of Reckoning

This is a bug. I've already poisoned the jarl.

Hey here's something that I'm not sure is a bug: the stealth cloak is unnecessary. Ordinary npcs in IC won't aggro if I'm unhidden and it's much easier to navigate and interact while mounted.

I got to the front of IC and around to the arena without using the cloak, though there are ton of Death ...

It's not, so I can't thank you for trying.

Good news is the coords are 30/42, so maybe that'll help. It's also nowhere near the blood splat quest location.

Shout out to Dementuss for actually leading people, including me, to the banner. That's being useful.

I am one of a dozen people swirling around the Order entry point in IC. Nobody can find it, nobody knows what it looks like.

Coords please.

edit: just had my 4th failure from time out. This quest is a bitter joke.

Same, though in my case I can connect and play when I log in to patch. That's...curious.

After that though, even if it's the exact same day, no luck. Once for patches and not after.

oh hey!
Me again!
This same problem!
Wheeeee!

Changed my pw to something simple, tried a proxy, tried a re-DL, etc etc etc same basic issue of functionally being unable to serially connect to the server more than once every two weeks.

Good news!

RoR worked!

And I logged out and came back and it worked again!

...but not a third time. Haw Haw. XP

Now we're borked again.

Did a full delete and reinstall etc etc. Using a VPN made no difference.

Interestingly it's once again doing the thing where when "Read Only" is unchecked it ...

Well I hate to jump on this bandwagon but it's more of the same here.

Did the VPN thing, opened ports, changed my password, unchecked Read Only, and tried every step reccommended in this thread up to this page.

I distantly recall this being part of what killed WAR the first time out.

edit: so ...

Oh, and:

[2018/01/14 21:21:34] LoginInterface::DoEventNotify: Sending event type [9] to loginserver
[2018/01/14 21:21:34] Attempting authentication using session token
[2018/01/14 21:21:34] MythLogin::LoginClient::AuthenticateWithSessionToken: Attempting to authenticate with session token
[2018/01 ...

Well I hate to jump on this bandwagon but it's more of the same here.

Did the VPN thing, opened ports, changed my password etc etc etc same old no go.

I distantly recall this being part of what killed WAR the first time out, perhaps.

edit: so here's an "odd" thing. Though I get ejected with an ...