100
edits
GameShark: Difference between revisions
m
no what is that doing there
HyperHacker (talk | contribs) (→Criticism: new section) |
HyperHacker (talk | contribs) m (no what is that doing there) |
||
| Line 20: | Line 20: | ||
==Unintended side-effects== | ==Unintended side-effects== | ||
If a code is incorrectly entered, the game may give the player a [[Bad Egg]], rewrite the Bag contents, freeze the game, corrupt or delete a Pokémon, corrupt the Hall of Fame data, or simply corrupt the save file. These occurences may also occur at other times. In other situations, nothing unintended may occur. | If a code is incorrectly entered, the game may give the player a [[Bad Egg]], rewrite the Bag contents, freeze the game, corrupt or delete a Pokémon, corrupt the Hall of Fame data, or simply corrupt the save file. These occurences may also occur at other times. In other situations, nothing unintended may occur. | ||
==Criticism== | |||
The GameShark was widely criticized for its poor construction and software quality. The Game Boy Color and Nintendo 64 models had a bare cartridge connector instead of a slot, so cartridges could be easily jarred out of place during play. The software used buggy and incorrect methods of writing to its internal memory, which caused it to occasionally corrupt the code list or the software itself and could render the device unusable. The case was made of thin plastic and fell apart easily. | |||
Additionally, the devices left the flash memory chips fully accessible to games, which allowed them to easily detect and even erase the GameShark. No games are known to tamper with it, however most N64 games included routines that would prevent the game from running or erase save files if a GameShark was detected. While these routines can be detected and removed automatically, the GameShark did not make any attempt to do so. | |||
==Related articles== | ==Related articles== | ||
| Line 36: | Line 42: | ||
[[ja:プロアクションリプレイ]] | [[ja:プロアクションリプレイ]] | ||