http://dbd.game/killswitch
Any possibility of BHVR being able to recognise the difference between a DC and crashing?
I love DBD, been playing it for 6+ years. My currently laptop is getting old therefore sometimes has problems processing the game so it tends to crash fairly often now but I can't afford anything to replace it just yet. I was wondering if anyone knows of the possibility of BHVR implementing a system to recognise the difference between someone intentionally disconnecting to go next in game, and someone's game crashing? As I understand the penalties are there to deter players from DCing often but its annoying when its not intentional and I end up with 15min + penalties and my SWF has to wait for that to be over before we can go into another match.
Answers
-
But the reason is irrelevent? You left the game for whatever reason mid way and ruined the match for others. Crashing isnt any more excusable than DCing, you start adding exceptions and you open it up to being abused. If your problem is your hardware then you need to sort it yourself, you're responsible for your own local problems, be they hardware, software, IP etc etc.
0 -
In addition to what @Shinkiro said above, they also treat any leaving a trial for any reason all the same because otherwise it would be abusable. Players could dashboard their game (or the PC equivalent) or pull some wires.
1 -
It's a nice thought, but people would absolutely find ways to force a crash.
It's like back before stable broadband connections became the assumed norm they are today, and a lot more people were on shakier connections. Quite a few games tried to be lenient by not tracking disconnects as a loss, and instead having a seperate DC percentage stat. It was quite common to run into players with insane win/loss ratios like 78-2, and something like a 68% DC ratio. You just immediately knew the only way you'd see the end of that match is if you lose, as if you start winning they'd DC without hesitation.
I do disagree with the new system where the penalty doesn't start ticking down until you start to queue again though. That actually disproportionately impacts people that just crashed, as even if they're done for the day after that they have to re-launch the game and start a queue just to not have to wait it out the next time they want to play.
Someone that genuinely ragequitted can just immediately hit re-queue no matter if they're planning to play more or not. That was a bad change, it's perfectly fine that the penalty starts ticking down immediately like it used to, habitual disconnectors will still rack up a hefty penalty and they're the ones that should be the primary target anyway.
1 -
My hardware can handle the game fine but I am getting frequent crashes and I am seeing a lot of people disconnect with no indicators of rage quitting.
I think the code is buggy right now, they even kill switched artist because of majority of her games crashing I heard.
If the increase in crashing is due to bad code, Behaviour should look at lessening the penalty, or at least have some basic analytics to see that person x hasn't rage quit a game for 1 month straight and slowly introduce the disconnection penalty in for people with good previous behaviours.
That way gamers who are having issues have a little more leeway, additionally we get replaced by bots now… I wouldn't say it ruins the game completely, I've had bots play better than the people that disconnected :D
0