One Survivor, 3 Decisive Strikes in a Row
So, I had a match as killer last night where I left the obsession until last (not by choice... it was a Camo-dette). After everybody else was downed, I saw them on BBQ & Chili and easily hunted them down, with them eventually eating dirt perhaps 10 yards or so from a hook. "Dr. Dribbles in the house," I thought. Well, the very moment I got them up on my shoulder... WHAM! Decisive Strike. Oooohkay then...? Bit odd, but let's roll with it.
So I chased them back down fairly easily. Figuring DS was now out of the way, I heaved them up and... WHAM! Second Decisive Strike. Ummm, WTH? I stood there flabbergasted for a moment, then began chasing them again. Knowing something was awry, I quickly caught up and laid them cold. In my book, this moment calls for letting the offender bleed out. So I walked with them as they crawled, still trying to process what happened. Did they update DS while I was at work and didn't know it or something? Time ticked away, a step forward to match the crawl. Blood. Corn. Claudette moaning (ugh, Claudette moaning...). Torture. Then, in the faint distance, I began to hear it... the sound of the hatch.
Oh, BS, c'mon now! So, hoping those multiple insta-DSs were just some sort of a glitch and, knowing this person would definitely make the hatch with bleed-out time to spare, I picked them up again and instantly tried to drop them with the ol' dribble. Nope... WHAM! Instant third Decisive Strike!
Well, somehow, some way, this goober ends up running off in the other direction of the hatch and up the tractor/plow where I whacked them down yet again before they could get over the ledge and jump on the cheater bail. They ended up bleeding out wandering aimlessly in a circle at my feet up there. Un-friggin-believable. Pretty stoked that I still got a 4K, but I almost feel sorry for how awful they were; you could definitely tell they needed hacks to be where they were.
So, afterwards in chat, I confronted them about the multiple insta-DSs. Below I'll attach the chat exchange. They knew they cheated, aren't even remotely scared of the devs about it as they mocked onwards with a "whacha' gonna' do about it?" attitude, and the worst part is after I took the screenshots of the chat and went to report it in-game... the client crashed. Well, I looked up the offender, found their SteamID64 as necessary and gathered information, went through the tedious DBD Support Center ticket, and now I get to sit and wonder if anything will ever come of it. Mostly because I know that without that in-game report, the ticket is basically null and void for hacking/cheating offenses (as I later found out by looking at the Game Rules & Report System post... ugh. Meh.). The cheaters in this game and pretty brazen at the moment, and from what I can gather -- unless they're chronic D/C'ers -- pretty much bulletproof, even on PC.
I've had some bad DS experiences in the past, but this one certainly took the cake (and smeared it all over its body and said, "Oooh, what a lovely tea party!").
Has anybody else faced a set of multiple instant DS occurrences before?
Comments
-
Oh, didn't you hear? DS is on a 30 second cooldown.
3 -
Wait wat FFS I have a hard enough time with looping ds people now they get as many as they want1
-
https://support.deadbydaylight.com/hc/en-us/requests/new
Click here, from the drop down click "Additional player report information".
Upload the video to YouTube under a private video and send them the link.
Try to include player account links, too.Please only do this if you're on PC, as the reporting currently doesn't work on console.
1 -
@Keene_Kills said:
So, I had a match as killer last night where I left the obsession until last (not by choice... it was a Camo-dette). After everybody else was downed, I saw them on BBQ & Chili and easily hunted them down, with them eventually eating dirt perhaps 10 yards or so from a hook. "Dr. Dribbles in the house," I thought. Well, the very moment I got them up on my shoulder... WHAM! Decisive Strike. Oooohkay then...? Bit odd, but let's roll with it.So I chased them back down fairly easily. Figuring DS was now out of the way, I heaved them up and... WHAM! Second Decisive Strike. Ummm, WTH? I stood there flabbergasted for a moment, then began chasing them again. Knowing something was awry, I quickly caught up and laid them cold. In my book, this moment calls for letting the offender bleed out. So I walked with them as they crawled, still trying to process what happened. Did they update DS while I was at work and didn't know it or something? Time ticked away, a step forward to match the crawl. Blood. Corn. Claudette moaning (ugh, Claudette moaning...). Torture. Then, in the faint distance, I began to hear it... the sound of the hatch.
Oh, BS, c'mon now! So, hoping those multiple insta-DSs were just some sort of a glitch and, knowing this person would definitely make the hatch with bleed-out time to spare, I picked them up again and instantly tried to drop them with the ol' dribble. Nope... WHAM! Instant third Decisive Strike!
Well, somehow, some way, this goober ends up running off in the other direction of the hatch and up the tractor/plow where I whacked them down yet again before they could get over the ledge and jump on the cheater bail. They ended up bleeding out wandering aimlessly in a circle at my feet up there. Un-friggin-believable. Pretty stoked that I still got a 4K, but I almost feel sorry for how awful they were; you could definitely tell they needed hacks to be where they were.
So, afterwards in chat, I confronted them about the multiple insta-DSs. Below I'll attach the chat exchange. They knew they cheated, aren't even remotely scared of the devs about it as they mocked onwards with a "whacha' gonna' do about it?" attitude, and the worst part is after I took the screenshots of the chat and went to report it in-game... the client crashed. Well, I looked up the offender, found their SteamID64 as necessary and gathered information, went through the tedious DBD Support Center ticket, and now I get to sit and wonder if anything will ever come of it. Mostly because I know that without that in-game report, the ticket is basically null and void for hacking/cheating offenses (as I later found out by looking at the Game Rules & Report System post... ugh. Meh.). The cheaters in this game and pretty brazen at the moment, and from what I can gather -- unless they're chronic D/C'ers -- pretty much bulletproof, even on PC.
I've had some bad DS experiences in the past, but this one certainly took the cake (and smeared it all over its body and said, "Oooh, what a lovely tea party!").
Has anybody else faced a set of multiple instant DS occurrences before?
The survivor has a point though, you cant expect much from the devs bud
I look at the hatch losing mechanic, the DS, SC rework. All have been scrapped and delayed indefinitely3 -
That's a great idea doing the video via YouTube link. Just added it to the report under additional information. We'll see if anything gets done about it... it and one from about 2 months ago still show "Open" with no new progress, so it seems most cheaters are home free. That D/C banning wave, though, now that's a priority, I guess
0 -
@Keene_Kills said:
That's a great idea doing the video via YouTube link. Just added it to the report under additional information. We'll see if anything gets done about it... it and one from about 2 months ago still show "Open" with no new progress, so it seems most cheaters are home free. That D/C banning wave, though, now that's a priority, I guessI'm sure they get a lot of reports a day, there was a hack you could do back in the day that disables window vaults for survivors, I reported the guy (with video proof) and he was banned within a week.
1
