Game freeze: Difference between revisions
(→Intro) |
Bearfan121 (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{redirect|"Freezing"|the status ailment Freeze|Status_ailment#Freeze|Status ailment}} | {{redirect|"Freezing"|the status ailment Freeze|Status_ailment#Freeze|Status ailment}} | ||
A '''game freeze''' is when the data completely stops flowing to the screen, thus causing the game to lock up. During a game freeze, the player cannot move, speak to other characters, select an object, or use any buttons. The only way to escape a game freeze is to simply turn the power off. Game freezes can occur due to the lack of information input into the game, such as when walking out of the boundaries of an area. They also occur when performing glitches such as the [[Mew glitch|Mew trick]] incorrectly. | A '''game freeze''' is when the data completely stops flowing to the screen, thus causing the game to lock up. During a game freeze, the player cannot move, speak to other characters, select an object, or use any buttons. The only way to escape a game freeze is to simply turn the power off and restart the game from the player's last save. | ||
Game freezes can occur due to the lack of information input into the game, such as when walking out of the boundaries of an area. They also occur when performing glitches such as the [[Mew glitch|Mew trick]] incorrectly. | |||
[[Image:Redcrash.png|thumb|right|A game freezing in [[Generation I]]]] | [[Image:Redcrash.png|thumb|right|A game freezing in [[Generation I]]]] | ||
Incorrect codes on devices such as an [[Action Replay]] or [[GameShark]] can result in encountering [[glitch Pokémon]], that can cause the game to freeze. In addition, a game may freeze if the player has used too many cheats on it, | Incorrect codes used on cheating devices such as an [[Action Replay]] or [[GameShark]] can result in encountering [[glitch Pokémon]], that can cause the game to freeze. In addition, a game may freeze if the player has used too many cheats on it, and possibly rendering the save file unplayable and the game permanently damaged. | ||
Game freezes are often accompanied by an odd buzzing sound; however, sometimes the normal music for wherever the player was before the game froze can be heard. Frequently, a loop or constant replay of whatever sound was being played prior to the freeze will be played. Sometimes, a freeze will play no sound, even if there was a sound being played before the freeze. Some game freezes are also accompanied by opcode errors when playing with an emulator, meaning that the game gives incorrect or impossible instructions to the hardware of the device, effectively crashing the game. | |||
The game may occasionally freeze while playing any [[Generation III]] game, when a player's Pokémon uses {{m|Thunderbolt}} or {{m|Thunder}}, or when fleeing from a [[wild Pokémon]], though | The game may occasionally freeze while playing any [[Generation III]] game, when a player's Pokémon uses {{m|Thunderbolt}} or {{m|Thunder}}, or when fleeing from a [[wild Pokémon]], though cases of the glitch actually occurring are exceedingly rare. The problems caused by the glitch occurring can be rectified by turning off the game's [[battle animation]]s. The moves only cause a temporary repeat of the sound, and it will go away if the Pokémon taking the damage is defeated. | ||
If the game is dropped, hit by any major force, has a dirty game cartridge/card or physically removing it from the slot may also cause the game, no matter what the generation to freeze. | |||
{{Stub|Glitch}} | {{Stub|Glitch}} | ||
Revision as of 20:19, 5 March 2010
- "Freezing" redirects here. For the status ailment Freeze, see Status ailment.
A game freeze is when the data completely stops flowing to the screen, thus causing the game to lock up. During a game freeze, the player cannot move, speak to other characters, select an object, or use any buttons. The only way to escape a game freeze is to simply turn the power off and restart the game from the player's last save. Game freezes can occur due to the lack of information input into the game, such as when walking out of the boundaries of an area. They also occur when performing glitches such as the Mew trick incorrectly.
Incorrect codes used on cheating devices such as an Action Replay or GameShark can result in encountering glitch Pokémon, that can cause the game to freeze. In addition, a game may freeze if the player has used too many cheats on it, and possibly rendering the save file unplayable and the game permanently damaged. Game freezes are often accompanied by an odd buzzing sound; however, sometimes the normal music for wherever the player was before the game froze can be heard. Frequently, a loop or constant replay of whatever sound was being played prior to the freeze will be played. Sometimes, a freeze will play no sound, even if there was a sound being played before the freeze. Some game freezes are also accompanied by opcode errors when playing with an emulator, meaning that the game gives incorrect or impossible instructions to the hardware of the device, effectively crashing the game.
The game may occasionally freeze while playing any Generation III game, when a player's Pokémon uses Thunderbolt or Thunder, or when fleeing from a wild Pokémon, though cases of the glitch actually occurring are exceedingly rare. The problems caused by the glitch occurring can be rectified by turning off the game's battle animations. The moves only cause a temporary repeat of the sound, and it will go away if the Pokémon taking the damage is defeated.
If the game is dropped, hit by any major force, has a dirty game cartridge/card or physically removing it from the slot may also cause the game, no matter what the generation to freeze.
|
This glitch-related article is a stub. You can help Bulbapedia by expanding it. |
|
This glitch Pokémon article is part of Project GlitchDex, a Bulbapedia project that aims to write comprehensive articles on glitches in the Pokémon games. |
