Why make a code-heavy character when you are not capable of coding too well?

How do you know that it’s because of ‚bad coding‘

its probably just because there was not enough time for QA and bug fixing. They have a pretty tight schedule with 3 month a chapter and all..

Granted they have bugs, but the twins are strong and pretty original.

Like every character they release, it comes with problems, and the bugs will be fixed.

I play through the bugs and consider it tapering. If I can get 4ks with a buggy killer, imagine what I can do when they get fixed.

Survivors beware! Lol

well fine i don't care what they edited and i doubt it was what you said it was, and there you are trying to make it sound better constructive posts are what is needed not the anger filled posts like yours. you don't see me belittling the devs, or anything yet i'm angry and I STILL make constructive posts even when I'm angry you how ever like personal attacks, btw so you know the community team passes constructive posts back to the devs so something like this might never be seen by more than the community team.

you disparage the dev's skill, you have know knowledge on what they can and cant do yet you make comparisons to other developers making games that are markedly different between each other. That in and of itself is the offense, I am also offended you didn't even come up with any good ways to fix this, obviously you are an expert in the development of this game why are you not working for them so you can make sure they do it right? oh right probably aren't a programmer, and thus where is your stance based, what knowledge are you using to support your assertions? it's better if you have a problem for you to try to help solve it instead of just throwing stones. I read nothing in your post that was constructive and that is another reason I personally am offended that you didn't just criticize the devs but didn't even find a way to help the situation. I'm more offended and disappointed at you being so petty.

you can call the game crap and i wouldn't care. but when you disparage someone's experience without even knowing it makes you petty and that is what offended me, not the fact that you had criticism. you paid money to play a game yes, one that you agreed will change over time (as it is multiplayer as well as having new content being put out). you agreed to play the game AS IS and if there are issues you can say hey this happened, whats up, here's the information you need to check into this. Your post is a direct attack on the devs, but it doesn't even address the issue. many posts here even in their attacks they still atleast TRY to help fix the issue even though many times they only want to fix it for one side or the other and not a balance but still it is better than a straight attack. and you end with an attack on me, this shows how immature you are being over this. my offense is your pettyness and that completely seals it. I'm glad your words are not going to be highlighted to the devs.

i never said that, I just said that if you want to complain about something at least 1) don't be insulting to others, 2) be constructive, and 3) don't assume what you don't know. your attitude is I can complain all I want to and everyone has to listen to me because I paid for this game and I get every say in the world about it. this is an elitist attitude and it comes through loud and clear every time. So complain all you want, seek sympathy what EVER you want to do but if you're gonna complain at least put an idea forward to try and show you want to HELP with the problem than just complain about it. I'll tell you complaints that are offered like this are listened to about 1000 times quicker and about 1 million times more likely to be considered. so you found a bug where X character stands and does a jig, which shouldn't happen. well instead of saying "#########?! why am I doing a JIG?" you could say "well I found that when I did Y my character, X, does this Jig so perhaps there is a correlation? " This is the way to get things really noticed, but if you start ranting "This game is ######### becuase my character just does a Jig, WHAT THE HELL!?" the devs tune that out and stop considering anything from that line of thinking till they see something that has some respect in it.

Also you paid for a game, and before the dlc was released, you were WARNED this dlc was being released with issues and those would be addressed in upcoming hotfixes, but you still paid for the dlc. I've encountered a few bugs which I have reported but I haven't bought the new characters so I can't say what is happening with them, and I haven't gone up against the new killer personally.

you just don't know what can be an insult. and you grin and laugh you're despicable for that.

you compared them to blizzard employees, thus saying their experience is less as well as their knowledge is less. you are talking out your rear for this trying to salvage your post. you speak as though YOU know programming (your (C) option) and your (A) option doesn't speak to their capabilities only what you are seeing here which might be an indication but you are speculating in an area you don't know thus it's bad and it's insulting to them to say you know they aren't as good as someone else.

28, according to their Wikipedia page. Blizzard has 29.

My bad.

first of all if you are talking about me, I am not defending the dlc, I have always talked about the veiled attack on the devs. just because some company has more years coding and making games doesn't mean that they are automatically better. same with people, just because you have been around doesn't mean someone else hasn't got the know how to best your knowledge. In tech this happens many times, a person who's been around much more but hasn't kept up to date can still do their job but won't excel because they don't have the mindset to get the new tools. Someone coming up in the ranks will use the newer tools to make things better. example admiral Rickover in the us navy who spear headed it's nuclear propulsion program refused to integrate newer methods of operation but kept to known things and thus it kept the program on a slow but steady course. so this is the case there were civilian power plants that had better setups than the navy did but they were prone to failures right away.

so why did I talk about this? older programmers might not try something like this because they don't want to rock the boat, the newer programmers are more ambitious and will leap at newer challenges. Now this is what happened here, the devs here tried things and when it came to it the higher ups said this goes out on schedule ready or not, so the devs tried to alert people to this and that they were working. so what happened we have posters like this one insulting their capabilities when he/she doesn't even know what those are or how to classify them. might want to understand that the OP wants people like you to misread what people like I say. The DLC was never being defended here because it was put out unfinished, but that decision is not one the devs make but the over all company execs and the devs either say yes sir to this or they get fired.

The game is a giant ball of rubber bands, all glommed together. Fix one thing, three other things break. It's something that the devs put up with because they can't prioritize fixing it. The devs are handcuffed to whatever quarterly release schedule is being forced on them, and they're obviously not given enough time to fix bugs. The people who actually make the game don't have any say in this. Creative teams usually don't have broad leeway to dictate their development schedules.

Every piece of software is a bug-ridden mess at some point; you just don't see it a lot of the time, because the developers were given the time and space they needed to iron everything out. It's why games and other pieces of software get delayed. You would simply not believe the degree to which some games that you love and would consider top-notch were once almost unplayable. The problem with DBD -- aside from what I have described already here -- is that it's a live service, so it's a bit like trying to repair a car while it's going 60 MPH. And the bean-counters won't let the car slow down, because their revenue and their metrics tell them that everything is going fine.

I'm not trying to defend some of the dumb stuff they try to push through, and this patch is just ghastly in terms of how badly they botched it. But you need to take the realities of development -- and executive apathy about it -- into account. "Developers just bad" is not remotely the entire story.