This is an old revision of the document!


About

Ubiquitous cheats rely on exploiting the underlying technology rather than exploiting game code and should be universal enough to be used in any games, including online games.

CPU Hogging

A CPU jammer software can be created that will overload the CPU with, say, computationally difficult to solve problems, thereby achieving a lag effect. The lag can then be leveraged to get through portions of games that require (too) quick reflexes.

This cheat can be achieved through hardware for handheld consoles, such as the Gameboy DMG variable oscillator mod, by simply replacing the oscillator with a half-frequency oscillator for half speed.

Perhaps the most attractive part of this ubiquitous cheat is that, depending on the task within the game, the cheat should work for massive multiplayer online games too - or rather, games that require Internet connectivity (Punkbuster) since such games allow a certain tolerance threshold before the game considers the player to have a severed connection.

Rolling Back Saves

One of the oldest trick in the books is to use the Save & Load feature of games that require you to pass a test before proceeding on with the main storyline. The principle is easy to comprehend: save when you win and load when you lose.

For instance, this cheat works wonder in Leisure Suit Larry 1 - The Land of Lounge Lizards when the player is supposed to obtain a certain amount of cash to continue the adventure by playing poker. DeusEx or Fallout hacking sequences can also be similarly defeated ensuring that no time is lost. Passing speech tests in RPG games can also be ensured to succeed with the same technique - even when the odds are against the player (in which case the average number of retries can even be computed).

This cheat is unbeatable unless the game forcibly autosaves after every failure of a minigame.

Manipulating Screen Colours for a More Favourable Palette

Most games allow changing settings such as brightness, contrast or screen gamma - the latter setting is typical of console games where the game asks you to move a slider till an image can be "barely seen". Most of the time, the darkness works to your disfavour and various game elements (such as items, or clues) will be hidden in darkness. Cranking up the gamma or manipulating the brightness can avoid a lot of trouble with finding the hidden clues.

The procedure can range from messing with basic tools such as NVidia control panel or perhaps more advanced tools such as SweetFx / Reshade to remove or enhance graphical elements.

Similarly, a lot of games sometimes have a calibration phase where the player is requested to move a slider till some image is "barely visible" - a request that can be completely disregarded and the player can just slide towards the end of the slider that makes the image entirely visible. Usually games that have such built-in calibrations will also require the player to pixel hunt down the line such that following the instructions to reduce the brightness is just a way for the player to shaft themselves.

Using Macros

Macros can help overcome repetitive tasks and some macros are more advanced than others - there are typical hardware solutions such as mice or keyboards with built-in macro features but more than often you will need some advanced scripting. Examples include:

Autofire

Autofire can be implemented for any mechanical button - even for desktop computer keyboards by using a timer circuit such as the NE555. The obvious advantages are bypassing button mashing sequences in games or perhaps some form of auto-run in FPS games.

Exploiting Scene Geometries

Some game props, particularly walls, are sometimes set to be phantom such that they do not comport themselves as a physical object in order to reduce the load on the physics engine. Usually such walls or boundaries (even other objects) are placed in "difficult to reach places" where the developers did not anticipate players to reach. However, sometimes players do manage to reach these difficult places by either:

  • performing jump combinations,
  • using skills or other physical objects to propel them

This usually results in the player being able to take shortcuts, for instance, by walking through walls thereby bypassing the intended geometry of a scene.

One such example is the Hobo: Tough Life wall exploit where a player can use physical props (in this case, a fence) to break through a physical wall. Similarly, just by jumping around, phantom walls can sometimes be found allowing players to escape the geometry.

Cut Scenes

Cut scenes in games represent moments when the game re-arranges the scene. This implies that states that were there previously are either halted during the cut scene or entirely removed. That being said, it is sometimes possible to escape a difficult situation if the player just manages to trigger a cut scene.

For instance, Guild Wars 1 only registers a quest hand-in when an NPC is reached. Even if the NPC is on the battlefield, then the quest completes and the enemies vanish. Other examples include games where the enemies will just be suspended and not deal any damage whenever a quest NPC is being talked to.

Similarly related is saving the game that sometimes implies that the game will be halted for a few moments. Some games save whilst additionally displaying a cut scene, in which case, the game will most likely be interrupted for the duration of the cut scene.

Being "Good"

With unbelievably few exceptions, games are rigged for the player to act with a "good" alignment. This is either because being evil is not a fully developed branch but most of the time this is because "evil" is self-destructive. One cannot be, truly evil since evil is self-defeating.

For instance, even if Dungeons & Dragons (in its computer game form) allows a player to be chaotic evil, it is still impossible for that player to be truly evil and additionally finish them game - simply killing off a story-related NPC will not allow the player to progress; otherwise, the key NPCs will have to be made invincible. Dungeons & Dragons in its pen and paper form would imply a DM that can use divine intervention in order to prevent a player from messing up the game but a computer would not anticipate, say, killing off a team member or killing off a key NPC since the decision branch would be way too large.

Examples such as Tryranny are equally sensitive - in Tyranny, "evil" might be implied by the story but not necessarily by player actions. Player decisions, may be political where some choice may lead to consequences that may be considered "evil", but the player is still restricted to doing what they are told (regardless the side).

Most of the other RPG games such as Fallout imply a "good" playthrough where the player essentially gets rewarded for being "good" and punished for being "bad". Ie: rewards are given to completing quests, not rejecting them, NPCs offer goodies and killing them off results more than often in no loot at all, etc.

