I’d say Lumberyard played a role in SOME of the issues, but definitely not all of them. I mean look at the decision-making. We still don’t have a roadmap FFS.
From a pure development perspective the root cause of patches introducing new bugs is often due to the programmers not having an in-depth understanding of the architecture and implementation. This happens when you lose employee continuity or you take a silo approach where some people only do this and some people only do that and there is communication failures. Often, organizations that lose employee continuity switch to a silo approach out of necessity. Treating people as plug-and-play modules increases the likelihood that continuity is never recovered because most people do not enjoy working under those circumstances.
It is also an indication that there is a testing suite short coming. What is a testing suite? It is a library of test recipes i.e. do these 25 steps in this order and this is the expected outcome. There are tools out there to script all this testing, collect the results and generate statistics so a human can sit in judgement. This is also referred to as regression testing.
As someone who has been everything from a programmer to a department manager I suspect that NW is in an all-of-the-above situation.
2 Likes
Pretty much is. When they released the game we only had that Lumberyard Engine, after so many bugs we faced and a few patches, a new “Azpth Engine” started to appear on launching screen. They are trying to rebuild the game from 0 on another engine, thats why we have like 0 response and communcation. They launched a game that wasnt ready, completely broken and not finished. Now the game entered a place where its not sustaining itself
1 Like
Well said.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.