Welcome to Elderfield Fishing Tutorial: Rod, Bait & Minigame

The current material points to the Lakefront as the starting place for fishing. It also points to Fisherman Herb as the early interaction that introduces the rod and bait. Because these details come from third-party pages and a Demo gameplay recording, confirm the location and dialogue in your 1.0.0 save before treating them as a fixed route.

Bring the rod into your active equipment before testing a spot. If the game offers a Use or equipment action, use it to inspect the loaded bait rather than assuming the last bait you carried is already attached. That check is useful even when no fishing prompt appears, because it separates an equipment problem from a location or tutorial problem.

1. 1

   Reach a fishing water spot

   Start with the Lakefront route shown in the collected material. Stop and verify the 1.0.0 map or tutorial if the spot is not available in your save.

2. 2

   Speak with the early fishing NPC

   The draft sources point to Herb as the first fishing contact. Check for the rod or bait handoff and do not assume a Demo dialogue is unchanged.

3. 3

   Equip the fishing rod

   Put the rod in the active equipment slot, then inspect it if the game exposes a bait or Use action.

4. 4

   Load bait for the spot

   Use the bait shown for the current location in the verified UI. A mismatched bait is the first candidate explanation when the spot does not respond.

5. 5

   Wait for the bite

   Cast or interact with the spot, then wait for the bite state. The sources describe the minigame as beginning only after a fish bites.

6. 6

   Work the progress area

   The candidate walkthrough describes repeated input while the arrow is over the blue bar until progress fills. Confirm the exact control and success message in 1.0.0.

The collected fishing material describes a bite stage followed by a blue progress area. Treat that sequence as a candidate interaction model, not a confirmed control scheme. The visible prompt in your save decides whether the current action is cast, wait, reel, or another input.

Watch for a clear state change before holding or repeating a button. If the game shows no bite, return to the rod, bait, and spot checks instead of assuming the minigame has started. If a bite is visible but progress does not move, record the prompt and the target area as separate observations.

This check isolates the first missing response. A failed cast does not prove that the bait is wrong, and a failed progress input does not prove that the spot is locked. Keep both possibilities marked To be confirmed until the current UI makes the cause clear.

Use one water spot at a time when comparing the collected material with a current save. The source set groups fishing by location and bait, but it does not establish a universal list of spot conditions. A controlled comparison is safer than changing several conditions together.

Before moving, write down the spot name or map context, the rod state, the bait name, and the exact prompt. Then repeat the smallest available interaction and record whether the response reaches the bite stage. This creates a useful note even when the result is negative.

Do not turn a successful catch into an unverified fish table. The collected pages differ in coverage, and the gameplay recording is a Demo session. Keep fish identity, size, season, time, weather, and reward details out of the confirmed answer until each field is visible in a current source.

A useful fishing note starts before the interaction. Record the platform, visible build or release context, water spot, rod name, bait name, and the exact wording of the prompt. These details make it possible to tell a changed control from a changed progression requirement.

Capture the result after each stage rather than only the final catch. The important boundaries are equipment ready, bait accepted, bite shown, minigame active, progress changed, and result displayed. If one stage is missing, leave the missing condition open instead of supplying it from a neighboring guide.

When the current evidence is complete, update the fishing evidence record before expanding the page with fish tables or rewards. Until then, this tutorial gives a cautious action order and a debugging checklist. It remains a draft because the 1.0.0 route and controls are not independently confirmed.

First check the rod, then the bait, then the spot. If the rod is equipped but no bite state appears, verify that the bait is actually loaded and that the location accepts it; only after those checks should you treat the tutorial trigger or the spot unlock as the problem. Record the stage that stopped.

If the bite appears but the progress does not move, check the control prompt and watch for the blue target area before changing location. The collected video shows a minigame response, but it does not establish the current 1.0.0 input or timing window. Keep the control To be confirmed.

This page is intentionally short while the current build is unverified. The remaining checks are the tutorial trigger, Herb and Lakefront access, rod and bait controls, the exact bite minigame, and the conditions for later spots and fish. Each item needs current evidence.

Once those checks are available, update the Evidence Pack first, then replace the draft wording with the confirmed route. Until then, use the action sequence as a checklist for what to observe in-game, not as a promise about every save or platform. Keep unresolved controls marked To be confirmed.