TAS Tricks - Revision history

Nxcy at 02:57, 15 May 2026

2026-05-15T02:57:07Z

← Older revision		Revision as of 02:57, 15 May 2026
Line 134:		Line 134:
	Consider the following example in 2-2. I would like to WJ on the pole to the right.		Consider the following example in 2-2. I would like to WJ on the pole to the right.

	[[File:2-2.png\|400px\|2-2_wall_jump]]		[[File:2-2_pole.png\|400px\|2-2_wall_jump]]

	I first ran into the pole and found that X = 2256. My aim is thus 2259. I found from simple trial and error that executing <>>> on frame 158 in my movie was the last frame that achieved a speed of 816. My goal is thus to execute <>>> on frame 159 and slow down so that I can still achieve 816. My final set of inputs looked like this		I first ran into the pole and found that X = 2256. My aim is thus 2259. I found from simple trial and error that executing <>>> on frame 158 in my movie was the last frame that achieved a speed of 816. My goal is thus to execute <>>> on frame 159 and slow down so that I can still achieve 816. My final set of inputs looked like this

Nxcy: Copied wall jump guide

2026-05-13T02:28:44Z

Copied wall jump guide

← Older revision		Revision as of 02:28, 13 May 2026
Line 93:		Line 93:

	Note that this might not always be the optimal way, its just a consistent way to save rerecords.		Note that this might not always be the optimal way, its just a consistent way to save rerecords.

			'''Practical wall jump guide'''

			Note:
			* “speed” refers to horizontal speed, measured in sub-pixels per frame and presented here in decimal. Sorry for those who prefer hexademical, but I learnt how to TAS before I knew what a hexadecimal was.
			* Most of the numbers here assume that Yoshi is moving to the right with an average speed of 760. The principles all apply to other speeds though (e.g. 767).
			* If Yoshi is moving to the left, then just mirror everything.

			To perform a wall jump (WJ), Yoshi must move 3 pixels (256*3 = 768 sub-pixels) into a wall. This causes Yoshi to enter a “standing on the ground” state for one frame, during which it is possible to jump. Yoshi therefore needs to attain a high speed (>768) on a frame where he is very close to the wall. More precisely, if Yoshi has speed V while at a distance D away from the wall, then we need V > 768 + D. Wall jumps can also only be performed at vertical tile boundaries, which occur every 16 pixels. The conditions on Yoshi’s vertical position, however, are much more relaxed. As long as Yoshi is reasonably close to a tile boundary, he will “snap” to the correct position, provided that the horizontal condition is met.

			Achieving a large speed for a single frame is easy. If Yoshi is running at 760, then the input sequence <>>> produces a frame with a speed of 816, which is more than enough for a wall jump. More generally, this large speed will be 56 higher than Yoshi’s average running speed. The challenge is making D small enough, which requires precise control of Yoshi’s speed as he approaches the wall.

			The simplest and most common scenario is when Yoshi approaches a wall at full running speed from far away. This case is the easiest as there is a lot of time to adjust Yoshi’s speed before he hits the wall in order to minimize D.

			First, run into the wall and note what horizontal position (pixel, not sub-pixel) Yoshi is at when he stops. We will call this X. Whatever it is, we need Yoshi to reach X+3. For example, if Yoshi stops at 1430, then our goal is to get to 1433.

			Now approach the wall for real. I recommend jumping early and releasing > so that Yoshi’s speed is fixed at 760. If you’re aiming to wall jump high on the wall, time the jump so that Yoshi hits the wall at roughly the apex of the jump. The exact height of the jump can always be altered later.

			Find the last possible frame (we will call this frame N) on which the sequence <>>> achieves the speed of 816 (we will refer to 816 as V now). N is correct if doing <>>> on frame N+1 doesn’t attain V. If you are very lucky, executing <>>> on frame N will reach X+3. In this case you already have a WJ and don’t need to do anything else. You should see Yoshi enter the standing animation for one frame. If you don’t see this, it means your vertical positioning is off and you should adjust your jump. The simplest way to do this is just to try releasing B on different frames.

			In the majority of cases, doing <>>> on frame N will not reach X+3. Instead, it will usually reach X+1 or X+2. In any case, it means that D was too large. Since you can’t move any faster (if you could have, why didn’t you already?) the only option is to slow down. The goal now is to slow Yoshi down by as little as possible so that the sequence <>>> achieves V when executed on frame N+1.

			Go back to the start of the jumping approach with > released and Yoshi’s speed locked at 760. The goal now is to try slowing Yoshi down by different amounts and checking if executing <>>> on frame N+1 achieves V. Note that achieving V doesn’t guarantee the WJ, as it is possible to slow down too much so that D is now too large again. You'll know if this is the case or not by monitoring Yoshi's position: remember we're aiming for X+3. It is required that we slow down by as little as possible, so that achieving V from <>>> on N+1 only JUST occurs and would not have occurred if Yoshi had slowed down even a little bit less. In reality there is a bit of leeway, but this is the mindset you should have.

			There are two simple ways to slow Yoshi down. For very fine adjustments, press > for a single frame during Yoshi’s approach. After a few frames, his speed will settle on the lower of the 3 usual oscillating values (744 if his average speed is 760). You can then coast at 744 for as long as needed, effectively losing 16 sub-pixels each frame relative to coasting at 760. To get back to full speed, simply press > again.

			If you need to slow down by a larger amount, you can instead use any of the following input sequences (the number of the right shows how many sub-pixels they lose relative to coasting at 760):

			<> = -56<br>
			<_> = -112<br>
			<_ _> = -168<br>
			<<>> = -224<br>
			<<_>> = -336<br>
			<<<>>> = -504<br>

			An underscore _ denotes a frame with no directional input. These sequences have the property of bringing Yoshi back to speed 760 at the end. Other similar sequences probably exist, but I find these to be sufficient. They can be inserted during Yoshi’s jumping approach to the wall at any time and in any combination. You don't necessarily need to remember the numbers. Just remember the order of the list.

			A simple trial and error strategy might look like this: do sequence (6) enough times so that once more would slow Yoshi down too much. Then move to (5) and do that enough times so that once more would slow Yoshi down too much… and so on, working up the list, gradually getting closer and closer to the WJ condition. In practice it’s rare that you’ll need to use all of these. If you find that even (1) slows Yoshi down by too much, then you should instead use the 744 coasting strategy.

			Consider the following example in 2-2. I would like to WJ on the pole to the right.

			[[File:2-2.png\|400px\|2-2_wall_jump]]

			I first ran into the pole and found that X = 2256. My aim is thus 2259. I found from simple trial and error that executing <>>> on frame 158 in my movie was the last frame that achieved a speed of 816. My goal is thus to execute <>>> on frame 159 and slow down so that I can still achieve 816. My final set of inputs looked like this

			[[File:2-2 inputs.png\|300px\|2-2_wall_jump_inputs]]

			Frame 125 is where I began my jump and released >, locking my speed at 760. Frames 159-162 is the <>>> that achieves 816 to get the WJ. Note that I release B on frame 161. This is so that Yoshi actually jumps! Frames 134-143 are the inputs I added to slow Yoshi down. While they may look random at first, they are nothing more than instances of the fixed sequences discussed earlier. In particular, frames 134-139 are (6) from the earlier list, i.e. <<<>>>, and frames 140-143 are (5) from the list, i.e. <<>>. I found this particular combination of inputs as follows:

			First I tried using (6) once and found that this did not slow Yoshi down enough (I did not get 816).
			Then I tried using (6) twice and found that it slowed Yoshi down too much (I got 816, but I did not get a position of 2259)
			Then I tried adding (5) after one (6) and found that it worked.

			If this set of inputs did not slow Yoshi down enough, I would have tried adding a (2) after the (6)(5). Note that there’s no point adding a (4) or (3), as this would end up being at least as much slowdown as (6)(6), which I already know is too much.

			If (6)(5) slowed Yoshi down too much, I would have tried (6)(4), and then maybe (6)(3) etc.

	===Ceiling Clip Walljumps===		===Ceiling Clip Walljumps===

