>> RU | Русский

Common tricks

"This is a sparring program. Similar to the programmed reality of the Matrix. It has the same basic rules – rules like gravity. What you must learn is that these rules are no different than the rules of a computer system. Some of them can be bent. Others – can be broken." ― Morpheus, The Matrix
There are several tricks that can be used (or at least tried) in many games to improve the time. If you are making a movie, be sure to try every one of them. Otherwise, try finding your own.

Unintended things abuses

Abusing untested code

TODO: More about untested code.
Untested code is a primary source of game glitches.
Untested code is not always helpful. For example, in Battletoads there's one level that is impossible to complete with two players because the game testers never actually tried the level with two players. The game was published containing a serious programming error that prevents the second player from moving (and resulting in his immediate death) in the Clinger-Wingers level.

Abusing erroneous assumptions

Due to limited processing power, old console games often make erroneous assumptions to reduce the number of calculations the game has to make. Sometimes these errors are just a result of programmer oversight.

Many interesting examples exist, such as:

Abusing side-effects of pause

In some games, pausing has unintended side-effects due to programmer oversight:
It might be worthwhile to observe what other anomalies are caused by pausing in your game.

Overlapping different game logics

Monster damage abuses

Monster "damage boost" abuse

It is common for games to be designed so that the character can't reach certain paths or platforms, but just barely. Designers often overlook the boost monsters provide when they hit you. By getting hurt at the right place and the right time, you can get monsters to boost you into places you normally shouldn't be able to go.
In some cases, taking damage sends the character in a direction neglecting obstructions due to oversight of the developers. This can be abused for creating unintended shortcuts.

In some cases, taking damage from powerful attacks flings the character at speeds faster than normal. If planned, this can send the character in the direction desired and save time. Super Castlevania 4, Legend of Zelda, Link's Awakening, and Kirby Superstar are examples of this.

In some cases the damage causes the character to retain that speed as long as he doesn't stop. In the video example here, Adventure Island 4, the character is able to retain a super speed boost for a strikingly long period of time. See also frame window abuse.

Invulnerability abuses

Most games contain some situations where your character is immune to harm.

Event invulnerability abuse

Often, when the game has started a scripted demo that may not be interrupted, like the animation for finishing the level, your character becomes invulnerable. If you touch something lethal during this state of game, the game may very well ignore it. The Little Nemo and Gremlins 2 movies have examples of this. In many games, such as Umihara Kawase and The Wrath Of Black Manta, lethal object collision checks are ignored when entering a door. In Mega Man 2, these checks are ignored when changing weapons.

Stun invulnerability abuse

In many games, if you take damage you will flicker for a while and temporarily become invulnerable, to prevent you from immediately taking more damage. This invulnerability can often protect you from "instant death" hazards, for example, allowing you to safely walk on deadly spikes or lava for the duration of the flickering. The Mega Man 4 and Blaster Master movies have examples of this.
It may also be advantageous to use such a period of invulnerability to pass through monsters that would otherwise take longer to destroy, or to pass through other nearby monsters that would do more damage. The Goonies movie is an example of the former, while Castlevania: Circle of the Moon movie is an example of the latter.

Avoid countdowns

Games often end levels with a score count down screen. The time spent on those screens count as well and should be minimized by causing the underlaying value to be as optimal as possible without losing speed. This usually means avoiding to collect items and having the correct amount of health at the end of the level.

Extraordinary gameplay

Abusing death and Game Over

While it may seem contradictory with goal to do things as fast as possible, it does not have to be. Games commonly reset the player position when the player dies, leading to possible shortcuts. Your health often also set to a known number and you may lose or gain items.
In games with multiple players, this can be used to change the amount of player interaction, for example dead players in an RPG will not get asked for their commands. Dead party members can also act as a form of party change, possibly affecting scripted events that depends on who is in the party.
In multi-player games, one player may be able to die to take advantage of a favorable spawning. The video example to the right demonstrates this idea in Level 5 of Super C. The two players continually die in order to spawn at the top of the screen to save time.
This can all be abused to save time. Submission doing this are marked with the category uses death to save time.
TODO: abusing Game Over.

Avoiding saving

