Character "Stuck"

Bugs & Features
1

So, my character Ignaruk Vhal-Zharuun is essentially stuck. I went to change his profile and it lagged a bit, so I refreshed the site. Now, that character cannot do anything at all. No commands, no text, no profile editing; nothing. It continually gets request timeouts.

I have cleared the cache, logged out/back in and used a brand new Google Chrome download with nothing synced, and it remains. Another character I have, on the same account, network, browser, everything… works just fine. I’m honestly not sure what to do here.

Edit to add: I logged out after sleeping all characters I had active (except Ignaruk) and flushed my DNS on Windows, and cleared Edge’s cached/cookies/site data. I logged back in and now that character does not exist on my character page. Here

2

Refreshing in the same room I got this and an empty looking pane:

EventBus.js:220  TypeError: this.lookingAt[(intermediate value)(intermediate value)(intermediate value)] is not a function
    at e.value (CharPagesChar.js:87:31)
    at e.value (CharPagesChar.js:103:8)
    at new e (CharPagesChar.js:35:8)
    at e.value (CharPages.js:106:25)
    at EventBus.js:218:15

This continues to occur if looking at Aspera Ailurid.

3

Morning all!

Okay. We have one of those.
I still haven’t found out why it happens.

@Skye , where your character the first to be affected, you think? When did occurr?
This is due to a character getting so-called “deadlocked”. Most interactions with a deadlocked character will cause your own character to end up deadlocked. And thus is spreads.

But I eventually need to find the reason why the ground-zero character ends up in that state, so I can fix the bug. What did they do when it happened?

For now, I will just restart the server and it will be allright!

4

I was in the Station Park. I clicked on a different profile to change to it. It “lagged out” and I refreshed the site to try and restart the connection (that usually fixes it for me) and then that’s basically when it all went downhill.

5

@Accipiter I managed to catch this snippet in the console when it was going on, I don’t know if it helps at all or is just, regular 404 errors but…:

Toaster.js:96 [Toaster] Error: h{rid: 'core.char.pc9p0qn5mrj005fq4o1g.ctrl', method: 'call.core.char.pc9p0qn5mrj005fq4o1g.ctrl.useExit', params: {…}, _code: 'system.timeout', _message: 'Request timeout',…}

6

It was something with the core service (Wolfery consist of a bunch of separate services, where the core is the main one).

Once restarted, it seems to work nicely again.

7

Ah, thank you very much. I’m glad everything is back to normal-ish. I appreciate it.

1 Like