Labyrinth Ladder Times seem to be acting strange after 2.2.2c

It happened to me again today.

My best PHC merc lab time was ~5:05 according to my timer. Ladder says 4:09. Uh thanks...?

Fortunately I would have been #1 anyway (although GuileFamilyMan is probably not trying very hard anymore, and/or may have had his time screwed up too... who knows!)

EDIT: hey here's another suspicious issue that may or may not be related - the remove-only prize stash tab that my merciless jewel came in is just called "(remove-only)". It doesn't have the date and time listed as usual. See screenshot below. You can also see that the other 2 jewels I won for normal and cruel today (woohoo!) have the correct tab names.

.

It seems like it happened to me now. I don't use a timer (either), but todays cruel layout is fairly long and it does not feel correct.

No good insight about the bug though I'm afraid:
I did a ~12 min exploration run to get to know the layout, as there is no map on reddit/poelab today.
Started a new run right away. It didn't went as smooth as I wanted so I portaled out a good third into the run.
Again new run right away. Went fine, but not remarkably fast or lucky from what I can say with that little layout experience. That run went up as 3:31 though, so basically the bug happened right away.
I did another run, now with my phone's stopwatch running, to get an idea what time I actually ran. However, that run crashed in the third (or so) zone, with a tileset error from what I recall.

Today I am also playing on London, which is one of the best and most stable servers for me. Frankfurt is the other option, but there seem to be ping spikes more frequent, so I rather use London.
The last few days I had Amsterdam still selected because I played from out of home and I forgot to switch back, because the difference is rather minor. So the switch to London might be important or a pure coincidence.


Edit: My reward stash tab did not have the naming issue that Fightgarr reported above.

"

aRTy42 wrote:

It seems like it happened to me now. I don't use a timer (either), but todays cruel layout is fairly long and it does not feel correct.

No good insight about the bug though I'm afraid:
I did a ~12 min exploration run to get to know the layout, as there is no map on reddit/poelab today.
Started a new run right away. It didn't went as smooth as I wanted so I portaled out a good third into the run.
Again new run right away. Went fine, but not remarkably fast or lucky from what I can say with that little layout experience. That run went up as 3:31 though, so basically the bug happened right away.
I did another run, now with my phone's stopwatch running, to get an idea what time I actually ran. However, that run crashed in the third (or so) zone, with a tileset error from what I recall.

Today I am also playing on London, which is one of the best and most stable servers for me. Frankfurt is the other option, but there seem to be ping spikes more frequent, so I rather use London.
The last few days I had Amsterdam still selected because I played from out of home and I forgot to switch back, because the difference is rather minor. So the switch to London might be important or a pure coincidence.

i feel like u might be right - i tried to catch up with u but that time is just insane with this layout

.

And again. 1:02. What.

"

aRTy42 wrote:

And again. 1:02. What.

YOOO nice time bro! LOL

As another example, noemberday's #1 HC merciless time today seems to have been shortened by around a minute as well (based on a brief conversation I had with him in-game; he times his runs too). Maybe this run happened at around the same time as aRTy42's bugged SC Cruel run?

This issue completely ruins the integrity of lab racing. I'd hate to see our upcoming UBER lab runs get affected.

Let's keep bumping this thread with examples / other info until we hear from GGG!

"

aRTy42 wrote:

And again. 1:02. What.

I wonder when will we see 0:01 ... this is gonna be hillarious when 4th lab comes

Just did a normal lab run in hardcore (about 2:20AM Eastern)

My listed time (currently #1) is about 1 minute too fast (4:12, my timer said 5:XX)

None of my other runs today (tons of merciless and a few cruel labs) had any timing issues. Just this one.

Nevermind.