Cant believe people are really trying to argue against the flashlight changes

The FOV is the way it is on purpose. I would not hold your breath for this to change....ever. The killer's view is supposed to be restricted.

Kind cat speaks wisdom.

I'm not really a flashlight user, but welcome the change; being clicked at by my own teammates is annoying as hell, so can only imagine what it's like for killer mains. I read somewhere battery drains faster or seems to with the new changes? is that true or just peoples perception?

Flashlights have been nerfed so much that I see most players just trying to use them as an annoyance now.

Don't get me wrong, I think being able to be blinded from the side was absolute BS but it just feels like they don't work anymore. I see so many people try and fail to use them now: they may be newer survivors but it's definitely on the up.

Personally I think flashlights should be one guaranteed stun as standard but the bulb is consumed on use as the entity's dark power causes a power surge of sorts which breaks the bulb and renders it useless for the rest of the match. The bulb and battery add ons can stay as they are for things like stunning zombies or burning the hags traps. But if you try to stun the killer the entire bulb and battery, regardless of colour or equipped items are depleted. In this form, the flashlight and all its add ons would be exempt from Built to Last to avoid abuse. Using the flashlight as an environmental tool which lasts longer, or a one use stun is the choice you make.

Id also make it so when the survivor uses the flashlight as a killer stun the killer auto-covers their eyes in a defensive motion for 3 seconds . In this way, the killer wouldnt actually see any light and their own arm would be the thing that blocks their vision. The flashlight would lose its light too so survivors would know instantly when it's been effective.

This would make flashlights more effective for survivors, especially as stuns have been reduced in time, and make the item completely impossible to grief the killer with.

I'm sure some think it could be abused, but no worse than now.

Items are bonuses, and can even be taken from chests or passed off between survivors mid match, so I certainly don't blame them for being lower priority compared to core mechanics before them. Plenty of people still use the flashlights just fine, and like every single change thats been done to their skill floor in the past, there will always be a period of people adjusting before its business as usual.

Keys are also still plenty useful, but for different reasons: They're used more for tracking and on-demand aura reading via the addons, the key itself only being insurance in case the killer finds the hatch first and closes it. Their usage isn't necessarily worse than it was before, but it certainly requires a different mindset and perspective than just ignoring aspects of the game raw like it used to. Some people see less value in that, some don't.

also TBH it feels like healing and gen rushing are just extremely desirable in general with the current meta, so its not much surprise that toolboxes and medkits are king. Most of the addons in toolboxes are for sabo, yet i think thats a pretty secondary consideration for most people who bring them these days, even though they synergize with perks like saboteur more than ever.

??? How? The only accessibility piece to spine chill requires a terror radius. That doesnt change stealth killers at all. The turning on withing 36 meters is by design. The perk is designed to be a slight counter to undetectable but unlike the terror radius doesn't give indication of how far away.

>How is an item that can stop a survivor being hooked bad?

I suck at killer, and even I find it insanely easy to avoid flashlight saves. 99% of the time, you can just face the nearest obstacle and go for the pickup.

They wanted it so you only get the bonus speed with line of sight which it does. and its line of full sight. Meaning you can get stalked and you will not get the bonus speed if your left shoe is covered.

I'm okay right now, kid. I don't use flashlights on a regular basis anyways because I don't like to troll the killer like many of you do. I wanted to test it out since I'm on console and don't have the luxury of playing the PTB. I also play killer more than survivor since 6.0 was released, so it really doesn't affect me. I'm just pointing out how blatantly flawed it is and somehow it still got pushed to production. In the real world, that makes no sense. Imagine a new car being released with a severely flawed engine. That doesn't generally happen. It's obvious this mechanic is broken, but it was released. The pressure was $$$$$$$.

Doesn't bother me, either. I'm a killer main, and when I do play survivor, I don't mess with flashlights because my aim is atrocious. My apologies if I came off a bit too snarky; almost every person I've seen malding over this tend to act like it will never be fixed, or that it's a perfectly good excuse to roll it back and leave flashlights alone altogether. Unfortunately, the poor release quality is now standard operating procedure for a number of developers: push it out half-baked and patch it up later.

There are numerous threads here and on Reddit about epilepsy issues that predate this change.

Out of curiousity, do you understand any aspects of game development? Or even how bugs are handled with this game? Because there is a bug tracker on these very forums that they always encourage people to use instead of making pointless complaints on the forums for issues anywhere near as big as you keep inflating it to be. In said topics, they take user accounts and evidence to help isolate the issue. The entire thing with bugs is that their cause usually needs to be understood and isolated before they can be fixed, which no amount of outrage is going to help with.

