People Alt-F4ing to avoid being killed while downed

I have noticed a trend of people disconnecting when they are downed and no one can pick them up. This seems to be a bit of an exploit if your load time is fast enough. To be fair I disconnect (unwillingly) more often then I’d like due to my connection so removing the mechanic would be a poor choice.

To give a specific example and Orgyn player was not Auric ready; (Not Managing hordes properly, Going down to like 3 enemies, jumping while trying to dodge etc.) They would often go down out of position and instead of dying he would d/c and return in like 30 seconds due to a fast load time. This felt like they were exploiting a fast load time to compensate for their mistakes.

To give all context I have:

  1. Doing this does gives you a corrupted wound but prevents you from dying.
  2. They were seemingly not lagging out as he was playing without issue up until their lack of skill caught up to them.
  3. If the bot dies while the player is d/c’d they will still spawn with the team.
  4. I think they took extra wounds so they could do this more often as taking extra wounds in Auric Damnation is somewhat pointless to just having more hp or toughness. (Conjecture)

TLDR: This Exploit (?) makes the games that its in feel cheap.

1 Like

Yeah, it s…cks to see some players systematically do it.
And the trend has become something that very much goes against the whole coop team accomplishment Darktide pushes for.

I have used it sometimes, as many players probably have but would very much not regret having an end to it considering how some players abuse it 100% of the time as soon as anything bad happens to them.

1 Like

Yeah. This ol’ topic.

Sounds like you ran into a particularly bad one. The fact they took extra wounds on an ogryn of all things.

Emperor help us.

The game can detect if you Alt f4. Could just lock them out of rejoining. I recall this being a thing in some other games though I don’t remember which ones. Though, I’ve had to crash the game with task manager at times because of mem leaks not auto crashing the game themselves, but that’s extremely rare.

:person_shrugging:

Gives the team a better chance when there’s a bot in my place when I cockup so badly it’s embarrassing so I rage quit and try again in 2 hours…

Yeah, it’s a total sh*tter move. People will claim that they need alt+f4 so they can rejoin a run after getting stuck out of bounds or whatever, but that’s so incredibly rare compared to people using it to cheat that it’s almost a non-argument.

I believe the complaint is not that people are ragequitting, but that forcing the shut down somehow makes the game think they lost connection and allows them to rejoin auto-revived.

1 Like

Unfortunately I’ve seen this bug reported months and months ago. There exist infact mods that let you DC and reconnect really quickly even to abuse this. Additionally I’ve seen xbox players reconnect very quickly, I think their load times make it very easy to abuse also. No fix as of yet.
Really sours the experience when a game is intensely difficult and a teammate decides to exploit on your behalf and be unkillable.

We’ll just have normalize everyone else on the team wiping as quickly as possible, whenever someone disconnects after going down, so there isn’t a mission for them to join back into. :smiling_imp:

They are only fooling themselves by being reliant on cheap tactics like that.

It’s not a bug.

This is the intended function… it’s a QoL feature that’s abused…

The only suggestion I’d make to fix it is if the same person reconnects, they should still be downed or already captured. Period.

Other folks connecting to fill the spot should function as-is.

I’ll say the only time I was glad this happened was when I was doing a no player deaths weekly, and our vet got netted right before a dropdown.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.