Brooklyn9d5 at 06:10, 4 May 2026

2026-05-04T06:10:59Z

← Older revision		Revision as of 06:10, 4 May 2026
Line 93:		Line 93:

	Note that this might not always be the optimal way, its just a consistent way to save rerecords.		Note that this might not always be the optimal way, its just a consistent way to save rerecords.

			===Ceiling Clip Walljumps===

Brooklyn9d5: /* 1/1 Running */

2025-04-16T19:27:02Z

1/1 Running

← Older revision		Revision as of 19:27, 16 April 2025
Line 35:		Line 35:
	The TASers at TASvideos decided to ban this trick for some TAS projects, keeping entertainment value in mind. This trick involves pressing < > every 2 frames after reaching the optimal speed oscillation, varying the speed between 2 numbers rather than 3, going 56 sub-pixels faster every 2 frames compared to just holding >...		The TASers at TASvideos decided to ban this trick for some TAS projects, keeping entertainment value in mind. This trick involves pressing < > every 2 frames after reaching the optimal speed oscillation, varying the speed between 2 numbers rather than 3, going 56 sub-pixels faster every 2 frames compared to just holding >...

	Doing this trick at 767 x-velocity would save about 3,5 frames every 100 frames.		Doing this trick at 767 x-velocity would save about 3.5 frames every 100 frames.

	Here are the comments regarding this trick in the 100% TAS:		Here are the comments regarding this trick in the 100% TAS:

Brooklyn9d5: /* Introduction */

2020-07-23T02:54:19Z

Introduction

← Older revision		Revision as of 02:54, 23 July 2020
Line 6:		Line 6:
	If you want to start TASing, you'll want to download this [http://www.mediafire.com/?z86e48e798bwhj8 .wch file] and open it with RAM watch in your emulator. This will allow you to see a bunch of important values like velocity and position, which will be used a lot while TASing. <br/>		If you want to start TASing, you'll want to download this [http://www.mediafire.com/?z86e48e798bwhj8 .wch file] and open it with RAM watch in your emulator. This will allow you to see a bunch of important values like velocity and position, which will be used a lot while TASing. <br/>

	Also check out the [[TAS_Guide\|TAS guide]] and the ~~YI page on~~ [http://tasvideos.org/GameResources/SNES/YoshisIsland.html TASVideos] for more info. specific to Yoshi! <br/>		Also check out the [[TAS_Guide\|TAS guide]] and the [http://tasvideos.org/GameResources/SNES/YoshisIsland.html YI page] on TASVideos for more info. specific to Yoshi! <br/>

	'''For the sake of clarity:'''		'''For the sake of clarity:'''

Brooklyn9d5: /* Introduction */

2020-07-23T02:53:53Z

Introduction

← Older revision		Revision as of 02:53, 23 July 2020
Line 2:		Line 2:

	=Introduction=		=Introduction=
	This is ~~a page~~ for TAS (Tool-Assisted Speedrun) tricks. Check out the ~~TASVideos~~ [http://tasvideos.org/WelcomeToTASVideos.html introduction page] ~~for more info~~ or this [https://www.youtube.com/watch?v=R3-ohYvi_fc video].		This page is for TAS (Tool-Assisted Speedrun) tricks. Check out the [http://tasvideos.org/WelcomeToTASVideos.html introduction page] on TASVideos.org or this [https://www.youtube.com/watch?v=R3-ohYvi_fc Youtube video] for more information on what a TAS is.

	If you want to start TASing, you'll want to download this .wch file and open it with RAM watch in your emulator. This ~~allows~~ you to see a bunch of important values like velocity and position, which will be used a lot while TASing~~. [http://www.mediafire.com/?z86e48e798bwhj8 Click here] to download~~. <br/>		If you want to start TASing, you'll want to download this [http://www.mediafire.com/?z86e48e798bwhj8 .wch file] and open it with RAM watch in your emulator. This will allow you to see a bunch of important values like velocity and position, which will be used a lot while TASing. <br/>

	Also check out the [[TAS_Guide\|TAS guide]] and the YI page on [http://tasvideos.org/GameResources/SNES/YoshisIsland.html ~~TASvideos~~.~~org]~~ ! <br/>		Also check out the [[TAS_Guide\|TAS guide]] and the YI page on [http://tasvideos.org/GameResources/SNES/YoshisIsland.html TASVideos] for more info. specific to Yoshi! <br/>

	'''For the sake of clarity:'''		'''For the sake of clarity:'''

Brooklyn9d5: /* Introduction */

2020-07-23T02:50:03Z

Introduction

← Older revision		Revision as of 02:50, 23 July 2020
Line 6:		Line 6:
	If you want to start TASing, you'll want to download this .wch file and open it with RAM watch in your emulator. This allows you to see a bunch of important values like velocity and position, which will be used a lot while TASing. [http://www.mediafire.com/?z86e48e798bwhj8 Click here] to download. <br/>		If you want to start TASing, you'll want to download this .wch file and open it with RAM watch in your emulator. This allows you to see a bunch of important values like velocity and position, which will be used a lot while TASing. [http://www.mediafire.com/?z86e48e798bwhj8 Click here] to download. <br/>

	Also check out the [TAS_Guide\|TAS guide]] and the YI page on [http://tasvideos.org/GameResources/SNES/YoshisIsland.html TASvideos.org] ! <br/>		Also check out the [[TAS_Guide\|TAS guide]] and the YI page on [http://tasvideos.org/GameResources/SNES/YoshisIsland.html TASvideos.org] ! <br/>

	'''For the sake of clarity:'''		'''For the sake of clarity:'''

Brooklyn9d5: /* Introduction */

2020-07-23T02:49:54Z

Introduction

← Older revision		Revision as of 02:49, 23 July 2020
Line 6:		Line 6:
	If you want to start TASing, you'll want to download this .wch file and open it with RAM watch in your emulator. This allows you to see a bunch of important values like velocity and position, which will be used a lot while TASing. [http://www.mediafire.com/?z86e48e798bwhj8 Click here] to download. <br/>		If you want to start TASing, you'll want to download this .wch file and open it with RAM watch in your emulator. This allows you to see a bunch of important values like velocity and position, which will be used a lot while TASing. [http://www.mediafire.com/?z86e48e798bwhj8 Click here] to download. <br/>

	Also check out the ~~Yoshi's Island [~~[TAS_Guide\|TAS guide]]! <br/>		Also check out the [TAS_Guide\|TAS guide]] and the YI page on [http://tasvideos.org/GameResources/SNES/YoshisIsland.html TASvideos.org] ! <br/>

	'''For the sake of clarity:'''		'''For the sake of clarity:'''

Brooklyn9d5: /* Melon Bugs */

2018-10-21T23:07:32Z

Melon Bugs

← Older revision		Revision as of 23:07, 21 October 2018
Line 260:		Line 260:

	Tapping < for 1 frame when trying to push a Melon Bug to the left will instantly set your velocity to -576.		Tapping < for 1 frame when trying to push a Melon Bug to the left will instantly set your velocity to -576.



	==Terrain==		==Terrain==

Brooklyn9d5: /* Giant Egg Aiming */

2018-10-21T23:07:24Z

Giant Egg Aiming

← Older revision		Revision as of 23:07, 21 October 2018
Line 251:		Line 251:
	TO-DO		TO-DO

	===~~Giant~~ Egg Aiming===		===Big Egg Aiming===
	TO-DO		TO-DO