same

same too

same here, had to quit the run, was completely locked

Yep, same here. Couldn't find a fix either

Good to know, I'll wait for the patch then :).

Thanks for the update!

Guy i find a way to fix this (Sorry for my bad English.)
้here what i found

Step 1: Choose a melee weapon previously patch spear, Bat, hammer. Importantly, do not take a knife.(I don't know how much is related, just a little or a lot.)

Step 2: In the Main Room, the objective is to complete two UPLINK Terminals. Start with the first one, for example, Terminal_151, and then proceed to Terminal_771.
Everyone must avoid going to the second Terminal. If anyone in the party goes to the second Terminal and trigger a IP for that is over , it's recommended to exit and start new round.

Step 3: After completing the first Terminal, if the enemies spawns stops, proceed to the second one.

Step 4: After you done second Terminal. The Exit will show on a map then GTFO Because I'm lost. and my team died for that I had to replay the whole level one AGAIN.

Note: If the first round you fail , return to the save point after completing the first Terminal. Enemies will continue to spawn until the level is completed successfully. recommended to exit and start new round again

OR wait for the patch

GOOD LUCK

Originally posted by Community-Calle:

It’s a kniven issue, we are working on a patch to fix it.

story of your game
to be honest

Originally posted by spiken:

It’s a known issue, we are working on a patch to fix it.

Hello, Spiken.
Just out of curiosity, is this patch still on the way? Found the bug today with my friends, so we assume it hasn't been addressed yet. We've been taking our time moving through the game and plan to play for a very long time yet, and we were just wondering if this was still on the table or not.

Encountered this bug.
Source terminal 771, child terminal 124, completed all 5 codes successfully, but spawns keep coming.
Cannot initiate a second uplink, since first is "in progress".
Restarted from checkpoint, same issue keeps occurring.

I think this is objective bug
Something that happens everywhere
Usually caused by lobby shenanigans, most commonly by returning to lobby mid-drop or someone joining mid-drop.

Could also be uplink bug, checkpoint bug or all the bug lingo that floats around GTFO.
A full reset usually fixes things, and just in general never touch return to lobby if you can.

(I'll update this once I find some more info)

Originally posted by Fabricator Locum Gulyuk FerroTiC:

Encountered this bug.
Source terminal 771, child terminal 124, completed all 5 codes successfully, but spawns keep coming.
Cannot initiate a second uplink, since first is "in progress".
Restarted from checkpoint, same issue keeps occurring.

My team encountered this bug too on the first uplink. Someone was disconnected and rejoined the game just before the uplink , first try was good with the break between the 2 uplinks. We died --> checkpoint.
Then, after the first uplink the waves of ennemies never stopped coming, there was no end to it. We double checked the first uplink was finished and it was the case.

Hope it will get patched one day

Originally posted by The_Keyser:

Originally posted by Fabricator Locum Gulyuk FerroTiC:

Encountered this bug.
Source terminal 771, child terminal 124, completed all 5 codes successfully, but spawns keep coming.
Cannot initiate a second uplink, since first is "in progress".
Restarted from checkpoint, same issue keeps occurring.

My team encountered this bug too on the first uplink. Someone was disconnected and rejoined the game just before the uplink , first try was good with the break between the 2 uplinks. We died --> checkpoint.
Then, after the first uplink the waves of ennemies never stopped coming, there was no end to it. We double checked the first uplink was finished and it was the case.

Hope it will get patched one day

That's just checkpoints not resetting levels properly, something that happens with a lot of checkpoints.
The dc doesn't have anything to do with it.
Checkpoints are busted, and R8 is a bug fest.

For clarification of my previous post.
We did try R8C1 map one day before with 3 players and 1 bot. Nobody got disconnected or joined/rejoined later. We successfully completed uplink on both terminals (not sure we started primary or secondary first) and ran towards the exit. Unfortunately 1 bot got stuck somewhere on the map and we couldn't revive him before we were overwhelmed by the horde.
Next day we tried again. In a single run (no checkpoints restarts) we started one of the uplinks. After "completion" (terminal stated uplink complete...), we couldn't start second uplink, since terminal stated "previous uplink in progress". And waves kept coming.
So we intentionally wiped, redo the map from checkpoint and did the _same_ uplink very thoroughly (standing by the terminal, no moving away, monitor always on), Same issue again.

I am sure if we retried and did the terminals in opposite order, we wouldn't have encountered this bug.
But we will not restart the map again if we know there is a high chance this issue will occur.
I am slightly upset about this, if it has been a "known issue" for almost a year...

Originally posted by Fabricator Locum Gulyuk FerroTiC:

For clarification of my previous post.
We did try R8C1 map one day before with 3 players and 1 bot. Nobody got disconnected or joined/rejoined later. We successfully completed uplink on both terminals (not sure we started primary or secondary first) and ran towards the exit. Unfortunately 1 bot got stuck somewhere on the map and we couldn't revive him before we were overwhelmed by the horde.
Next day we tried again. In a single run (no checkpoints restarts) we started one of the uplinks. After "completion" (terminal stated uplink complete...), we couldn't start second uplink, since terminal stated "previous uplink in progress". And waves kept coming.
So we intentionally wiped, redo the map from checkpoint and did the _same_ uplink very thoroughly (standing by the terminal, no moving away, monitor always on), Same issue again.

I am sure if we retried and did the terminals in opposite order, we wouldn't have encountered this bug.
But we will not restart the map again if we know there is a high chance this issue will occur.
I am slightly upset about this, if it has been a "known issue" for almost a year...

Kick the bot, finish the level. instead of trying to revive.

If you want to avoid the uplink bug, do the overload and you don't have to do the uplinks at all.