BHVR Kill Switches The Flashlights But, Not Merciless Storm?

The scars from bugged Merciless Storm run deep...

One bug hold the game hostage, another don't. Think about it, Killswitch is only for majorly egregious bugs that stop the game from functioning. old Eruption, merciless storm and Skull merchant 3geners dont even do that.

Why does everything and anything have to become a “Us vs Them” argument or debate?

The MS bug was damn annoying but wasn’t game breaking like the flashlight + locker is. Wesker and Dredge got actual game breaking bugs recently and both got killswitched within a day. Of course they should take better action against bugs such as the MS one (check how Blast mine is still there even though currently can make you invisible btw), but why do people have to get catty and sassy over this.

Looks like devs can’t ever really win. If they don’t take action people complain, if they take action they complain as well.

It was an annoying af bug but was nowhere near this one that can prevent people from getting hit at all. People would just stay in lockers because they can’t be hit there and wait for the killer to leave the game because they just can’t do anything about it if survivors refuse to finish the gens. It’s just nowhere close for comparison, and we all should be happy and glad they took action as fast as they did with Dredge and Wesker months ago.

Merciless Storm was in fact killswitched, and I know because I used it in one of my builds. The thing is, they returned it to the game thinking the bug was solved when it wasn't for some reason.

If you find fun in pitting the playerbase against each other it’s quite odd behaviour to say the least. Sorry to break it to you but are not better than the people you complain about and you are so wrong, and it’s been said here that game breaking bugs have been rapidly kill switched for killers too e.g. Dredge and Wesker going invisible.

Except that's not the case and what has been brought up a few times in this topic proves it. Don't try to create a false narrative because you want something to blame on your lack of skill and BHVR not balancing the game in the way you think it should be.

1, that wasn't what I was talking about. I was talking about finishing FAST vault and still being hittable (which is not intended - this should be the main difference between mid and fast vault) - also if they indeed reverted it, people would not complain. But they reintroduced buggy behavior AND slowed fast vault to the point that there is barely any difference with mid vault (and going for fast vault is worse then accepting mids)

2, That would be true if you didn't already get prompt (because you are close enough) without moving an inch and the prompt suddenly disappearing on it's own. But as this is the case - I call it a bug that devs ignore - because it's apparently not a priority (same as vaults)

At least we can agree on some things.

And yes - this is the case right now. There's a video by someone (sorry, I can't remember who tried it) where survivor fast vaulted and waited on a spot for a few seconds (to make sure no lags are present) and still got hit.

