Game freeze: Difference between revisions
Blueapple128 (talk | contribs) No edit summary |
Blueapple128 (talk | contribs) m (→"Softlocking") |
||
Line 20: | Line 20: | ||
Certain [[glitch]]es do not cause the game to outright crash ('hard' lock), but rather cause the game's code to form an infinite loop, preventing any of the player's inputs from being processed. Examples: | Certain [[glitch]]es do not cause the game to outright crash ('hard' lock), but rather cause the game's code to form an infinite loop, preventing any of the player's inputs from being processed. Examples: | ||
* In Generation I, a [[level]] 1 Pokémon using {{m|Psywave}} will cause the game to softlock, as the game attempts to generate a random amount of damage greater than 0 and less than 1.5 × the user's level (rounded down). No such number exists, preventing the game from continuing. | * In Generation I, a [[level]] 1 Pokémon using {{m|Psywave}} will cause the game to softlock, as the game attempts to generate a random amount of damage greater than 0 and less than 1.5 × the user's level (rounded down). No such number exists, preventing the game from continuing. | ||
* In [[Kanto]]-based [[core series | * In [[Kanto]]-based [[core series]] games, before obtaining the [[Boulder Badge]], a person blocks the path out of [[Pewter City]] to {{rt|3|Kanto}}. In [[Generation I]] games (except {{v2|Yellow}}), a glitch allows the player to bypass this person and then talk to him from the right side, an action the developers did not anticipate. As the path the person walks is dependent on the side the player talks to him from, the game attempts to look up a path based on the player's coordinates; since the path in this caes is nonexistent, the game will never find it and will not continue. | ||
{{-}} | {{-}} |
Revision as of 00:39, 5 February 2015
- Freezing redirects here. For the status condition, see Freeze (status condition).
A game freeze occurs when the data completely stops flowing to the system, 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 file.
Causes
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 incorrectly. Older cartridges and systems are also more prone to freezing than newer ones.
The most common cause of a game freeze is the game being given too many tasks at once. For instance, there is a higher probability of the game freezing when the player tries tweaking.
Incorrect cheat codes used on cheating devices such as Action Replay or GameShark can result in game freezes. On rare occasions, incorrect cheats may possibly render the save file unplayable and 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. In very rare cases, the music (and not the remaining sounds) can be the only thing to freeze, leaving the game still playable. Sometimes game freezes are accompanied by garbled sprites or various vertical lines.
The game may occasionally freeze while playing some copies of Ruby and Sapphire when a player's Pokémon uses Thunderbolt or Thunder, or when fleeing from a wild Pokémon; however, cases of the glitch actually occurring are exceedingly rare. The problems caused by the glitch occurring can be rectified by turning off the battle effects. The moves only cause a temporary repeat of the sound, and it will go away if the Pokémon taking the damage is defeated.
The game may also freeze if it is dropped, hit by any major force, has a dirty game cartridge/card, has been physically removed from the slot, or even if it is played on a faulty system (such as a Game Boy Color with low battery level). Game freezes are not limited to handheld systems, and it is possible for some home consoles to freeze up during gameplay.
"Softlocking"
This is incomplete. Please feel free to edit this to add missing information and complete it. Reason: newly created section, needs more examples and sources |
Certain glitches do not cause the game to outright crash ('hard' lock), but rather cause the game's code to form an infinite loop, preventing any of the player's inputs from being processed. Examples:
- In Generation I, a level 1 Pokémon using Psywave will cause the game to softlock, as the game attempts to generate a random amount of damage greater than 0 and less than 1.5 × the user's level (rounded down). No such number exists, preventing the game from continuing.
- In Kanto-based core series games, before obtaining the Boulder Badge, a person blocks the path out of Pewter City to Route 3. In Generation I games (except Yellow), a glitch allows the player to bypass this person and then talk to him from the right side, an action the developers did not anticipate. As the path the person walks is dependent on the side the player talks to him from, the game attempts to look up a path based on the player's coordinates; since the path in this caes is nonexistent, the game will never find it and will not continue.
This article is part of Project GlitchDex, a Bulbapedia project that aims to write comprehensive articles on glitches in the Pokémon games. |