Two different things: Bugs - Fortress
HarteSkole
Posts: 9 ✭✭
Bugs: It is important to prioritize fixing the bugs in the game before including new elements. The bugs make it less fun to play, witch for me and probably others players means reducing playing Harry Potter Unite. For example the bug with color flames everywhere is very ignoring and time consuming so it would be nice to prioritize fixing that.
Fortress: It is much more fun to play in fortress especially Dark chambers (random) with tasks like “take down XX enemies in fortress”. I know there are or can be a good reasons for playing egotistical or being mainly passive in fortress, but if you had to take down X enemies in a fortress battle to get XP from the fight, I think/hope it will motivate to knowledge about the selected profession in battle and how to prioritize helping wining the battle if none enemies for mine/yours profession.
It was different and much more fun experience to play for example Dark 5 under this brilliant event because it’s much easier to win the battle when everyone in the chamber are active and helping . I know that this subject easily can provoke writings about technical difficulties and it is possible that we just have had a worldwide lucky week with nearly none technical issues.
Comments
Honestly, there are hundreds of bugs in the game. They seem to have greatly increased in numbers, since the start of the pandemic, since most programmers now work from home.
I am guessing that most of them don't even play the game. They just get assigned a bug to fix. Then they find the line of code that they assume is generating the bug, change it, and submit it for the next patch. In many cases, instead of finding the correct line of code, they find a similar line of code that is actually associated with something unrelated to the bug. Changing that code results in a new bug. Since they don't perform any testing before pushing the "bug fix" in the next update, the new bug and failure to fix the current bug are not noticed, until the next patch goes live.
Once the patch goes live and players submit feedback that the old bug is not fixed and there is now a new bug, they assign the task of fixing the, now two, bugs to random programmers, which results in possibly more bugs.
My guess is that they are failing to make a proper changelog, to show what is being changed and when; so no one really knows what the other programmers are doing. With reduced communications between the programmers, due to them working from home, the likelyhood of more bugs is drastically increased.
That make sense
Testing doesn't remove bugs. Testing merely shows the presence of bugs. It would then be the responsibility of the project managers to priorize the bugs higher than the features they compete with in order for them to be adressed.
And software-bugs rarely are only a single line of code. Software nowadays tends to be so complex that most bugs are a combination of several statements that all would need to be changed in order to adress the issue.
Another issue is that often developers write code at the height of their own skill. But given that debugging code requires more skill than actually writing it, most developers are incapable of debugging their own code - therefore also unable to understand the mistake that lead to the bug and likely to repeat that same mistake again and again.