BHVR would rather fix the NOED "bug" than fix the Jason Audio Issues
Basically title. On the PTB, NOED was changed to what it really should be: revealed upon the last gen being completed. They "fixed" this "bug" aka enough killers cried so they reverted the feature change. Meanwhile, for half of every match, the audio in the game is bugged and it's as if I stepped into a deafened Hag trap. Great work!
Comments
-
Wait they removed NOED reveal? that was such a healthy change 😑
5 -
That's what I'm saying!
2 -
Was NOED bugged? I thought it was always revealed.
2 -
Just curious - under what conditions are people allowed to ask for legit bugs to get fixed without being accused of “crying” about it?
9 -
It is a bug that it's hidden in end game. It's just lasted so long that people consider it a feature.
-10 -
Honestly that bug was the perfect rework for that goofy, embarrassing perk. L bugfix.
4 -
Considering that every other instance of the Exposed status warns the survivors, but NOED does not, it really makes zero sense.
That bug actually made NOED more fair to play against, since you knew it was in play, before the first survivor went down.3 -
Personally I'd like NOED reworked entirely. It's a cheese perk that rewards kills not earned, in my opinion.
5 -
I've been saying for years that that was how NOED should work. Status effects are there for a reason and the current design is a hangover from the days when the perk didn't apply Exposed at all. It used to just say you get put into dying state if you get hit.
3 -
Doesn't Devour hope only warn when you hit someone too or was that changed?
2 -
So its been bugged for the games entire lifespan???
1 -
Devour doesnt either
0 -
Correct.
-5 -
Right, Devour also does this.
Correct. But all other instances does give you the warning.
0 -
sooo its not really breaking any sort of trend then is it?
2 -
I mean you can argue the benefits of the change, but it was a bug so it's definitely for the best it got fixed. I think the game has enough bugs already without leaving new ones untouched, potentially causing more problems.
0 -
Though, unlike most bugs in the game, this one was actually pretty healthy
1 -
Okay, I have to ask. Where was it stated that the NOED bug was an intentional change and not a bug?
2 -
Is this guy trying to claim the new "tab" bug is something that has been in the game long time. Its literally new bug that only appeared after the patch.
Also the NOED being revealed when last gen is done was a bug. Its not listed as a change anywhere and it was quite fast marked as Under Investigation in the bug reports. In no point any dev/mod tried to claim it was working as designed as they will do that if something is intentional and is reported as bug. This bug also is not old it started happening in 9.6.2 as that is the first time someone reported the bug. NOED originally was only revealed after killer did normal M1 attack on a survivor after the totem was lit. You can go check tons of videos of it so no this bug was not in the game from the start.
PS if you have problem with the sound issue press ESC and it clears up after you go back to the match from that tab.
Post edited by Wezqu on3 -
Well its a hex and it should be strong, glass cannon made hard hitting perk that can be removed so I dont think its bad how it is so its appears on hud when someone is hit.
More what it needs is some requirement not so high but some atleast.
-1 -
So main post is gaslight, kinda makes sence because I dont remember noed to be showed immediatly after last gen is done.
-1 -
Glass cannon that doesn't reveal itself until the end of the game, most times when it's far too late to do anything about it and can easily secure a 1 or 2k depending on hook state distribution.
Do you see how that's a balancing issue?
-1 -
When did I say this bug wasn't new? I thought saying "JASON AUDIO ISSUES" would be your first and only clue needed to realize I'm talking about this patch which was present on the PTB. …You did play the PTB right? Or are you unaware of that data point from almost a month ago at this point?
-1 -
The same place where they put the info that surge makes you scream when it procs versus how it used to not before. Spoiler alert, they never made a patch note for it. This change was almost 4 years ago at this point. Still not a peep from the team anywhere.
Case in point, based on track record, even patch notes aren't good enough.
0 -
It reveals itself as perk states once its used on survivor same as devour and then it reveals itself.
Only change its needs is some requirement like get 3-4 hook stages so it isnt free compleatly.
0 -
So in your opinion any undocumented change is intentional and not a bug when you have one example where this is the case. Gotcha.
-1 -
No, what I am saying is I would like clarification from the devs since there are instances for both sides that make it indeterminate on whether or not it was an intentional feature or a bug without expressed disclosure from the development team.
-1 -
Sorry no. If a survivor is exposed, which happens when the last gen is powered, they should be alerted to that fact. Same goes for devour hope. Every other status effect is revealed to the survivor when it is applied to them. As a previous poster mentioned, this is a vestige from before exposed existed in the game.
These cheese "surprise" hexes really need to be lost to the sands of time for the sake of fairness.
0 -
It got reported as a bug it went the progress to get fixed even in the reports. It seems thats quite big validation that it was not intentional.
-1 -
For the majority of the games life, there were spots that survivors could go down and be literally impossible to pick up, but other survivors could heal them.
If you're going to imply favoritism when it comes to bug fixing, you need to think a bit more.
0 -
Its a hex and its up to devs.
If it gave itself away I would be for making aura for tomtem hidden till domeone gets hit by it and reduce aura reveal range of totem to like 16 meters because there would be enough time to deal with it or be prepared for it.
If you have something against devour I suggest get some help, that prrk works rarely and mostly gets you few downs but in like 1/2 of situations it gets cleansed before it does something and theres literary whole game time to deal with it so it should stay as it is (devour).
-1 -
I have no idea what you are saying in your first sentence.
-3 -
You are turning this into an us vs them when my original post was about a healthy balance change for a cheese perk getting priority in being reverted over a glaring gamebreaking issue with audio coming in and out every match. Please read more carefully next time.
-4 -
I am asking for the only 2 perks in the game that don't reveal themselves when applying the exposed status effect to act like every other perk and addon in the game.
And please for the love of everything good in this world, reread your message before you hit post.
-4 -
The NOED thing got reported and fixed as a bug. That validates it as not intended in the official bug reports.
0 -
Noed maybe for how cheap it is but devour?
There isnt such well done hex its strong and its meant to be, it has huge requirements and it can be destroyed/ taken away by survivors in seconds.Its a gamble perk ho all in or loose like it or not its well done perk even when its from all times and leave your love of god for yourself.
-1 -
Do you have a source?
-3 -
Both devour and noed need full reworks.
When did I say for the love of god? Please reread carefully.
-3 -
I think you know how to go check Betahub bug reports and use search function like anyone else.
-1 -
I'm not creating yet another account on a 3rd party site just to see if a bug report has been made for a feature. So no, I guarantee your assumption of "like anyone else" is basically just false since at most 10% of the people with a forum account have one there.
-3 -
Ok you do you.
0 -
Glad to know we are in agreement that data like that shouldn't be locked behind yet another barrier and should be available for the community to see, especially since the PTB is public access.
-2 -
I am not in agreement with you in anything really just saying that you can do what you want it will not effect my opinion of the matter at all.
-1 -
I don't understand? You said that they posted data on the bug, I said that it would be preferable to see the data without having to make an account. You agreed by saying you do you. Not really sure why you think we aren't in agreement after that… unless you don't know what you do you means?
-1 -
I am saying this last time I did not agree with you my comment was you stating that you did not want to do another account. Thats your choice and I am not in oblication to provide you anything and you are also not entitled to get what you want. I am done with this conversation as there is nothing here to talk about anymore as either you are just being tense or you are trying to just rile people up. I have better things to do with my time.
-1 -
It was not a feature, it has never been a feature. It was a bug pure and simple and it was fixed. Please stop trying to spread misinformation.
There is no Survivor or Killer bugs with our QA team, bugs are prioritised by impact first of all, and QA don't look at which side it's for. Lets stop making these arguments that we fix something because we're killer sided / survivor sided, we fix it because it's a bug.
4
