{"id":361,"date":"2018-06-19T08:33:10","date_gmt":"2018-06-19T15:33:10","guid":{"rendered":"https:\/\/blog.sixages.com\/?p=361"},"modified":"2018-06-20T11:41:27","modified_gmt":"2018-06-20T18:41:27","slug":"bugs-part-1","status":"publish","type":"post","link":"https:\/\/blog.sixages.com\/index.php\/2018\/06\/19\/bugs-part-1\/","title":{"rendered":"Bugs, Part 1"},"content":{"rendered":"

I don\u2019t know if this is a dark secret of game developers, but games ship with bugs. Known bugs.<\/p>\n

\"Status<\/p>\n

Part of the late development process is reviewing the bug list to see what most needs fixing. We all hate bugs, but we also love shipping. Not everything has to be fixed before release. The closer we get to making the release build, the stricter the criteria become. We\u2019ve recently deferred a bunch of bugs that we would have fixed when we started the triage process.<\/p>\n

Why be so strict? Because many fixes can have unintended consequences. We just discovered a fairly rare bug yesterday, which had been introduced by a change we made last year (which was tested back then and found to work perfectly as designed). Since even a simple bug fix can destabilize the game, we want to make sure any last minute fixes are truly warranted.<\/p>\n

At the end of the process, the only bugs to be fixed are those that affect all players, prevent play, or make us look stupid. Most of what we\u2019ve been finding lately have been issues that come up if you have tons of feuds, or when you made certain decisions and then ally a particular clan. These aren\u2019t going to be that common. And even the players who end up doing that won\u2019t be blocked from the game, or find it illogical. My classic \u201clook stupid\u201d bug was a game I saw years ago, where the publisher spelled their own name wrong on the title screen. Luckily we haven\u2019t found anything like that.<\/p>\n

But of course, we do want to fix all the bugs. So I\u2019ve been making the fixes in an alternate branch of the code. As soon as everything is locked down in the App Store, we\u2019ll switch over internally and start testing that.<\/p>\n

Part 2 of \u201cBugs\u201d<\/a><\/em><\/p>\n","protected":false},"excerpt":{"rendered":"

I don\u2019t know if this is a dark secret of game developers, but games ship with bugs. Known bugs. Part of the late development process is reviewing the bug list to see what most needs fixing. We all hate bugs, but we also love shipping. Not everything has to be fixed before release. The closer … Continue reading “Bugs, Part 1”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[14],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/posts\/361"}],"collection":[{"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/comments?post=361"}],"version-history":[{"count":6,"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/posts\/361\/revisions"}],"predecessor-version":[{"id":379,"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/posts\/361\/revisions\/379"}],"wp:attachment":[{"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/media?parent=361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/categories?post=361"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.sixages.com\/index.php\/wp-json\/wp\/v2\/tags?post=361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}