http://dbd.game/killswitch
Poor Processes Exposed by Unfortunate Staff Actions
Recently a series of events occurred which exposed some extreme problems with the internal processes used by the DBD staff.
We had a staff member claim that Streetwise “does not meet kill switch criteria”
There were several other perks suffering from bugs with exploits like infinite sprint burst.
Three of these perks were kill switched by Behaviour and an apology was issued, but only after community backlash.
We have also seen that the developers have decided to reduce the opacity of the fog vials which isn’t the problem at all. The opacity of the fog vials varies depending on the map they are used on, with some maps appearing 100% opaque. There is also a bug which permanently creates fog across the map every time a vial is used until visibility is reduced to 10 meters.
This has exposed the fact that the staff of Dead By Daylight do not play the game they are working on.
There’s many other issues that I could delve into, like The Clown, which all show a consistent pattern of harmful development practices.
My suggestion is that moving forward, when making decisions about balance changes, new perks and new killers; experienced players should be brought into any meetings regarding changes to share their feedback.
I suggest this because I enjoy DBD and I want to see it succeed, but I don’t trust that the staff at Behaviour are capable of making these decisions in good faith.
Comments
-
People who are good at playing a video game are not game developers. Their input should exist for actual game devs to draw upon but they should not dictate changes.
4 -
I trust experienced players or content creators even less with the direction of the game than i do with BHVR.
4 -
The devs do play the game (pubs included) and they do have experienced players as advisors. To me, it's more likely that the entity or entities overseeing what gets greenlit for any given patch is the wrench in that system. It's easier to direct our upset and frustration toward influencers and community managers and I think BHVR is aware of that. Not trying to fly too close to the sun there, but I'm just saying.
1 -
Normally I'd try to agree with you, but there's a giant steel beam in the offering menu that would have been easily caught if they played even a single game before releasing the build to production…
2 -
It still applies there. The recent livestream proved that the decision-making is clearly a major culprit with these things. Although the beam itself is likely more to do with spaghetti code getting in the way of anything that would fix it.
0 -
Who knows, maybe the beam is the only thing holding up all the code and removing it would cause everything to collapse. (That's a joke, but look at this cool graphic.)
3 -
The beam being there is not anything to do with spaghetti code. Someone just added object that clipped into the view point of the offering showing screen area. Like everything you see the main lobby, the queue area, offering loading screen and match loading screen are all in that same instance the game loads in the beginning. You get certain view when you get into the lobby showing the abandoned road with the guard towers. Then when you ready in to lobby the view changes to somewhere else that is out of sight of the main menu area. Then when the match starts loading you get the loading screen and offering screen views. The beam that was on the loading screen was most likely one of the legs of the over road sign clipping into the area where the offering screen is located. Its just someone placing asset and not noticing its in frame for the offering screen.
You can think it like this there is several cameras in the area and every time you change menus you switch to different camera but you are still in the same area just seeing different viewpoint.
1 -
Read the part where I said, “That’s a joke.” I’m a software engineer myself, with experience across banking, medical, and gaming industries. I know the beam has nothing to do with code.
It’s simply a comically bad oversight, one that perfectly illustrates how little Behavior appears to test their own game.
In the Unreal Editor, removing a game object takes only a few seconds if no one else has the level checked out in source control. The fact that it’s still in the game makes its presence even more baffling.
0 -
It is removed they removed it in today's patch.
Still don't know why you are answering me I was talking to the other person claiming its spaghetti code when its not really a code issue but someone placing asset wrong and not noticing its clipping into the loading screen area.
0 -
Ah my bad. Idk why I got a notification that I was replied to.
I haven't been playing DBD lately so I wouldn't have seen any patches for today. I switched to Nightreign and have been "gitting gud" as Executor. I recently got the achievement to kill three different Nightlords in a row without dying!
Honestly, I may uninstall DBD. The recent performance of the staff has been unacceptable for me and there's too many other good games.0 -
No problem man. The beam is still in the game but its now a badge you can find it in your badges.
Have to admit I have been taking minor hiatus from playing DBD myself but its more of me playing it too much recently and just wanting to do something else.
You also most likely got the notification because its your topic so you most likely have accidentally auto subscribed to it or something.
0 -
True, true 😎
Very interesting. I didn't consider that.
0
