|
|
| Line 1: |
Line 1: |
| − | == Summary ==
| |
| − |
| |
| | This page explains glitches that has to do with ancilla. | | This page explains glitches that has to do with ancilla. |
| | | | |
| − | For now, go to [[Spooky Action at a Distance]] for the also-ancilla-related glitch that was found in 2018. This page is a summary of the glitches found mid 2019. | + | For now, go to for the also-ancilla-related glitch that was found in 2018. This page is a summary of the glitches found mid 2019. |
| | | | |
| | In this game, we use the word ''ancilla'' (plural: ''ancillae'') for objects that Link produces/uses. Some examples are Boomerang, Bombs, Somaria block/spark, Sword spark, and Boots dust. | | In this game, we use the word ''ancilla'' (plural: ''ancillae'') for objects that Link produces/uses. Some examples are Boomerang, Bombs, Somaria block/spark, Sword spark, and Boots dust. |
| | | | |
| | Enemies, Heart drops, etc... on the other hand, are sprites. | | Enemies, Heart drops, etc... on the other hand, are sprites. |
| | + | |
| | + | == Types == |
| | + | Ancillae are a broad category, so this page only covers the broad overview. |
| | + | |
| | + | Specific types of ancilla-related glitches: |
| | + | * [[Spooky Action at a Distance]] |
| | + | * [[Ancilla Overload]] |
| | + | * [[Ancilla Misslotting]] |
| | | | |
| | == History == | | == History == |
| Line 46: |
Line 52: |
| | | | |
| | In addition to checking for available Slots for ancillae, there is another routine the Search Index is involved in, and it has to do with Wall Arrows. If the player tries to create more than 3 wall arrows on-screen, the Search Index will be set to <code>04</code>, and the index will decrement as the game looks for Wall Arrows to replace with the new Wall Arrow. | | In addition to checking for available Slots for ancillae, there is another routine the Search Index is involved in, and it has to do with Wall Arrows. If the player tries to create more than 3 wall arrows on-screen, the Search Index will be set to <code>04</code>, and the index will decrement as the game looks for Wall Arrows to replace with the new Wall Arrow. |
| − |
| |
| − | == Ancilla overload ==
| |
| − | Ancilla Overload is a glitch where the Front Slots are filled such that new ancillae won't be able to load in. This is considered a Minor Glitch. Generally this is going to be executed in one of two ways:
| |
| − | # Fill Slots 0-4 with non-particle ancillae. When you try to load a new ancilla in this case, the Search Index will fail to find a particle ancillae to replace and the ancilla will not load in.
| |
| − | # Fill Slots 0-4 with a mix of particle and non-particle ancillae, but make sure the Search Index is set to a value where its search will miss the particle ancillae. This will also prevent new ancillae from loading in.
| |
| − | ## Generally this manipulation of the Search Index is going to be taking advantage of our knowledge of the two routines it's involved in (read the Search Index section of this page for info).
| |
| − |
| |
| − | === Heart Despawn Glitch ===
| |
| − |
| |
| − | A method to despawn heart containers, making our Low% runs lower.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Heart Despawn Glitch
| |
| − | | file= File:Low_hpskip_armos.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | This works by filling up ancillae slots in clever ways that only despawn the heart container, but not the pendant/crystal that follows (else you would softlock on most bosses where doors are closed and menus not possible).
| |
| − |
| |
| − | Pastebins: https://pastebin.com/aNApJZLz https://pastebin.com/BeBFwZX6
| |
| − |
| |
| − | === Splash Deletion ===
| |
| − |
| |
| − | Ancilla Overload allows for one method of performing the [[Fake Flippers]] glitch. The splash that happens when Link jumps into deep water is an ancilla (ID: $15), and the check for Flippers occurs as part of the splash ancilla's routine. This means if there's no splash, there's no Flippers check, and Link will be able to swim. And of course we can make this happen with ancilla overload. See the [[Fake Flippers]] page for more info and setups.
| |
| − |
| |
| − | == Misslotting ==
| |
| − |
| |
| − | === Explanation ===
| |
| − |
| |
| − | The game was coded to have certain items in certain slots. Bombs for example, need to be in slot 0 or slot 1. Most other items from Link's inventory were only coded to be in slot 0, 1, 2, 3 or 4 (which we'll call the Front Slots). The Back Slots (slots 5-9) are typically reserved for less "significant" ancillae, such as the sparkle effects that appear while Link is holding a sword charge. However, there are ways to force an item that would normally spawn in a Front Slot into a Back Slot. Since this was unintended from developers (and it doesn't really happen in normal gameplay), unintended things happen.
| |
| − |
| |
| − | We call the concept of putting an item into a slot it was not coded to be in ''mis-slotting'' (or ''misslotting'').
| |
| − |
| |
| − | Broadly, the way this works is to do the following:
| |
| − | * Set the search index to a value at least one digit above the value of the Slot you want to Misslot to (ex. if you want to Misslot an ancilla in Slot 9, you want the search index above <code>09</code>)
| |
| − | * Occupy slots 0-4.
| |
| − | * Occupy the slot you want to misslot to with a Particle ancillae. Commonly, this will be slot 9.
| |
| − | * Load the ancilla you wish to misslot. When you do this, the game will see slots 0-4 occupied. It will then reference the search index to look for an available slot to spawn the object in. It will see a replaceable ancilla in slot 9 and will load the object there, giving a successful misslot.
| |
| − |
| |
| − | === Manipulating the Search Index to High Values ===
| |
| − |
| |
| − | If you read the section on the Search Index, you probably noticed that neither of the two intended routines it's used in lend themselves to setting the Search Index high. This is important because when we fill the Front Slots and use the ancilla we want to Misslot, we want the game's secondary search routine to be looking through the Back Slots. So how do we set it to a high value? By far the most common way is to use a Slot 2 Lamp.
| |
| − |
| |
| − | The Lamp sets values to an array at <code>$03C5</code>, but for some reason, this array only has two positions: one for Slot 3 Lamp and one for Slot 4 Lamp. If you go one under this with a Lamp in Slot 2, the Lamp starts setting values to <code>$03C4</code> -- and that's the Search Index! Since the Lamp's quota is 3 (the game allows 3 Lamp flames on-screen at the same time), you can quickly use the Lamp 3 times, and you'll put a Lamp flame in Slot 2. This will put a specific value into <code>$03C4</code> depending on which direction Link is facing when the Slot 2 Lamp happens:
| |
| − | * If you Lamp facing North, the Search Index will be <code>0D</code> (or 13 in decimal)
| |
| − | * If you Lamp facing West, the Search Index will be <code>10</code> (or 16 in decimal)
| |
| − | * If you Lamp facing South, the Search Index will be <code>0A</code> (or 10 in decimal)
| |
| − | * If you Lamp facing East, the Search Index will be <code>07</code>
| |
| − |
| |
| − | East facing Slot 2 Lamps aren't normally used since <code>07</code> isn't a high enough value for most of the useful Misslotting in Speedruns. We typically want to Misslot ancilla into Slots 8 or 9, so we can just use one of the other three options to accomplish this.
| |
| − |
| |
| − | === Effects ===
| |
| − |
| |
| − | The consequences of Misslotting are generally going to be the result of the arrays that Front Slot Ancillae use as part of their routines not having enough elements for Back Slot Ancillae. This means that when Front Slot Ancillae are loaded into the Back Slot, the memory addresses they modify as part of their routine behavior will be the 'wrong' addresses.
| |
| − |
| |
| − | For example: memory address <code>$0394,X</code> (X being the Slot of a Somaria Block) is a variable that figures into the routine of placing Somaria Blocks. When Link places one, the value at this address jumps to <code>0B</code> before decrementing down to <code>00</code>. So when you go to place a Somaria Block with no other ancillae on-screen, it will load in Slot 4 by default. The game will add 4 to our base address to get <code>$0398</code> and modify the values there.
| |
| − |
| |
| − | Meanwhile, the Hookshot uses memory address <code>$039D</code> to determine which Slot's duration counter to use while the Hookshot is pulling Link. When Link uses the Hookshot, it will extend and a counter at the Hookshot's Slot will increment every frame until it latches onto something. The game then puts what Slot the Hookshot is in at <code>$039D</code> and the pull starts. The game will now decrement that same counter it was using before as Link is pulled to whatever object he's Hookshotted, and the game knows to use this specific counter because of the value stored at <code>$039D</code>.
| |
| − |
| |
| − | But what if we place a Somaria Block in Slot 9? Well now when the game adds <code>09</code> to <code>$0394</code>, we get <code>$039D</code>. Well that's the same address the Hookshot is using to see what values should determine how long to pull Link for! This is the basis for how [[Hookpush]] works, but all Misslot effects are the result of this kind of behavior.
| |
| − |
| |
| − | There's a tutorial on how misslotting works here: https://milde.no/public/alttp/misslots/.
| |
| − |
| |
| − | See [[Consistent setups for misslotting to slot 9]].
| |
| − |
| |
| − | ==== Weirdshot ====
| |
| − | {{Main|Weirdshot}}
| |
| − | ''Weirdshot'' (sometimes called Hookclip) is the name of a [http://zelda.speedruns.com/mm/tech/weirdshot similar glitch] in Ocarina of Time speedruns, copied over to ALttP.
| |
| − |
| |
| − | The hookshot can pass through one-tile blocks.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Weirdshot
| |
| − | | file= File:Gthookclip.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | What happens is that the hookshot object is traveling in EG for 3 out of 4 frames. There is another variant of this where the hookshot is ''only'' traveling in EG. If you hit something in the other layer, it will drag Link to it and also change Link's layer.
| |
| − |
| |
| − | Preliminary technical explanation can be found here https://pastebin.com/ua73VDi1, but it's not complete.
| |
| − |
| |
| − | ==== Hookpush (Somaria misslot) ====
| |
| − | {{Main|Hookpush}}
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Hookpush
| |
| − | | file= File:Wonkaspike.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | The reason this works is very technical, but basically, the "hookshot dragging Link to an object" code is glitched out and Link is dragged for a longer duration and often a different direction. This code does not check any collision at all, so Link can clip through walls. You can also use this to get Link into EG.
| |
| − |
| |
| − | We can completely control the direction, the duration, and whether or not Link should be put into a different layer, by changing the setups.
| |
| − |
| |
| − | Tutorial on how to do this consistently: https://milde.no/public/alttp/misslots/
| |
| − |
| |
| − | Pastebin: https://pastebin.com/KsRGZNKu.
| |
| − |
| |
| − | ==== Hookpush (Hook misslot) ====
| |
| − |
| |
| − | Same application as above, but done by misslotting hookshots instead.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Hookpush
| |
| − | | file= File:Hookpush hookmisslot.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | Technical explanation: https://pastebin.com/Z1FanJwK
| |
| − |
| |
| − | ==== Overworld Conveyor ====
| |
| − |
| |
| − | By transitioning right after dropping either a Bomb or Somaria (misslotted in slot 9) from taking damage, you can get the conveyor effect while in the overworld. You can get this effect either upwards or downwards depending on the setup.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Overworld conveyor effect
| |
| − | | file= File:OwConveyorEffect.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | When this effect is active, you can nudge against any slope and automatically clip from one side of the overworld map to the other, without anything colliding with Link. You can even use your sword and some items while in this ''noclip mode'', while other actions like dashing or moving will let Link collide with things again.
| |
| − |
| |
| − | Another application of this is transitioning into an underworld entrance. This gives the same effect as mirroring while on a conveyor belt, except the setup is outside the entrance and can easily be done for all entrances now.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = OW Conveyor into UW OoB clips & EG
| |
| − | | file= File:ConveyorOobFromOw.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | Note that Somaria is not needed for this, it could be done with holding a bomb instead.
| |
| − |
| |
| − | ==== Fanfare Skip ====
| |
| − | {{Main|Fanfare Skip}}
| |
| − |
| |
| − | Fanfare Skip is a glitch that can be done while collecting Pendants that will skip most of the cutscene that typically follows grabbing them. For it to work, the following conditions must be met:
| |
| − |
| |
| − | * The pendant is collected with ancilla slots 0-4 filled.
| |
| − | * A somaria block is misslotted 8 slots higher than the slot the pendant is in. Typically this is done by ensuring the pendant spawns in slot 1 (it will normally try to spawn in slot 3), and then misslotting a somaria block to slot 9.
| |
| − |
| |
| − | For more info and specific setups, see the main page: [[Fanfare Skip]]
| |
| − |
| |
| − | ==== Murderbomb ====
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Murderbomb
| |
| − | | file= File:Murderbomb.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | By putting a bomb into slot 9, we can reset the ''explosion duration'' timer indefinitely by simply using a hookshot or producing sword beams.
| |
| − |
| |
| − | ==== Overworld Ancilla Persistence Through Transitions ====
| |
| − |
| |
| − | By misslotting a bomb (or anything else), it will still be active after Link transitions.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Example of Spooky Bomb
| |
| − | | file= File:SpookyBomb.mp4
| |
| − | | width = 340
| |
| − | | description = A silly application of this, but it's the only known one that does anything "useful".
| |
| − | }}
| |
| − |
| |
| − | === Arbitrary misslotting ===
| |
| − | Misslotting an ancilla into a slot that doesn't even exist (slot 10+). Basically, you end up writing values to arbitrary memory at will.
| |
| − |
| |
| − | This is the really broken stuff.
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Arbitrary Code Execution
| |
| − | | file= File:Ace.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | {{VideoBox
| |
| − | | title = Crystals out of nowhere
| |
| − | | file= File:Freecrystals.mp4
| |
| − | | width = 340
| |
| − | }}
| |
| − |
| |
| − | Some technical information here: https://pastebin.com/NnRnX4X5
| |
| − |
| |
| − | == Categorization of ancilla related glitches ==
| |
| − |
| |
| − | * Uninitialized altitude
| |
| − | ** Spooky Action Glitch
| |
| − | * Overloading slots
| |
| − | ** Despawn
| |
| − | *** Splashless fake flippers
| |
| − | *** Heart Delete
| |
| − | ** Misslotted Ancilla
| |
| − | *** Slot 5-9 misslot
| |
| − | *** Weirdshot
| |
| − | **** Weirdshot (Alternating Layer)
| |
| − | **** Weirdshot (Opposite Layer)
| |
| − | *** Hookpush
| |
| − | *** Murder Bomb
| |
| − | *** OW Conveyor
| |
| − | ** Slot 10+ misslot
| |
| − | *** ACE
| |
| − | *** etc. Anything can be done in theory.
| |
| − |
| |
| − | Some glitches in different "categories" use similar methods for its exploit.
| |
For now, go to for the also-ancilla-related glitch that was found in 2018. This page is a summary of the glitches found mid 2019.
Enemies, Heart drops, etc... on the other hand, are sprites.
Yuzuhara found that using items in certain combinations created weird effects, like getting two somaria blocks/bombs, having bombs explode indefinitely etc. He did not understand how it worked, and it was mostly not known about in the Discord at the time, but he posted everything on his twitter account here
Someone mentioned it on Discord after 4-5 months had passed, and the videos were linked into Discord. We started looking more in depth on what was happening, and this investigation produced a few new glitches. All of them having something to do with Ancillae.
An ancilla is "A self-acting entity whose routines and existence are established and controlled from the 10 item array at $0C4A." Broadly speaking, these are going to be objects that are spawned by Link's items. Bombs, arrows, the boomerang, fire and ice rod shots, the dust Link kicks up while dashing, etc. -- These are all ancillae.
There are 10 positions in the game's memory for ancillae, and we call these Slots. For practical reasons, we name/number them Slots 0-9.
Ancillae won't just choose whichever open slots to occupy. They can be broadly classified into Front Slot Ancillae (these occupy the first 5 slots: Slots 0-4) and Back Slot Ancillae (these occupy the final 5 slots: Slots 5-9). Front Slot Ancillae are generally significant objects in gameplay. Ancillae that load here will be things like Bombs, Arrows, Somaria Blocks, Sword Beams, Dash Dust, etc. Back Slot Ancillae are less significant to gameplay, often being objects that just add a bit of visual flare. Back Slot Ancillae include things like the sparkles that appear on Link's sword when he's charging a spin attack or the sparkles that appear on a shot from the Ice Rod.
Arrows that are stuck in a wall, the sparkles that appear with an Ice Rod shot, and the sparkles that appear with a Silver Arrow, the Red Boomerang, or when Link is charging his sword are all what we call Particle Ancillae. A key attribute of Particles that differentiates them from other ancillae is that they can be replaced. This is an important factor in ancillae glitches, as we'll see below.
In addition to checking for available Slots for ancillae, there is another routine the Search Index is involved in, and it has to do with Wall Arrows. If the player tries to create more than 3 wall arrows on-screen, the Search Index will be set to 04, and the index will decrement as the game looks for Wall Arrows to replace with the new Wall Arrow.