When things go to live, they have integrity checks done as a means to see if an issue exists, and then more to see if the impact is considered acceptable enough to be ok with a delayed resolution in a subsequent bugfix or release, depending on the schedule. Either they were unaware and are working to identify and fix, or considered it not prevalent enough to cause major issues while they investigate. Either way, again, pointless outrage doesn't do anything to help when proper reporting and providing evidence absolutely do.

Yes, I do. I'm literally in college right now earning my bachelors in game design. When the flashlight was supposedly tested by their testing team, it should have been quite obvious that the flashlight automatically aims at the ground. They already said during the PTB that they were aware of the issue. The PTB is 2 weeks, so they had 2 weeks to fix a new mechanic which they didn't do. It's not pointless outrage when they didn't do their jobs to properly release a mechanic that was only supposed to only change the speed at which the flashlight turns on and off, and the sound of the flashlight. They didn't need to redevelop the flashlight completely which is what I believe they did. Unless they had to because they didn't code any delay modifiers but still, that's coding which doesn't cross over into the cone trajectory or where it aims. Everyone sees there is a major issue with the flashlights, but skilled developers somehow missing it makes no sense. Unless somehow the developers weren't paying attention while working on the flashlights.

When something is created or changed, it goes through a testing and approval phase. If it cannot pass testing, it is not implemented. One of the testing phases is called "Stress Testing", where a user does everything they can to break the mechanic/product/ect. This is usually the last phase of a test to make sure nothing is missed. But throughout any of the phases, if it fails, it goes back to programming. Again, you act like the flashlight has always aimed at the ground and that's something that can be easily missed. As soon as the PTB came out, many people were already pointing out this flaw. Twitch and Youtube streamers recording these events and basically saying flashlights are pretty much useless. But some of you, only a few compared to the majority calling out this issue, somehow still act like this should be accepted as normal. Like every major flaw that gets released should just be shrugged off.

And as for reporting tickets, the devs have been receiving them for a couple of weeks now since it was released in PTB. Behavior has already advised they were aware of the issue, which means they don't need any more tickets on the issue. They advised they were working to resolve the issue and still released it live despite knowing it was an issue. A person can test this mechanic in a few hours, maybe a couple of days depending on their workload, and still provide feedback that it isn't function as it should and should not be released. But TWO weeks of PTB and it was ignored. So yes, I know all about user acceptance testing, development testing, stress testing, bug reporting, and game development. I also know that something that you and the devs seem to think is so minor, will probably think something major will also be minor. Unless it costs them money, like people losing their perks, prestige, bloodpoints, accounts, or can't even log into the game. Customer satisfaction should always come first in a business. To do that, you provide quality products and service. You don't release a "fix" for a mechanic that is so easy for anyone, especially the customers, to see that it points in all the wrong directions instead of where they are aiming.

When the flashlight was supposedly tested by their testing team, it should have been quite obvious that the flashlight automatically aims at the ground.

Yeah again, not how bugs work. Bugs are caused by unintended reactions caused by errors in the logic, and are very rarely as self evident as you posit. Sometimes changing one word in a completely unrelated file can cause irregularities like that and nobody would have any idea the two could even be related, and considering its both a team rather than an individual, as well as a game written in Blueprints and later converted to C++, The potential for things like that to get missed is far more than you're willing to give credit.

The PTB was also for a lot more than just flashlight changes, in fact it was arguibly FAR more important to pay attention to the other changes that were being done as a litmus for whether they would even be potentially viable in the game at a later time. They have stated multiple times that this PTB was going to be completely different than previous ones, and again, that is precisely what the bug tracker is for. There was a report for it simultaneous with one that was about male survivors wrists distorting during certain animations, which could have been related and is one of the things they fixed. It apparently didnt fix it, so now the bug should (and has been) resubmitted in the live version so that it can be further investigated.

One of the testing phases is called "Stress Testing", where a user does everything they can to break the mechanic/product/ect.

They do, but they don't understand how to do it correctly. Smoke/Sanity testing has always been their biggest weakness in the game's development and continued support, quite simply they are bad at finding their own problems. I have been pretty critical about their QA teams in the past concerning this, so you are absolutely preaching to the choir. They certainly do them, and their bugfix notes in each patch mention things that have never been actively reported plenty often enough, they simply miss things very frequently. Whether it be due to them being overworked with the 1.5-3 month release schedules, not enough hands on deck, the team not being as good at the userbase at finding ways to break their own product, or simply not thinking to test specific aspects, they miss stuff. And that happens with any game. That doesn't mean them missing stuff means they never catch anything, though. Its a form of outcome bias to pretend they never do their job just because they missed one thing that angers you specifically.