Winning a game, without any other additional information, would imply a "good" playthrough as a best guess, since statistically it is the choice that most games prefer.

Pathfinding Exploits in Role Playing Games

In role playing games players meet computer-controlled opponents in a given environment in order to do batte. One of the programming problems is how will the computer-controlled opponents pick a target and that is conventionally solved via something called the "threat tables" (computeristically, a priority queue): a table is constructed by the software ranking every player by the amount of threat they generate and the computer picks players in descending order by their threat ranking. Implicitly, since the computer controlled opponent(s) must attack a certain player that has been selected, the computer must then generate a "physicial" path to the selected player, in case the attack type is melee. In doing so, the computer-controlled opponents must traverse both the environment and will also avoid other players in order to reach a given player. The algorithm can be grossly approximated as follows:

  • generate a threat table, perhaps based on attack power of all players and previous history of attacks,
  • pick the top-most player,
  • move to the player,
  • attack the player
  • loop at the first step

One common trick is to perform a "body-block": a "body-block" is usually performed by a player on the lower levels of the threat tables that moves within the environment and attempts to block the computer controlled opponent just by standing in the path of the computer-controlled opponent; the player usually uses their intuition to guess the path that the computer-controlled opponent will pick.

The effect of a "body-block", sometimes in very severe cases, is to confuse the AI so bad that the computer-controlled opponent will just never reach the player that it must attack. In doing so, the player and the computer-controlled opponent dance across the environment whilst the rest of the players in the party attack the computer-controlled opponent from afar. In case one of the players attacking the computer-controlled opponents from afar will generate sufficient threat in order to surpass the player blocking the computer-controlled opponent, the players will either change roles or the player performing the body block will attempt to generate threat back in order to maintain their position on top of the threat table.

One example of performing body-blocks can be found in:

  • Star Ocean - one of the players equips an item named "Bunny Shoes", granting extra speed and is able to run around, blocking the computer-controlled opponents that will ignore the player performing the body block and turn and twist trying to generate new paths towards the players generating threat.

The technique can sometimes be combined with the environment, ie: attempting to make computer-controlled enemies end up stuck behind items in the environment such as rocks, hills, trash and others, perhaps even related to exploiting scene geometry issues where players attempt to make a computer-controlled opponent fall off some platform or ledge.

A somewhat similar and related technique is called "kiting" which involves one player generating sufficient threat in order to race a computer-controlled opponent trying to reach them. One example of "kiting" can be found in "World of Warcraft": some funny situations include an event where one player managed to drag an extremely high level boss into a starter city with low level players and just watch the ordeal unfold:

A more useful example of implicit "kiting" is performed by just two players, Incantatrix and Melchior in Scholomance, a high level 5-person dungeon using just two mages.

In this case, the "kiting" performed is implicit since the only way to survive the overwhelming amount of foes (for a 5-person dungeon, done by 2) is to oscillate between the two players and confuse the AI such that the foes will bounce back and forth from one player to the other. At 1:46m in the movie, both players hide behind a doorway that makes enemies have to recompute the path and start walking towards the doorway, the other player generates some threat and does the same, effectively exploiting the line of sight (LOS) and confusing the mobs. This is one example where the "kiting" involves the environment as well as the players.

Back at the time, a two-people party was considered impossible, especially given the party configuration since mages are cloth wearers, take lots of damage, deal in return lots of damage and thereby generate a lot of thread and are generally not designed as characters to be on the front lines.

Perhaps one of the most prominent and perhaps irreducible but not directly related examples would be the classic Pac Man exploit as explained by Retro Game Mechanics Explained (originally at https://www.youtube.com/watch?v=ataGotQ7ir8):

Although not a "body-block", nor "kiting", the Pac Man exploits are based on the limitations of old-era platforms where a developer "fix" was introduced in order to prevent a buffer overflow condition that resulted in some distinct patterns being generated by the ghosts in Pac Man. The patterns are then leveraged by the user in order to confuse the AI into either avoiding the player altogether, effectively reaching a stale-mate (or a deadlock) where the game can run indefinitely without the player losing. Or, the patterns can be used to exploit the game such that the user always wins.

Both techniques, "body-blocking" and "kiting" are not even considered "cheats", even though they exploit the underlying AI algorithm in order to gain an advantage, but they are, in fact, considered to be player tactics. In many ways, the critique would be unfounded since both techniques do require a lot of player skill - kiting or attempting to body-block high level enemies with rapidly reordering threat tables is very dangerous to a player - in the World of Warcraft example presented in the video above, "Grindpa" from the "Khadars Rage" guild kites a very high level computer-controlled enemy "Kazzak" into a starter area but the process of doing so must have been painstakingly difficult and would have required an insane amount of skill. Kazzak is considered a world-boss, of unknown level and the player must have dragged the boss across at least three distinct regions to get to Stormwind (Azeroth → Eastern Kingdoms, from Blasted Lands to Stormwind). Similarly the maneuvers performed by Incantatrix and Melchior were considered impossible given the design and constraints of the game.


fuss/ubiquitous_game_cheats.1596205613.txt.gz · Last modified: 2020/07/31 15:26 by office

Access website using Tor Access website using i2p


For the copyright, license, warranty and privacy terms for the usage of this website please see the license, privacy, data protection and copyright compliance as well as the plagiarism pages.