It often takes several seconds to manually save the game and is rarely needed in a TAS movie. Similarly, turn off auto-saving.
However, in many games, you can take some advantage, such as to warp back to an earlier position in the level, reset character status, etc. when you load a saved game. It is recommended that you study what consequences can happen after saving the game.
There are some situations where the act of saving has an extra benefit that can save time, such as restoring player resources or setting an area to a specific state. In Alwa's Awakening: The 8-Bit Edition for example, lighting a save torch room costs a few frames but also fully restores the player's health which can be later spent for damage boosts that save much more time.
TODO: another example of taking advantage just from saving the game?

Reset the game, keep the sram

Game consoles have reset buttons that restart the game from the beginning of the program. This may seem like an obvious suboptimal move, but at times it can be faster to reset the game after saving than continuing with the game. The most common example is letting the game save after finishing a level, but skipping the following cutscene.

Reset the game, do mind the sram

Writing the save is a sensitive operation. As games often say "Don't turn off the console" during saving, ignoring this advice often leads to corrupted saves. Usually the result of a corrupted save is that the game refuses to load the save afterwards. But with careful timing and some luck it's possible to create a corrupt save that the game does accept loading. This can lead to major glitches and subsequent sequence breaking.

Input abuses

Two or more actions at once

Try to make some input that most probably hasn't been tested, like pressing left+right or up+down at the same time, or use multiple input devices like gamepad+touchscreen simultaneously. It might have bizarre and useful consequences. See the Zelda: ALttP and Zelda 2 glitch runs for examples of this.
(Note that some emulators (such as VirtuaNES or old versions of Snes9x and FCEU) don't allow you to press right+left or up+down. The consoles themselves have no such qualms, though you usually have to press very hard on your controller to press in two opposite directions at once.)

Frame window abuse

In some games, there are short periods when you can make valid game input while you are not supposed to do so. Catching such an opportunity might either merely allow you to act earlier, or do things unintended by the developers.
TODO: Another typical example with a different outcome.

Alternating buttons

Often, you need to press a button to dispose of some dialog box, or to start the game, or something similar. When two buttons can be used to activate the same goal, you can press them like this:
A, B, A, B, A, B, A, B, etc.
so that a button is effectively pressed every frame. It doesn't save actual time in the movie, but it saves time making the movie, because you don't need to test for the earliest possible frame every time. Some emulators (such as VBA and Snes9x) let you put A and B on autofire starting at different frames to automatically press this sequence of buttons, which is even less effort for you.
Sometimes a game will actually accept the next input every frame, in which case it does actually save time in the movie compared to pressing one of the two buttons as early as possible each time. Also, some games might have been designed not thinking it's possible to press buttons so fast, and strange things may happen as a result.
Be aware that hexediting may be more cumbersome if you use this technique. It may be difficult to determine the exact frame where the input affected the game.

Super speed abuse

When you act inhumanly fast, like pressing a button 30 times a second, you might be able to do things that the game developers would never have thought possible.

Outrun the game

You can often catch the game unprepared if you move at extreme speeds. This means that the game may not have had the time to prepare itself for you being at that point. This means in practice that objects that should be there may not have been created yet. Depending on your exact situation this may be a blessing or a curse.

Not on camera? Not there!

Games frequently cheat by only updating objects that are near enough to the camera. If you can somehow outrun the camera you might be able to ignore objects that would otherwise impede your progress.

Fast motion collision abuse

Games almost never interpolate motion between frames. This means that you are in one place on one frame, and in some other place on the next, without actually having traveled the path between them, like we do in the real world. This is how animation works.
If you are moving very fast, you can sometimes pass through objects because the game does not render a frame when you are inside the object. Combined with the close approach collision abuse mentioned above, the speed may not even need to be very high.
The example shows Gradius collision abuse. Due to the extreme speed, the ship is able to fly through narrow pieces of ground that would normally destroy the ship.

Collision abuses

Close approach collision abuse

Most games don't do pixel-perfect collision checks. The character's and enemies' sprites (the graphics that you see on-screen) have unusual shapes, while their "hit-boxes" are usually actually square. Games are programmed this way because it’s much easier to program "is the character's box touching the enemy’s box" than it is to program "is any pixel of the character’s graphic touching any pixel of the enemy's graphic."
In some games, the hit-boxes are actually bigger than the sprites, and you can get hit by an enemy before it seems like you should. In a lot of games, though, the opposite is true: hit-boxes are actually smaller than the sprites, so you can seemingly touch or even go partially inside enemies without getting hurt. The SMB1, SMB2, and Solomon's Key movies have many examples of this.

Diagonal movement between tiles

Some games check what tile character is on by just checking one point. This may make it possible to pass diagonally between tiles, sometimes useful to get past tiles that are deadly or otherwise harmful.
Example of this applied to Jetpack: http://www.youtube.com/watch?v=EjTNYr7J_DY

Other collision abuses

By various methods (such as pushing into corners in strange ways or getting shoved by an enemy) you may sometimes manage to get embedded into the floor, walls, or ceiling. Sometimes when this happens you just get stuck and your game is ruined, but other times it might allow you to make use of new routes that weren't possible before. For example, you might be able to gain support and jump from a wall. The SMB1 and SMB2j movies have examples of this.
In most games, collision calculations are very simple. As mentioned earlier, because motion is not interpolated, sometimes you can go through enemies or walls if you are traveling fast enough or along an odd enough trajectory. With respect to walls, most games account for this by very quickly ejecting you from the wall to prevent you from getting stuck. Sometimes, you can trick the game into ejecting you in the wrong direction, which is how walls are initially walked through in SMB1. In other games, wall ejection moves your character at high speed in one direction (usually horizontally) until the game finds a place where you can exit the wall. This is most useful when you can force the game to shoot you off at high speed along your desired path! In Mega Man and Mega Man 2, even ceilings eject you horizontally, which is why the authors of those movies often perform various antics that result in Mega Man being embedded in the ceiling.
The image on the right shows a classic example in Super Mario Bros (the famous wall glitch that allows entrance into -1)

Jumping off ledges

The speed of playable characters in most games, especially platformers, is nonlinear. This is usually done in form of acceleration: the longer the character moves in a certain direction, the higher their velocity is. Similarly, the longer they fall, the faster they reach a platform underneath the starting point, so it's often preferable to jump shortly before the edge of the platform. Avoid the temptation of running off and falling normally, because often the character will have little-to-no downward velocity for a short period (unless, of course, you need it that way).
Note: Some games have drastically reduced aerial speed. For them, it's usually preferable to do very short jumps only a couple frames before reaching the ledge, or to not do any jumps at all. Be sure to study the physics of the game you're working on well, don't hesitate to use Memorysearch to find exact values for character's speed.

Subpixel carryover

This is extremely common in NES games (and less common on platforms such as DS and GBA). Regardless of platform it should be looked into for any game.
The subpixel value represents a fraction of a pixel. It is used to calculate how many pixels a character moves in a frame. Often at the end of a level/room, the remainder of this value is not cleared. This means the value left over will be used on the next level/room. When possible a high value should be left in a level to give the character a tiny "head start" in the next level.
Note: Subpixel variation is a common source of desyncs when copy/pasting movies. In games with subpixel carryover, the subpixel values should be aligned before copy/pasting.

Subpixel Inheritance

Games often use subpixels for objects other than the player character, such as enemies. Games also often reuse memory used to store active objects as objects spawn and despawn. Combine these two facts with sloppy initialization and objects will inherit the subpixel values of whatever occupied the memory before. This can be the subtle nudge the object needs to be at the exact right position.

Luck manipulation

Video game consoles are computers. They do exactly what they are told, and will always give the same result when given the same input. There is nothing that is truly random. The only source of true randomness in games is you! Games are purely deterministic and depend solely on user input.
Learn to abuse this fact. You can affect anything that has an element of randomness in it, like monster movements or item drops.
Read more at LuckManipulation.

Lag Reduction

The processing speed of old console systems is limited. They can only handle so many objects per frame. If there are too many objects on screen at one time, the game slows down, because it just can't calculate everything in one frame.
Knowing the cause of this phenomenon is important when making a TAS. Often this lag can be minimized by keeping the number of on-screen objects low, either by destroying them early, or perhaps not destroying them to prevent an overly complicated (and processor intensive) death animation from playing. Luck manipulation can be useful here, too. In some games, whether or not a monster spawns is random.
On-screen objects are not the only cause of processor use. Some actions require more calculation than others. For instance, being close to enemies, or collecting or using certain items may cause the game to lag.
Often lag can happen for unknown reasons, sometimes doing a slightly different strategy which doesn't cost time can prevent the event from occurring. In this instance a Memorysearch might help to reduce it

Corrupt memory and save data

The game uses the memory to know what you have done, what you are doing and what you have left to do. If you somehow gain the ability to directly edit memory you have effectively won.
Slipping some wrong values into wrong addresses you can command a game to do arbitrary things. But that requires deep disassembling of the original game code, expert knowledge.

Game options

TODO: Examples.
Many games provide game options for you to modify how the games work. It is recommened always to try them out to see if you can save time with certain settings.

Text speed

Some games allow you change how fast texts are displayed and fading out. Setting the text speed to the highest level usually saves time, and it is worth trying even if you can skip the texts, because sometimes you might be unable to skip them as quickly due to input limitations.

Movement/battle animations

In some role-playing and strategy games, you can turn off or choose simplified versions of movement/battle animations. Choose the fastest way.

Demos and cutscenes

Although you are likely to be able to skip them with input if the game provides such options, it might be faster to disable them just at all.

Difficulty level

In general, we prefer movies done on the hardest difficulty provided that they demonstrate the best superhuman gameplay, but there are cases where lower difficulty may allow even better demonstration and we prefer that.
Note: In some games, you can access some extra items, stages, bosses and/or achieve some hidden endings if you are on a certain difficulty, which is usually the hardest one. Having this happening might interfere with your decided movie goals. So make sure that you have investigated the secrets in the game.


It is usually a waste of time to save the game in a TAS, especially when it is automatically done everytime. Turn the auto-save option off if you are allowed to, otherwise, avoid triggering it as much as possible.

Date and time

In many games, these settings affect the randomness in the games. See also LuckManipulation.
In some games, when the date and/or time matches with a particular value, some secret game material become accessible.

User profile

Typically in many, but not limited to, long games featuring the save and load function, you are often asked to create a user profile before you can save, which usually contains some informations such as your or your game character's name, gender, birthday and so on.
It is usually a good idea to keep the informations as short as possible so that you can spend least time in creating the profile or having the informations cited during your gameplay. In some games, however, the informations in your profile may have deterministic or random effects on the gameplay and you may accordingly manipulate them to be in a favourable way.

How to find out tricks

Study existing materials

Game walkthroughs, FAQs, forum posts, email letters, IRC remarks, etc. If you find or suspect that the game you are TASing has an engine similar to another game that has already had a TAS submitted, check it out to see if particular tricks or glitches used in it are applicable to your game as well.

Examine game data

Read the program

All games are programs in some form. While they are intended to only be executed by the game system, there is nothing stopping you from reading the program instead. While the program code is most likely not very easy to read, it is the exact rules that the game is made out of.
The best way of understanding the rules is to simply read them and figure out exactly what they mean. You can check exactly how the random number generator works or simply why the player character (supposedly) can not move into walls.
This is a very difficult thing to do, it is recommended that you know how to program before you attempt this. This is not normal programming, but on a lower level. You will need to actually understand the instructions that are given to the processor and not what the programmer may have written.

Read the script

Many games, especially ones with plot, have their own script engines. It commonly controls important events such as when you can go somewhere and how enemies behave.
Learn how the script engine works and examine what the game script does. It can have flaws just like the main program. But most importantly, it allows you to understand what your options are.

Examine the level data

Games frequently store important data right inside the level definitions. You can find all sorts of tilemap flags, trigger areas, enemy controls and more! Why waste time guessing where exactly things are when you can simply look them up?

Examine the data tables

Games frequently need to store large amounts of values for some purpose, be it the statistics for the items in the game, enemy health values, character statistic growth data or pre-computed math functions. There is no need to waste time hunting for values in memory when you can just read them all in one go.

Try things out

Simply try doing things that you aren't expected to do. Game developers forget about all the possibilities. It is your job to remind them what is actually possible.

See also

GameResources/CommonTricks last edited by feos on 11/11/2023 6:32 PM
Page History Latest diff List referrers View Source