For fields of mistria legendary fish, begin with the skill menu, Almanac, weather display, and any alert shown by the current game. Record what the save shows before choosing a water area or changing equipment. Build a personal catch route from successful observations instead of an old condition table.
Check the current menus first
Open the fishing skill menu and read the perks available on the save. Then inspect the Almanac and Museum views for the fish entries, silhouettes, or donation slots currently shown. These screens give you a starting record before a day is spent travelling between water areas.
Write down only visible information, such as the in-game date, season, weather label, perk text, alert text, and any fish silhouette. Keep the note beside the save name so records from different files do not become mixed. Recheck the same screens after an update because labels and behavior can change with a new build.
Read an alert before choosing a route
If the game presents a fishing alert, pause and copy its wording exactly into the catch note. Do not turn a silhouette into a water, time, rod, or bait instruction unless the game also displays that connection. Use the alert as the beginning of an observation rather than a complete route by itself.
Choose one accessible fishing area and make a short test there. Record the water type, time block, displayed weather, shadow sizes seen, equipment used, and whether a catch succeeded. Move to a second area only after the first test has a clear result, so several changed conditions do not blur together.
Change one condition at a time
A useful log keeps all but one condition stable. Try another water area while keeping the time and equipment the same, or change the time while returning to the same water. This makes a success easier to repeat and a failed attempt easier to interpret.
Avoid turning one empty fishing session into a permanent rule. Fish availability, ordinary random variation, player position, and the length of the test can all affect what appears. Repeat the same setup on another suitable day before removing it from the route.
Use a compact record for each attempt. Keep it short enough to compare at a glance. Record these fields:
- save name and in-game date;
- season and exact weather label shown by the game;
- alert or silhouette shown that morning;
- water area and approximate map position;
- time block, equipment, and shadow sizes tested;
- catch result and whether the Almanac or Museum changed.
Keep fish conditions separate
Do not copy a condition from one legendary fish into another row of the log. A weather label, water area, or shadow size that led to one catch is useful only for repeating that same observation. Start a fresh record when the Almanac, alert, or Museum points to a different fish.
Keep equipment experiments separate as well. If a catch fails, change either the rod, bait, location, or time in the next test, not all four together. A single controlled change produces a route you can explain and repeat later.
When a successful catch occurs, capture the full screen state immediately. Note the location, time, weather, equipment, and any alert before sleeping or changing areas. That successful row becomes the reference for the next attempt on the same save.
Check the Museum before selling
After catching an unfamiliar fish, open the Almanac and Museum interface before shipping or selling it. The live screens show whether the catch filled a record or donation slot on that save. Store the fish temporarily if you still need to decide between collection and cash goals.
Keep the first successful specimen until the collection check is complete. For later catches, use the current item information and your own goals to decide whether to donate, store, or sell. Avoid attaching a promised price, reward, or catch limit to the route unless the game displays it.
Turn the log into a repeatable route
Review the successful rows and look for the smallest shared set of visible conditions. Plan the next fishing day around those observations, then repeat the route without adding extra assumptions. If the result changes after an update, start a new dated row rather than rewriting the older observation.
The useful outcome is a short checklist tied to the current save: read menus, note the alert, test one area, change one condition, and check the Museum. That route answers the next action while keeping each observation tied to its date and save. It also leaves a clear record that another player can reproduce on the same version.