Why Executioner cage loud notification was considered as issue in bug fix?
I don’t know is it even possible to get a respond from devs, but… Why exactly this, when this feature was implemented many years ago and was consistently working? And no one complained on this, because currently this killer having probably the best anti camp in this game and also trigger base kit BT?
When he obviously has actual issues, like aura reveal/killer instinct showcase after uncage, as well as inconsistent logic of cage send, when instead of actual further point it sends to the closest corner, why exactly this was considered as issue?
Answers
-
The same way plague being stunned by DS or head on deactivating her power was a "bug" NEVERMIND the fact she was in the game for what 4 years at that point. So take your pick i guess on whether that means the dev team is so slow that a fix like that takes 4 years to happen. Or they just dont label stuff in the right category.
5 -
I think its missleading.
Often you could hear his Cage Sound while nobody was caged at all.
-1 -
I played a match. You don’t really get notifications anymore. The sound of cage can happen in cases of when killer is too close to already existing one and it transfer position
0 -
I just want to get answer. I get why it was implemented in anti tunnel ptb. Here? It’s just a picky thing. And his actual issues wasn’t fixed. I mean, bug on Lerry is still a thing. Random trail of torments and even invisible one as well. I just want reasonable clarification and that they will address his actual issues as well. Maybe some info compensation in his base kit
-2 -
In all fairness, it was a bug. It's a bug that's existed for a year and a half, maybe two years at this point, but I distinctly remember it not being a thing on his release. I feel like people have gotten used to it being there given how long it's existed but it was a bug. There's many instances where you can argue shadow nerf over bugfix - like Plague pointed out earlier in this thread - but I don't think this applies
-2 -
In all fairness as well. A bug should not be left in for so long people get used to it being a part of the power i guess. That was the reason for the blight drama. He had a bug for so long that it basically became part of the killer itself. Then obviously when its removed a lot of people didnt like it. Quake kinda had this with rocket jumping which was not a intended mechanic. Then it went into tf2 as a offical thing. If a bug exists for so long the players get used to it then it should feel more like a nerf then a bugfix. Especially to those who main the character.
-1 -
Do really? Because I’ve seen this feature on videos that was 5 years ago. The same year of his release
And even in case it was a bug - why it was so consistent? While he has other bugs, more inconsistent, like literally showing aura of survivors after uncaging or long instinct/invisible trails that actually breaking fairness of his power. This is something that appeared recently and is really frustrated.
I don’t want to exploit these bugs now just to get basic knowledge about what happening on map, while other killers have it by default. Considering that cage can be directly send to other places, it can be 50/50, and happen literally to the position of other teammate who working on important gens. He already got BT, stronger anti camp, and he sacrifice cancelling of survivors perks by being unable to use a lot of meta as well. Be doesn't have mobility or map control tools.
As his main, I don't ask to remove BT or sth. Just return feature that is really important for gameplay and was here for 5 years. People who consciously looking for tunnel will spend their time to find a cage and proxycamp anyway. I simply can't allow chase in other corner of the map because can’t be sure cage was sent in area I don't need to control, and two survivors have to be there until some heal
3 -
You'll have to forgive my lack of evidence, I don't have any footage and can only speak from my own gameplay, but I've played him quite a lot and have done consistently since his release and I distinctly remember a period - after they fixed the first time - where it was fine, and then it broke again, and now they've fixed it again. I can't give you a timeframe, my memory is shot, so all I have is my word and reputation.
I agree, honestly, they should at least put it somewhere higher in the patch notes, because people who haven't been around for too long won't know that it's unintended and think it's a shadownerf. But this one specifically doesn't feel like a nerf - to me, anyway - because I knew it was a bug that would eventually be fixed. Time and time again the message "cages are not hooks" were said, and they weren't intended to give hook perks or noise notifications on the PTB, but likewise if someone's started playing in the last 2 years then they won't know this.
It wasn't handled amazingly, agreed, but there was a period where it was fixed and working as intended. That I am sure of.
-1 -
There are long standing bugs for many elements in this game. For any of them to be fixed is a miracle someone did something besides making new cosmetics.
It's not uncommon for the Devs to say one thing years ago and say the exact opposite today. A bug yesterday is a feature today. An affect written in plan English is said to be a bug and is "fixed". This is what you can expect from DBD.
2 -
You'll have to forgive my lack of evidence, I don't have any footage and can only speak from my
owngameplay, but I've played him quite a lot and have done consistently since his release and I distinctly remember a period - after they fixed the first time - where it was fine, and then it broke again, and now they've fixed it again. I can't give you a timeframe, my memory is shot, so all I have is my word and reputation.
As much as I main him, and as much I watched for videos from his mains… If we call “fixing” a feature that was considered as change from his release, than it was returned back, and existed for many years, is it an actual issue? Especially when they already adjusted the problem that uncaged survivor can be instadown.
Devs can leave it as it is ofc. People will just use his actual power less again. This killer already having an issue many people were simply using m2 for zoning rather than hits, and were using torment just for Mori, and now they doing this again.
I edited my previous comment why I find this as an issue. So, just hope devs would try to read this at least :/ I already got used that they are consistently making unnoticeable changes to his power that greatly affecting gameplay, yet just to wait another month for this to be returned back. When his actual bugs are left barely fixed
0 -
I remember how they flighted with his flicks. That's just disappointing that they do like this because can’t make it stable
Still don't understand why we call a bug a logic thing in the game, especially when it exist in game longer than “fixed version”. Even in case with Plague stun - it was rational and consistent. Sometimes the only thing you need is just stop calling mechanic changes a bug fix, I assume
1 -
Since we are adding 30s of endurance and elusive, can we return loud notifications? Or at least get some clarifications now why it even was an issue
0 -
It's the same excuse they used in Nick Cage's patch to try and push another handheld for survs.
"Fixed a bug that prevented killers to look down after an M1".
A SEVEN YEARS BUG?! ARE YOU KIDDING ME?!
Yes, this happened and was in Nick's PTB. When you M1 a surv the camera of the killer went all the way down similar to Nurse's fatigue and they even said this was suppose to give survs better chances of escaping a chase.
The only reason it didn't got through was because it was a huge accessibility issue (motion sickness).1 -
I assume they will ignore it and it continue to be like this forever, because this killer don’t have high pickrate anyway :/
0 -
Probably. :(
0 -
Less people see him, less people actually can dodge him in my lobbies. More I see boring shift w + predrop and stomp matches
I started to play him less after finishing my challenge, because people rarely can handle this killer in lobby, THAT much my style for them is confusing. People surprised killer can use m2 not for zoning only or using cages for info and forcing change of position. And devs now gutted the way how I played games on him before, removing noticicafions. Am I really supposed to use cages now only for dodging DS or for Mori…
0 -
Seems the way.
He is the only killer I don't bring a Ebony Mori. I just make survs get Torment so I can mori them after the 2nd hook.
If I send them to the cage there's a risk I'll not be able to reapply Torment to them again, another surv will be cleansed of this status if they rescue the caged surv (which in this scenario make two survs that are not Tormented anymore) and now I don't get a notification when they are rescued from them.0 -
It’s actually really nice to use cages for controlling zones. Or for saving time if you don't have it for hook. After survivor uncage, I get info about position of two survivors at least. Even can understand if it happened close to the gen, that person was actively working on it. And since the logic of send is further point, I can be sure that at least one person have to leave (if all of them are close to me), and go really far far away to rescue, so I can save time
I’m not tunneling at last possible moment, and I know many spawns so this risky 50/50 now haven't done anything for me in terms of can I tunnel survivor or not. But that fact they killed my fair play way of using cages… wow, that is really telling me a lot about BHVR
0 -
Yeah.
The lacking of information is the real issue here for sure.
Pretty similar to the discarded changes to tunnel from last PTB.0 -
it has been a but for 7+ years .
source : trust me bro0 -
If being for real, invisible trails and bug on Lerry indeed was a thing for that long time
I reported for aura reveal bug weeks ago, no reaction as well
0
