Comments on: Classic Games, Classic Bugs http://blog.utest.com/classic-games-classic-bugs/2009/07/ Software Testing Community Fri, 30 Jul 2010 06:53:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Game Developers Conference: A Slideshow | Software Testing Blog http://blog.utest.com/classic-games-classic-bugs/2009/07/comment-page-1/#comment-14938 Game Developers Conference: A Slideshow | Software Testing Blog Mon, 15 Mar 2010 17:30:57 +0000 http://blog.utest.com/?p=1206#comment-14938 [...] meet Steve Wiebe, the long-time owner of the world’s top score in Donkey Kong. You may recall this author’s fascination with the never-ending battle for this top score, as chronicled in King of Kong: A Fistful of [...] [...] meet Steve Wiebe, the long-time owner of the world’s top score in Donkey Kong. You may recall this author’s fascination with the never-ending battle for this top score, as chronicled in King of Kong: A Fistful of [...]

]]> By: “Life’s a Glitch, Then You Die” (Happy Halloween from uTest) | Software Testing Blog http://blog.utest.com/classic-games-classic-bugs/2009/07/comment-page-1/#comment-14572 “Life’s a Glitch, Then You Die” (Happy Halloween from uTest) | Software Testing Blog Fri, 30 Oct 2009 19:53:24 +0000 http://blog.utest.com/?p=1206#comment-14572 [...] From Wikipedia: “Donkey Kong also featured a kill screen in the 22nd stage, and the 117th screen. This is an example of a kill screen that is not due to an integer overflow in a level counter (since programmers prevented this), but a different oversight on the part of the designers. The amount of time allowed for any given screen is determined algorithmically during play by the level the player is on. The timer is calculated 100×(10×(level + 4)), and has a maximum value of 8000. When the level reaches 22, the game reads 100×(10×(22+4)) or 100×260. However, the 8-bit counter rolls over at 256, meaning the game calculates 100*4. This causes the timer to be set so low that there is simply not enough time for the screen to possibly be completed.” (Note: we’ve blogged about this before) [...] [...] From Wikipedia: “Donkey Kong also featured a kill screen in the 22nd stage, and the 117th screen. This is an example of a kill screen that is not due to an integer overflow in a level counter (since programmers prevented this), but a different oversight on the part of the designers. The amount of time allowed for any given screen is determined algorithmically during play by the level the player is on. The timer is calculated 100×(10×(level + 4)), and has a maximum value of 8000. When the level reaches 22, the game reads 100×(10×(22+4)) or 100×260. However, the 8-bit counter rolls over at 256, meaning the game calculates 100*4. This causes the timer to be set so low that there is simply not enough time for the screen to possibly be completed.” (Note: we’ve blogged about this before) [...]

]]> By: Susan http://blog.utest.com/classic-games-classic-bugs/2009/07/comment-page-1/#comment-14445 Susan Wed, 19 Aug 2009 04:07:15 +0000 http://blog.utest.com/?p=1206#comment-14445 I recently came across your blog and have been reading along. I thought I would leave my first comment. I don't know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often. Susan http://onlinemariogames.net I recently came across your blog and have been reading along. I thought I would leave my first comment. I don’t know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.

Susan

http://onlinemariogames.net

]]>