Category: 

What is a Kill Screen?

Article Details
  • Written By: Phil Shepley
  • Edited By: Bronwyn Harris
  • Last Modified Date: 26 August 2016
  • Copyright Protected:
    2003-2016
    Conjecture Corporation
  • Print this Article
Free Widgets for your Site/Blog
Roughly one-fifth of the world's stock of gold - worth over $200 billion USD - is stored under the streets of London.  more...

September 30 ,  1949 :  The Berlin Air Lift ended.  more...

A kill screen is a major error that occurs in a video game and usually causes further progress in the game to be halted. This error is usually due to a programming error or a design oversight and will cause the game to freeze, crash or simply become unplayable. Kill screens are usually associated with classic video games such as Pac-Man or Donkey Kong, which are from the Golden Age of Arcade Games.

Probably the most infamous kill screen is in the arcade game of Pac-Man. When the player reaches the 256th level of the game, the right hand side of the screen is replaced by random symbols and letters, and the game begins to act too erratically to play further. The reason this happens is that within the programming of the game, there is an 8-bit level counter. Since it is 8-bit, it can only possibly contain 255 distinct values, and the 256th value causes the game to crash. This phenomenon is known as integer overflow.

Ad

Integer overflow is not necessarily the only cause for the kill screen to occur in a video game, and sometimes games crash because of other types of computer bugs. An example of this was in another classic video game: Donkey Kong. In this case, the kill screen occurred on the 117th screen and was due to a design oversight by the programmers. In each successive level of Donkey Kong, the player is given less time to complete the level. The oversight is that by the time the player reaches level 117, they are no longer given enough time to possibly complete the level. This results in the kill screen where the player can go no further.

Other famous games that result in a kill screen after a certain amount of time are Dig Dug, Duck Hunt, Galaga, and Frogger. Usually these can be fixed with a patch. Other times, the kill screen actually becomes the goal of the player, who finally “wins” the game by causing it, ironically, to become unplayable. In the cases of Galaga and Frogger, the kill screen does not necessarily occur in a particular level, and a variety of circumstances can cause integer overflow and the end of the game.

Ad

You might also Like

Recommended

Discuss this Article

shepley
Post 2

The writer implied within the sentence that using the 256th value causes integer overflow (i.e. there are 256 values, 255 of which are available.) Nice try, though.

anon45198
Post 1

"Since it is 8-bit, it can only possibly contain 255 distinct values" Ummm, no. An 8-bit register can display 256 distinct values, not 255. Fail.

Post your comments

exception 'Exception' with message 'error writing captcha: Duplicate entry '2147483647' for key 'PRIMARY'' in /ssd/www/wisegeek/public_html/_core/classes/public/Captcha.php:44
Stack trace:
#0 /ssd/www/wisegeek/public_html/_core/controls/public/ControlDiscussionPostBox.php(324): Captcha->createCaptcha()
#1 /ssd/www/wisegeek/public_html/framework/classes/Control.php(104): ControlDiscussionPostBox->preRender(false)
#2 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): Control->render()
#3 /ssd/www/wisegeek/public_html/tpl/default-nocustom-lu/pages/public/article/article.htm(526): Control->__toString()
#4 /ssd/www/wisegeek/public_html/framework/classes/Control.php(300): require('/ssd/www/wisege...')
#5 /ssd/www/wisegeek/public_html/framework/classes/Control.php(309): Control->requireTpl('pages/public/ar...', Object(PageArticleCom), true)
#6 /ssd/www/wisegeek/public_html/framework/classes/Control.php(131): Control->renderTpl('pages/public/ar...', Object(PageArticleCom))
#7 /ssd/www/wisegeek/public_html/framework/classes/FormDataControl.php(87): Control->renderTemplate()
#8 /ssd/www/wisegeek/public_html/framework/classes/Control.php(109): FormDataControl->renderTemplate()
#9 /ssd/www/wisegeek/public_html/framework/classes/ScriptPage.php(50): Control->render(false)
#10 /ssd/www/wisegeek/public_html/framework/classes/Control.php(149): ScriptPage->render()
#11 /ssd/www/wisegeek/public_html/framework/classes/Page.php(97): Control->__toString()
#12 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(443): Page->processRequest()
#13 /ssd/www/wisegeek/public_html/_core/classes/public/PublicFrontController.php(7): PublicFrontController->renderPage()
#14 /ssd/www/wisegeek/public_html/index.php(11): PublicFrontController::run()
#15 {main}