Behavior has already advised they were aware of the issue, which means they don't need any more tickets on the issue.

Thats why you ADD to the tickets that exist. They don't want 50 people creating tickets for the same issue, they want people to go into the existing tickets and give additional setups: does it only affect male survivor models? does it only affect certain flashlights? addons? map geometry issues? the larger the sample set, the easier it is to narrow down variables that can cause the issue.

I certainly don't defend and agree concerning some of BHVR's coding bad practices like their absolute lack of accounting for extremes and lack of internal data integrity (and call them out for it when relevant, like here!) but I feel like you're really misplacing a lot of your frustration considering this game is notoriously bad about bugs, and always has been for its lifespan. There are sound bugs from years ago that still exist with how they implemented barrier based sound attenuation, nobody has ever claimed this game is great about bugs, just that youre just pointlessly complaining when there are aveues for you to help resolve the situation. I should also clarify I had to ask about the development aspect because of the amount of outcome bias there has been in your posts about it: it would be very easy to assume someone has no idea what kind of work actually goes into these things and assume there is none. If your argument is that they don't do a good enough job, thats perfectly fine. But expecting games to ship bug free like the

The fact that people accept broken mechanics to be released in video games seriously needs to stop.

comment kinda paint a different perspective. Even games with the best QA teams still have major bugs slip through regularly, and its pretty much why there are so many infamous bugs still in games from before the bugfix dlc patch days.

TL:DR Edit: you're putting your demands and expectations too high unless you are either someone working on the team, or a shareholder. This bug is one of many in the status quo of this game, and there is no reason to decide this is the one bug slipping through to get this worked up about.

flashlight ratatatatata on a mousewheel was annoying, can't see how the change really effects flashlight effectivness.

in a general sense, absolutely not

in this one case where quite literally everyone but the people using Flashlights to BM benefit, absolutely yes

I feel like you're agreeing but a lot of things you keep cranking up to 11 just to try to prove a point, like the customers over workers and shareholders part. Thats ironically exactly why the urgency of the flashlight changes were required, due to the controversy surrounding photosensitivity issues and BHVR's developing accommodations to prevent the issues. They needed to put the flashlight changes out ASAP due to the severity of its impact on the potential health of the customer (and also the shareholders and dev team themselves for liability, as some have complained about.) Another customer being inconvenienced is a secondary priority, and not necessarily one they are ignoring by prioritizing the other. If they did something like say "yeah we dont want to fix flashlights so we wont" that would be a different story, but they have acknowledged the bug and have been working with the community on isolating and resolving it. Its not as fast as you want, but again, your perspective seems tinged with personal bias.

As for tickets, I do hope people continue to send them in regardless how they are sent in. Maybe that will push the devs to fix this sooner rather than a year or two from now

So you'd rather make everything harder for them to actually fix things, and encourage people to sabotage the process, out of spite? Do you honestly not realize how venomous you're being on this topic? I will always prefer to turn my displeasure with how they do things into constructive avenues than act like a child over them.

But imagine your character in Assassin's Creed being unable to shoot a bow and hit a target despite the player is aiming correctly.

And there's where your argument falls through the floor. QA is entirely different for different types of games, which is why its extra ironic you used AC as your basis. It is not a multiplayer asymmetrical pvp game that runs as a live service with updates every 1.5 months at minimum, with regularly scheduled content updates every 3 months. After having transferred both languages and engines throughout tis development, migrating from p2p to dedicated servers, having passed its initial scope more than 4 years ago, filled with an ungodly amount of spaghetti code due to all to the above. They don't have to re-edit old code in those conditions, they work in development and pre-realease, bigfixes post launch, DLC and then further bufixes from that before starting work on the next game. There is no DBD2, its not an annual franchise from one of the biggest publishers in the industry, it doesnt even have a single player mode. It is very important to note, if you actually want to be constructive, that the game is likely not very easy to work with under the hood. You should always operate under the assumption that things may not work exactly like you posit, and even when i've done things like suggest simple checks to detect ragequitting on hook using simple universal methods like input tracking and/or duration and frequency of actions I have disclaimed that there might be something internally that makes a simple method like that ineffective or impossible to implement.

We actually agree on a lot of points, but your frustration is extremely misplaced. Make the bug report if there is none, and if there is, do what you can to provide case examples for them to compare with their testing. Use that energy for something positive, or ignore it and either play more games or take a break until they fix it. You can call it critique but it certainly isnt constructive criticism.