I know it sucks when the game crashes but it’s worth to make it imposible to rejoin to stop stupid penance cheezers to alt+f4 out of games
Or maybe better change the penance so it resets if u quit out so it dosen’t incentives bad players cheezing the game.
2 Likes
I do agree and have been ripped to pieces by the forums for even suggesting this. The solution that will work is replacing the bot in the same state as the player like V2.
1 Like
I full heartedly disagree - abuse by some doesn’t justify to punish all who have connectivity issues for whatever reason.
11 Likes
There’s no need to do any further “punishing” than just remembering the state the player was in when he loads back in. If he DCs while downed, he will load back in downed. If he leaves the game while dogged alone, he’ll load back in while dogged alone. The game explicitly tracks stuff like distance to team and uses it to move bots around, it wouldn’t be hard to implement something like this at all.
At the very least this would stop people from exploiting and having “infinite lives” in a mission. They would still alt+f4 out to preserve their penance progress, but it’s atleast one half of the issue solved. The solution to the penance issue imo is to not design penances like that in the first place. It’s totally meaningless either way: if it lets you quit out then you can just cheese it. If it doesn’t let you quit out then you’ll have it ruined by DCs and crashes. The solution would be to not implement penances like this in the first place, they’re always meaningless no matter what.
1 Like
Agree, This is what’s wrong with the game.
Worst Idea I’ve seen in a while. Reconnecting is great feature we shouldn’t lose just cause of a loophole.
6 Likes
From previous beaten to death topics, we know that the vocal majority do not like this idea, a solution was found, I’m curious your perspective though. What would be your solution? @Harridas
I think the same bot system as V2 would work, while allowing for the rejoins to continue.
1 Like
Was on my phone when I wrote that so I didn’t elaborate much at that moment.
In terms of a solution I think it’d make sense for a disconnected player to rejoin in the same status they were in when they lost connection, (not the same place, just whether or not they were downed or disabled) like what @Kambrin said. Punishing players in any additional ways is going to harm the experience for regular players. Like when my internet suddenly died on the 5th Maelstrom mission even though we were playing perfectly, I’d be unhappy if that progress were to get wiped just because of that. And it’d be even worse for my american friends who get randomly disconnected far far more often than I have.
1 Like
Disconects sucks but not that frequent.
Dopy players altf4 because they can’t survive or wanna abuse some infinitive lives are worse.
Like u could keep the feature on lower levels or non aurics/maelstroms.
Or if you reconect in Auric-T5/maelstroms you need to be rescued as a downed state in the next area
Or just reset the counter for penances for the "survivor"ones if u disconect to not incentives this behavior.
They are not that hard to get legit by just playing the game
1 Like
Yea, I think the alt+f4 experience has lowered the skill ceiling of a lot of players, granted it is a mechanic of the game now so how can you blame them?
Technically this should be possible. When you press Alt+F4 is Windows sends a termination signal to the current process. Afailk this process then can be handled by the application, before Windows just forces it to close. So this should not be a problem for Fatshark to actuall introduce their own code/instructions before the application is closed, for example prevent the client from abusing it.
One thing to consider is that, whilst the game stability has improved since the launch, people still crash. I’m no a pro coder, but I would imagine server should be still able to recognise the difference between a client crash and a handled process termination.
1 Like
The game can tell the difference between a disconnect or crash and an ‘end process’ command from the computer. Banning someone from reconnecting to a session they alt-f4’d out of wouldn’t affect people who disconnect due to network issues or actual crashes.
1 Like
I agree with the premise but disagree with the execution. I think a good middle ground would be requiring rejoiners to be rescued. I really dislike the people who abuse it to escape nets, ledges etc
I think this topic has been chatted about already (Alt f4 - #26 by Jonboy).
I don’t have a golden bullet solution. But I can imagine running in to a fight with a bot who then just suddenly drops to the ground and needs rescuing because the player reconnected. Bots are admittedly pretty bad and nobody relies on them to keep them alive, but that experience would just be jarring for those NOT doing the alt-f4 thing. Backs to the wall sharing aggro, and then suddenly it’s all on you.
Better all round if the game could capture alt-f4 and record it so that the round can’t count for progress. I’m pretty sure the 10-games-no-down malice+ steam unlock (“Flawless Execution”) used to discount a round unless you got all the way through, start to finish, no outs so I’m not sure what’s up with this newer one.
1 Like
No, I disagree. I crash a lot, and do not care about cheezers
6 Likes
I absolutely cannot accept that. If someone doesn’t want to or cannot play anymore during a mission they should be completely free to do so.
Also a very bad idea, it’s mostly going to end up punishing people who don’t have a perfect connection to amazon’s shitty servers which is a lot of people and punish other players who may need to reconnect for other valid reasons such as a player getting stuck somewhere or needing to restart for performance reasons, etc…
I believe the idea of the game remembering the player’s status upon rejoining is the best way to go about it, it doesn’t stop people from exploiting reconnects but more importantly doesn’t harm the experience of legitimate players.
You cannot actually successfully do this. The logical conclusion of trying to differentiate is always that players will just pull the plug. A game can’t differentiate a pull plug from an “authentic” internet outage.
All changes in this direction would really do nothing except make those players plug pull instead of alt+f4ing. It doesn’t really solve the problem.
There’s basically two solutions in the end. One is what some Souls games implement: if you DC from pvp enough, be it pull plugs, alt+f4, closing the console, lightning striking your PC, whatever, it doesn’t differentiate: you get online banned after a couple times. You can unban yourself in some of the games, in Dark Souls 2 you had like an item once per playthrough that could do this iirc. Probably not a good fit here considering how much this game crashes and how bad the servers are compared to souls games.
The other solution would be not implementing penances that encourage this behavior. That’s literally it.
1 Like
The person alt+f4ing already created a jarring experience for the players because suddenly the downed teammate who needs help is replaced by a happy alive bot.
Arguably this sort of change would CUT DOWN on those jarring experiences since they now wouldn’t alt+f4 to begin with (since it wouldn’t revive them for free)
No, I don’t think it’s the same.
I not talking about the constant cycling of players here.
Having someone pop up alive when they weren’t gives you an extra life, always welcome, as it were. The opposite just leaves you in the creek.
Can you imagine picking up a bot in a clutch, then that bot dropping back down. Compare that to the opposite, you’re on the deck and a bot pops up to revive.
Don’t get me wrong. The alt f4 mechanic sure is bust. But the two opposites I don’t think are the same.
Alt F4 is way too slow.
use this chea… eehhh MOD instead:
This allows you to bind a key to instantly load back into your current lobby, no game restart through multiple loading screens required, only the mission loading. Way faster and efficient. Dont bother trying to use this on actual disconnects tho, it only works while youre still inside the current match.
Honestly not even as good as Wobins freaking cheat mod that shows all specials and elites constantly. Dont need to reload and reset your big D damage numbers from the scoreboard if you can see every special in the game coming a mile away the millisecond they spawn
Use this!:
Always remember fatsharks modding policy for DT is EXPLOITS EXPLOITS EXPLOITS but dont allow people to solo conveniently that would be crazy.
Special shoutout again to that dog Wobin for single handedly making every handicapped person able to solo the entire game. The true champion for accessibility that we need