I hope DBD will not get a reward on steam this year.

Actually... the fact that you play this game means you like the idea, not that you like how the devs are doing things.

And it's not like that, "oh, if you keep saying that we don't care we will stop", this is not a free game you know? They are making money with it, so we, as purchasers are part of it. I can understand how damaging it is, I have made things for ungrateful peopple, but I didn't get a reward by it, that's a true "labor of love", if you do bussiness then that's a different thing.

And as toxic as the community is, I do believe they are very patient with how BHVR's is doing things. When I came into the game, the first event was the BBQ event. I am sure it recquired a lot of work but. Why removing almost all existing events when they have already the codes? Would you call that a "labor of love"? Would you call a lavor of love to not refunding the Legacy cosmetic to those who own the game since day one when they said "we are trying to bring it back" for years but now they sudenly say "we can't do it"? Would you call a "labor of love" when they could have done a blood hunt during lockdown and they haven't? And yes, we ended having it but because the community pushed for it. So no, a "labor of love" is something that YOU do, not that you're FORCED to do. Another one. Would you call labor of love when in the free rift there are many tiers with absolutely nothing even supposed they could give a few blood points or shards?

If it's a "Labor of Love" then why does the community needs to push those changes? Even infinites were changed due to community pushing it, not from behaviour's side. So yes, this is a Labor of love but for the community of this game that keeps pushing things, not from behaviour. Even the new upcoming perks are just bandaid fixes for in-game problems, like ruin as an example.

So... now you're saying "Don't be negative?" if you do something it's because you care, a friend of mine recorded a wonderful video message to me even if I didn't ask for it, that's because he cares, now if I were the one saying "Could you make a message video to me?" and he agrees. Don't you think that I have every right to be angry when he made a promise to me that he didn't keep or he seems to have forgotten?

This community is so [BAD WORD] ridiculous. They are never satisfied. They are working, they cant change everything but they are working on balance.

I rarely jump on the forums, but I felt like I needed to respond to you because what you're saying is suspect. I'm a Software Engineer, I don't think you are (or you're very knowledgeable) frankly. You might be super old school, especially since you mentioned languages no one uses from ~30 years ago.

To be entirely transparent, I have ~15 years of experience with modern development (5 professionally) in C++, C#, PHP, Python, JS (node, frontend frameworks), Typescript, Visual Basic 6/.NET, Java, and F#.

Here's what stands out:

• "Fortrain" is Fortran. This is a niche language that was released 60 years ago and since essentially replace by Julia or Python for scripting purposes.It's also not OOP, so it's largely irrelevant in todays engineering.
• Basic and COBOL are also old and are not entirely OOP (COBOL apparently added some support in 2002). Like 40 to 60 years old.
• C+ isn't a language... It literally doesn't exist.
• Assembly and machine code are both great concepts, but have little to do with modern code practices.
• I'm not sure why you even mentioned command line environments. As an engineer, that's probably the last thing I would think of as something "impressive" to explain my credentials. I work in the command line pretty much all day in various Linux distributions and Windows (cmd, powershell)....

I can't quote multiple of your posts, but they all have bad or odd information. Particularly, your rant on spaghetti code was interesting.

"this is what happens here, for anytopic for the most part: disconnect penalty, the fact that killers are getting nerfed all the time or survivors are always nerfed and many other topics like this one and the dreaded "Spaghetti Coding" which is a term coined in the 70's and 80's for a programming style that is no longer even used. originally programs were written with number lines (like 10, 20, 30, 40 etc) and when you needed to add things you had 9 lines you could do it with and thus you end up having to redirect the program to lines far down the line and then make sure it returns to the right point."

Spaghetti code absolutely is a thing today?

The modern foundation of software design (OOP) is encapsulation, data abstraction, polymorphism and inheritance. If your objects are properly designed, they should not directly interact with other objects that are logically unrelated. That's why techniques and design patterns such as Dependency Injection are a standard.

But I digress, the point is that not properly following these principles is regularly considered "spaghetti code".

Also, using the Blueprints has other reasons that Scott didn't mention. There isn't a great VCS for Blueprints, which makes working in a team difficult. It's not just Scott that states using Blueprints for large portions of a game isn't viable.

I'd respond even more, but I just wanted to point out some issues from your posts on "page 2" before others took you seriously.

I see that this thread got pruned way to go mods it doesn't make you look desperate at all ;).

Sadly the game is massiveley underrated and pretty unknown by many. The game is so great, already prestige 11 on it.

I'll give you the benefit of the doubt, but:

• C+ was never a language. You can see a list of languages here (link). You can see the history of C++ here (link). The reason why there was no C+ (it was actually originally called C with Classes from 79-82) is because the naming is purposeful. The ++ symbol is called the increment operator, so C++ is supposed to mean "The next C++".
• I appreciate the aerospace background, but that doesn't provide much cross-knowledge to modern development.
• If you think that debugging code is simple in any way, you're extremely incorrect. The etymology of spaghetti code is irrelevant to modern standards. Spaghetti code has it's own Wikipedia page (link) that explains what it means.

Quote: "Spaghetti code is a pejorative phrase for unstructured and difficult-to-maintain source code. Spaghetti code can be caused by several factors, such as volatile project requirements, lack of programming style rules, and insufficient ability or experience"

If you watch the video though, Scott provides proof of why he states they use Blueprints. Blueprints are way less manageable compared to C++ code. Mclean also has a Twitch VOD that states they use Blueprints, but much less. Of course there's other factors that cause bugs, but historically BHVR has caused the same bugs to reappear in future patches. My educated guess is that they aren't properly utilizing VCS, QA cycles, and a proper UAT environment/system to ensure these bugs don't suddenly reappear.

I entirely sympathize with the devs. It's likely they knew the patch was not ready to go live, but management pushed them to launch on schedule. Debugging is difficult and if the code is not following best practices, it's easy to create new bugs and also extraordinarily difficult to find/fix existing issues.