Kazza
Member
An interesting and well balanced video, looking at many different examples (too many to list) of how developers react to criticisms of their games. It seems that the Marauder enemy in Doom is one of the most recent examples, with some people asking it to be nerfed/removed etc. I haven't payed attention to that particular "controversy", but I did notice some people complaining about some of the SoR4 bosses being too hard (on hard mode!) and asking the developers to make changes. There have also been a vocal group complaining about the lack of SoR3-style rolling/running mechanics (it seems SoR3 was more popular and sold better than many assume, judging by the number of people missing its special moves). I think someone summed up the situation quite well when they wrote (paraphrasing here, as I can't find the original comment:
1992: This bit is quite difficult, I need to take a new approach and try to get better.
2020: This bit is quite difficult, the devs need to patch and fix this.
The video gives examples of how devs take players views into account during development, as well as after. It also explains a few things devs should consider before making changes to their game, such as:
- making sure that the complaints reflect the views of your players as a whole, and not just a very vocal minority
- not necessarily implementing the solutions proffered by your players, but instead to delve into the source of their complaints and maybe thinking of a better solution
- there are some things that some players may hate but that others love, and listening to every comlaint could result in a very mediocre game without any special characteristics
There's much more packed into the video, so I would recommend that you watch it.
Last edited: