#18: Error-Free

- 12:00 am

An extensive, intriguing and lively story, new weapons and items and even completely new buildings, all of that await you inside the CSP – a true mammoth project. To make sure you’ll always have a lot of fun with it, bug fixing is very important. But how do we get rid of all these little bugs? With the example of a concrete example, we’ll show you how the fixing usually works. 


Phase 1: 

A team member recognizes an error while using our current developer build.  

In this case, faces are mirrored while in a conversation. This is pretty obvious if some characteristics are not symmetrical. Here you see the original screenshot that was part of the message in our internal board. Those don’t look like the ones on our website or the social media channels. They only need to show the error clearly without consuming to much disk space. 

Phase 2: 

The problem is thoroughly analysed. We try to understand the problem and it’s origins to solve the problem as completely as possible and not only at the place we found it. In our example, part of the analysis was a comparison of the static and animated meshes. 

Phase 3: 

When the origin of the problem is found it is fixed by the responsible department. Sometimes the solution is quite simple if only one value was set wrong, but sometimes the problems are far more complex. Sometimes some creativity is needed if a direct solution isn’t possible. 


In this case, the problem could be solved so that the characteristics are only found on the right side at any time. 

Phase 4: 

The corrected file is released. After that, additional team members test the fix. But not only the fix is checked, but also if additional problems occurred after the changes. If needed the fix is revised. In this case, we discovered the same error on various faces. Now all faces have their characteristics on the right side. 

Phase 5: 

The right file is uploaded on the server and the thread in our forum is closed with a note. In this case, it was: “Fixed #8237