I am also of opinion to make lags not favor lagging-person, but instead split the difference (meaning let server "hold world state" and let server decide what is and what isn't a hit). That's just mi opinion though.

But I will grant u one thing back - patch before last patch vaults were indeed broken and it was unfair towards killers

nurse an wesker have been kill switched in the past

You know how and why this is a lie because I already explained it to you in another post. Lag affects for better or worst every single player in the game in many ways, including not getting hits that they should have get in the case of survivors.

The funny thing is lag does affect certain Killers, and they are among the most complained about poor QoL experiences. Singularity, Doctor, and Ghostface all utilize 'Survivor' lag, aka it disfavors the user, or in this case is a rare example of favoring the Survivor over the Killer. So many times you get revealed through a wall as Ghostface, or the Biopod tag lock-on is barely broken, or shock them only for them to drop the pallet or vault, and that was lag. (I love Ghosty and Sing, but Doc is unplayable garbage to me as I hate the Survivor being laggy giving them an advantage that often.)

As far as I am aware, the only time lag disfavors the Killer in normal matches, is pallet stuns. In that case, the laggier person gets hit (with the attack or the pallet stun) because it is the only place with validation implemented. I would recommend implementing that same level of validation to corners, where the server says the laggier person loses, but not open spaces.

Edit: I just realized this latency tangent I responded to has nothing to do with the topic, so I won't respond back if you respond to me to avoid going further off topic, but feel free to respond regardless.

When I said that? But I have to say, saying that a killer with high ping would give less reaction to a survivor when in any case what would do is make the killer whiff attacks that should have hit is a little misleading.

Also, some examples of latency benefiting survivors:

• On generator grabs (and previously hook grabs). The killer see the survivor still doing the gen, go for the grab, the grab animation start to play but the server receive the info that the survivor let go the gen and the grab animation stop, leaving the killer just stand there or in the best case doing a quick attack.
• On pallets. Even when they get obviously hit they can still drop the pallet in the same instant. And that is if they get hit, as sometimes you see how they are eating your machete but doesn't even get hit at all.
• On getting hits. Like I said, there are times when you have obviously hit someone and either left unharmed or the game does a rollback because he used some perk. The perfect example of this are the times when you do a hit, hear a death scream, but you get DHd instead of the survivor going down.

Again, lag affects everybody, sometimes for better and sometimes for worst. It never is all benefit for someone, none for the others. And again-again, you know all this because we talked about it in extent in another post. So, who is lying here?

Well, I have to say, playing with high ping is without any doubt a huge advantage for the killer. Did you see how many hits I'm able to land while everybody is just playing without problems?

And that poor Jake, he didn't had any chance to react! It's so OP having lag in a game with a client-server architecture! Totally worth it. Who don't want to play like this?

And now talking seriously, it really surprised me that most of the match was playing fine. The game should have the hell out of good lag compensation. For reference, the lowest connection I had seen right now is 100 Mb (Megabit) per second... that is 12500 KB (KiloByte) per second, and I'm playing there at 6 KB/s. So, another proof that your internet speed has nothing to do with being lagged nowadays.

Dude, two Doritos ago you didn't even know what lag compensation was and that the game worked in a dedicated server infrastructure now. And now you are an expert in gaming networking?

My information was getting to the server, but late. That's why I could hit and even grab Jake from the gen. I simulated high latency by bottle necking the packets, so the game send them later than it would normally do. The upload was more affected than the download, so that's why I could see everybody playing fine but the others don't even saw me where I was.

There are only two instances where there was packet loss (marked by the two diamonds icon besides the high latency one), but the rest of the match I was literally lagging, ergo, high latency.

EDIT: Well, it seems that having an high ping is so not any advantage for survivors in any situation that now people are lag switching to literally speed hack somehow.

But keep trying to defend your asinine claim that latency is "killer sided".

"How does getting packet in wrong timing allow you to sprint for a long time" Simple: The Cheryl in the video is getting extreme high latency by lag switching to exploit the lag compensation and make the server don't realize the Sprint Burst or the bonus speed on hit should have ended long ago (that's why it only works when he hit her or uses Sprint Burst). But whatever it is the case or not, it is still lag / high latency's fault (check 2:48. She literally get placed in the wrong place and "phased" through a wall because she is lagging like hell) and what it is shown in the video could happen even if not intentionally and for a short time with a latency spike, just as the rollback can place you somewhere you don't even were before as happens in my video. Also, I don't think you really know how a lag switch works, as that Cheryl is without any doubt lag switching.

And for more proof of this being "weaponized high latency", even if we get back to Counter Strike:

And I know that you had become a networking guru in a couples of days, but before you hang the title on the wall you should have a look at what a buffer in programming is. More specific in this case, a packet buffer:

The packets don't get lost just because your bandwidth isn't enough (most of the time), they get buffered to be sent as soon as they can. That's why, again, even if it is seconds later the info was getting to the server of the game and that Jake got hurt. This and yet again, when there is packet loss in the game it shows an icon, and as you can check, there is only two instances where that icon shows.

In short, the only one that is trying to gaslight people in believe that the intrinsic nature of latency in DbD is killer sided is you. I never said that what you described didn't ever happen, but that your claim that having lag never benefits survivor or punish killers is ridiculous (because it is).

1, I have official education in the subject. Stop with your condescending comments. It's true I didn't specialize in games specifically, but I even have knowledge in this domain (alas I admit it's dated).

2, Also you are wrong. She was clearly turning from left to right which means packets were arriving. If we are talking selectively letting some packets go thru (go left/right) and some others (end of sprint burst) which if this even could work means badly programmed actions (how could server allow sprint to move you so far? Server itself should deny this on it's end - but that's a bit different topic). This is clearly just and only cheating.

3, if you are such a guru and know everything about buffering then tell me what happens when buffer gets full... Maybe perhaps it "overflows" and some packets get dropped? That's exactly what I wrote in last message. Let's stop w being condescending now