How to Fish Speedrun Records — 1.0.11+, No Gambling & Crab%

Current How to Fish speedrun records

v1.0.11+ Solo · Snapshot from September 29, 2026 at 05:16 UTC. These are accepted community leaderboard results; later runs can change the standings.

What is the Crab% speedrun?

Crab% is the short community category built around the opening Spider Crab route. Its current rules end when the runner kills the crab, sells the shell and picks up the keys. The September 29, 2026 v1.0.11+ Solo snapshot shows 0:55.550 by Flyinbryon in first place.

Keep Crab% separate from a full Any% run: it is an opening-category objective, not a claim that the campaign can be completed within the Crab% time. Confirm the live category rules and timing endpoints before recording because the board is new and can still change quickly.

Any%, No Dynamite, 100% and Crab% are different runs

Select the category before planning the route. A fast finish is not automatically valid for every board, and a video labeled “world record” is incomplete unless it identifies the category, version and player count.

Current No Gambling record and rules

No Gambling is now a formal community category on Speedrun.com. Its published rule is narrow: any use of the roulette table invalidates the run. The September 29, 2026 v1.0.11+ Solo snapshot lists 15:59.933 by balllight in first place. The run was played on 2026-09-07 and accepted on 2026-09-08 at 20:06 UTC.

Use that exact v1.0.11+ Solo filter when comparing the result; another version or a Duo run belongs to a different board. A submission needs its own category, version and player-count label before its time is comparable.

Does Friendly Fire off protect a speedrunner from TNT?

No. Patch 1.0.11 makes your own explosives lethal even when Friendly Fire is disabled. The No Dynamite rules prohibit using dynamite to damage fish or bosses but still allow it in water to get fish. Any runner using TNT must clear the blast area before detonation. A player reported dying to large TNT clusters during a Bean attempt; Friendly Fire off does not prevent that self-damage.

Speedrun.com also exposes Solo, Duo, Trio, Quad and larger player-count filters. Multiplayer boards require their own evidence and should not be compared directly with Solo. Read the selected board’s live rules before recording.

Why the three speedrun version groups must stay separate

1.1.0 is a new release, not a newly verified category here. This September 29 API check retains the board’s actual v1.0.11+ Solo filters. The leading Any% run was played September 26 and accepted September 27, before The Islet Update. Do not label that time a 1.1.0-only record or assume the new bow is permitted under every existing rule set.

Speedrun.com now exposes v1.0.4, v1.0.5-v1.0.10 and v1.0.11+. The official 1.0.5 patch fixed travel to islands before they were unlocked, while 1.0.11 added hold-to-attack and changed self-explosive damage. The community board consequently keeps routes from these builds in separate variables.

A faster time on an older build is not proof that the v1.0.11+ record is wrong. Always write the full label—for example, “v1.0.11+ Solo Any%”—instead of collapsing all boards into one How to Fish world record.

Rules, video evidence and input overlay

The leaderboard posted an August 28 rule change requiring an input overlay for top-three Any% runs. That notice is historical community moderation guidance, not an in-game setting or a fresh confirmation of every current rule. A runner aiming for the top of Any% should confirm the rule again before starting a serious recording.

1. Open the exact leaderboard filter. Choose category, version and player count before reading the times.
2. Read the live rules. Do not rely on an older video description when the board has posted a newer rule.
3. Prepare continuous video. Keep the game, timer and any required input display readable from start to finish.
4. For co-op, capture every required point of view. The player-count variable includes evidence requirements for multiplayer runs.
5. Keep the submitted version exact. Record the visible build before using a route that depends on patch behavior.

Build a first current-patch route

A first route should remove indecision before it tries to copy every advanced movement trick. Use the campaign order, boss triggers and one-hour planner to create a repeatable baseline, then compare splits against your own previous run.

1. Match the accepted category and version to your actual run. Confirm moderator rules before submitting on 1.1.0; the checked v1.0.11+ Solo board is not a separately verified Islet category. Do not copy a v1.0.4 or v1.0.5-v1.0.10 route without checking which steps changed.
2. Write the five-island objective chain. Record the quest item, boss trigger and required hand-in for each stage.
3. Pre-plan purchases. Avoid opening shops without a specific weapon, lure, Radar or engine target.
4. Practice transitions separately. Time the boat departure, island landing and quest hand-in rather than only the boss fight.
5. Save a clean split sheet. Keep one line for each major hand-in and the final completion trigger.
6. Add risk only after consistency. A route that resets repeatedly is not automatically faster than a stable current-patch path.

Bean achievement vs competitive speedrunning

The Bean achievement planner answers “Can I finish within one hour?” It includes broad target splits and a forgiving achievement route. This page answers a different set of questions: which leaderboard applies, what the current verified reference is, why patch versions are split and what evidence the board expects.

Use Bean as the first milestone if a 15–25 minute route is not yet realistic. Completing the game under one hour can establish route memory without claiming a leaderboard record or satisfying a category’s submission rules.

How this page handles changing records

Each category name in the table opens its v1.0.11+ Solo board, and each time opens the individual accepted run. The September 29 refresh changed Any% to 9:54.867 by spenceuh; the other four checked categories retained their previous leading results. The snapshot time is a source check, not the date on which every run was played.

Exact record times are always paired with a check date. The page will not silently treat an old first-place time as permanent, and it will not merge pending or unverified runs into the verified table. The live Speedrun.com board remains the deciding source for placement.

• Quote category, version and player count with every time.
• Include the September 29, 2026 05:16 UTC snapshot time when comparing these results.
• Keep official patch facts separate from community leaderboard decisions.
• Recheck the live rule notice before recording a top-three attempt.