(Still) can't login due to connection timed out - save issue?

[Player Name]

This is a follow-up from https://gitlab.com/2009scape/2009scape/-/issues/1449. I thought this was simply a bug in the server that would unscrew itself after the reset. But it hasn't - I still can't log in, with the same "connection timed out". That suggests that the problem is not something that is running on the server that has gone a bit loopy, but that whatever the problem is also got propagated to my savefile. Could you take a look?

One thing that has changed, which seems important to mention, is that now my account does show as logged in on the friends list during the login attempt.

(Of course, I realize that ceik's just-merged MR is likely to fix this problem from occurring to future players - but it's not obvious to me that that MR getting pushed to the live server will cause my save to get itself unstuck on its own. If it will, I can just wait it out!)

[Ceikry]

Can you recheck after the hotfix update is deployed?

[Player Name]

Ah, was just editing in that I'm totally willing to do that, of course
I assume that that will be after tomorrow's usual reset?

[ryannathans]

hoping within minutes/hours

[ryannathans]

try now

[Player Name]

No change.

In case the issue is somehow caused by the deep wildy threat timer (which I noticed survives server reboots in my local testing), maybe it would help if you could teleport me to lumbridge? Only suggestion I can think of, but it may be totally off base.

[Player Name]

I can reproduce this locally (or at least, something that gives the same behavior, no promise that the cause is the same) by editing my save to include "teleblock":{"ticksLeft":"99999999999999999"}}. This generates an exception when the game tries to parse the save:

java.lang.NumberFormatException: For input string: "99999999999999999"
at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
at java.base/java.lang.Integer.parseInt(Integer.java:665)
at java.base/java.lang.Integer.parseInt(Integer.java:781)
at core.game.system.timer.PersistTimer.parse(PersistTimer.kt:17)
at core.game.system.timer.TimerManager.parseTimers(TimerManager.kt:71)
at core.game.node.entity.player.info.login.PlayerSaveParser.parseCore(PlayerSaveParser.kt:348)
at core.game.node.entity.player.info.login.PlayerSaveParser.parse(PlayerSaveParser.kt:56)
at core.game.node.entity.player.info.login.PlayerParser.parse(PlayerParser.java:25)
at core.game.node.entity.player.info.login.LoginParser.initialize(LoginParser.kt:27)
at core.net.packet.in.Login.proceedWithAcceptableLogin(Login.kt:165)
at core.net.packet.in.Login.proceedWith(Login.kt:147)
at core.net.event.LoginReadEvent.read(LoginReadEvent.kt:36)
at core.net.IoReadEvent.run(IoReadEvent.java:45)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)
java.lang.IllegalStateException: Failed parsing save for: Player Name
at core.game.node.entity.player.info.login.LoginParser.initialize(LoginParser.kt:28)
at core.net.packet.in.Login.proceedWithAcceptableLogin(Login.kt:165)
at core.net.packet.in.Login.proceedWith(Login.kt:147)
at core.net.event.LoginReadEvent.read(LoginReadEvent.kt:36)
at core.net.IoReadEvent.run(IoReadEvent.java:45)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)
[12:22:10]: [SystemLogger] [ MS] player_name -(WLD)> 1
[12:22:10]: [SystemLogger] [ MS] player_name -> RQ CONTACT INFO
[12:22:10]: [SystemLogger] [ MS] player_name <- SND CONTACT INFO

Also tried manipulating the deep wildy threat-time-remaining variable in the same way, but that does not seem to be a factor - I can login with that set to the same ridiculous value.

It's possible that I got a revenant spawn from the threat system right as I logged out, and for all I know this hypothetical rev tbed me right as the game was logging me out? And I believe there were indications that the visual desyncs, which I was suffering from at the time, interacted with the timer system. Maybe this is the answer?

[Ceikry]

the teleblock applied by revs doesn't use a ridiculous value.

[Ceikry]

Apologies for the delay, been preoccupied with a lot of fires lately. I'm starting to take a look at this directly using your save now, and I'll provide you with any updates.

[ryannathans]

try now, should be fixed (cause was related to logging out after being frozen, unrelated to teleblocking)