Devs deserve some credit

I Understand perfectly what you're saying... ive given credit where credit is do... the flood gates need left open this time.... I'll provide them with a thank you when they touch up the game again.

Dude level with me, giving them credit isn't gonna get anything done. If we keep telling them what they do well instead of what they do poorly, it'll just get to a point where they get complacent because it'll seem like the people bringing up the bad is just a very vocal minority, and that's what kills games.

Yeah, I mean whatever the reason, it's still a fair point. People aren't likely to change their minds unless you're relaxed when you're talking to them, even if they know their point isn't very strong. And there's certainly more than enough high-tension comments on the forum anyway.

1. ~36 new characters including licensed characters from major horror franchises, new engine and improved visuals, rift / archives, massively improved balance, console releases, crossplay, dedicated servers, SWF (people love to hate it, but this game might be dead without it), etc. Community feedback is important, but please give credit where credit is due.
2. I'm sure they did play the game on console before releasing the patch. Not everyone is running into the performance issues, though, and they have to weigh performance issues for some people against "sorry, we're cancelling the event due to poor performance". You can bet people would have been on them for that too.
3. I'm talking about the collective, not the individual. I'm not saying that the person who made any one post definitely doesn't know what they're talking about. I'm saying that many, many people are complaining and most of those complaints betray no such knowledge. On the whole, then, most of the noise is almost certainly coming from people who don't know enough to comment on how well Behaviour is doing its job.

1. Those changes (rather than the content updates) are all things that they've done in the past, yet they hardly do anything to improve upon it once they've released unless there's outcry. I give credit to devs that deserve it, and they don't deserve credit for balancing the game. The community does.
2. Not everyone? Most, if not all, people are experiencing these issues. If they weren't, they wouldn't have so many people complaining about it. The people not having issues are the lucky minority.
3. That's fair.

I've been playing for almost 4 years and feel this game has improved tenfold. Can it be better, absolutely. Will they continue to improve it, yes. However, they have to work with the player base and unfortunately that's not going to make everyone happy.

Developing a game like this is not a simple task. BHVR has to take into consideration player skill levels or lack thereof and strike a balance that works for everyone. When Freddy first released, I was perfectly fine with his design. But most weren't. BHVR listened to community and made him more accessible for a wider audience. This happens with a lot of MP games when they first release. Developers have to adjust difficulty to accommodate lower skilled players.

Which sucks because instead of working to get better at the game, people tend to complain about designs that simply don't fit their play style and want it changed so it does. Which can hurt a player who could have benefited from a new killer that worked better for them.

Video games are competitive business and the fact that DBD has no rival after all these years says a lot about the state of the game and their dedication to improve it.

1. They've been continually improving visuals, continually releasing and tweaking killers, perks, etc., releasing cosmetics for new and old characters, they're in the midst of a push to refresh all old maps, and they've been making lots of perk updates lately, mostly to really trash-tier perks to make them more viable again. I think they've been doing a lot. The community and the devs both deserve credit.
2. I've seen posts on here from console players and PC players complaining about performance, and I've seen posts on here from console and PC players who have noticed no difference. I don't think anyone knows how widespread it actually is. I haven't noticed a difference personally. If most people's performance is actually as much of a slideshow as I've seen on some posts on here, BHVR would be shooting themselves in the foot to release this patch, which is why I'd assume it's only some people. Even if all they care about is money, they don't make money by releasing a patch that most people can't play.

I think paying for the game is credit enough

and stay for how long we have.

As a software engineer I'm going to tell you right now that what you learn at school/college is nothing like actual development. Little/no colleges teach about how real world engineering is like and you only really start to know once you get a job or internship. That is why imposter syndrome is such a huge huge huge thing in the field.

Anyways, I'm arguing against your point #2 - we don't know if their code is spaghetti because something changes and breaks. There are so many factors in this.

DBD is written in presumably C++ because it uses unreal - I'm gonna give a situation I've been in as a dev in c#, which is also an OOP language. Let's say we have a base class - BaseSurvivor that has base mechanics for every survivor and whatever inherits from that class overrides as needed, whatever. Let's say they have a method on there that calls a static helper class that does some business logic, and we had a bug report come in that says 'hey this isn't providing what we are expecting' and we go in and fix it, but in the process we introduced a new bug. The devs and QA team go through it and test it don't find anything wrong. We ship this update out to the customers, and bingo bango we got another bug report come in because this static helper class was also used in another part of the app and had unintended consequences. That's not spaghetti code, that's just the paradigm. One of the biggest things in OOP is reusability of code, if you need to do the same thing twice, you make it reusable.

Sprints are also not just one thing being worked on, it's multiple things being worked on at once by multiple people. Blaming something broke because they fixed something could be a completely from something else even though to us, the end user, it seems that correlation = causation for the issue.

In either case, I don't particularly put blame on issues on devs on a few issues (ie this event) because usually things like this are controlled by product team and priorities and initiatives usually come from the business side of things and they are told what to do. This is why it takes forever for things to happen. Remember when they changed auras and had so much backlash? It's not just as simple as a dev or two going in and reverting things, it's an entire process. Product and project managers need meetings, determine if it's a "hotfix" or if it will go out in a regular update, devs need to estimate time/effort on the tickets created, do investigations, it needs PR reviews, it needs to go through some QA (I assume bhvr has some sort of QA, but sometimes I question that).

I think the biggest issue facing DBD is that the original devs didn't expect this to blow up and it's just had bandaid after bandaid of fixes that can only be solved by rewriting the game from scratch, and that's not a particularly easy initiative to take nor is it profitable for the business side of things to hold off on what could be a multi-year project to approve it. These are usually put in the backlogs as technical debt tickets and sit there forever and taken up randomly in sprints and not at once. Even if any new code is optimized/cleanly written/whatever, it's still on top of the base code that isn't.

TL;DR blaming devs doesn't do anything when things like the event come from above them and the business side got initiatives to hit, deadlines to meet, blaming devs for spaghetti code for changing something and another thing breaking is ignorant we don't know what their code base looks like nor do we know if it broke because something else was worked on

Have the devs admitted that? Have you seen the code? Has the source code leaked? Am I missing something here? Obviously, I haven't seen it, I don't know what their code base looks like, I'm just arguing you can't say it's spaghetti code unless you've seen it and bugs can happen regardless if it is or isn't.

Please reread my example. And again, when developers do stuff it's usually in sprints where multiple things are being worked on, again: that doesn't mean it's spaghetti code that breaks it. If an abstract or base class is used for all killers, and they fix a bug from one killer in that abstract or base class and it affected spirit, that again is because it's spaghetti code. It's literally the paradigm of oop to have code being reused when you can to limit spaghetti code.

Edit: if I get proven wrong and shwon proof it is spaghetti code, cool, I'm just offering alternative reasons as a dev and I'm giving devs at least a little benefit of the doubt because I work in the field.