Fishing ships stop working after depleting fish and do not automatically move to nearby fish

:play_button: GAME INFORMATION

:backhand_index_pointing_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME BUILD #: 185872
    GAME PLATFORM: Steam
    OPERATING SYSTEM: Windows11

:play_button: ISSUE EXPERIENCED

:backhand_index_pointing_down: DESCRIBE THE ISSUE IN DETAIL (below). LIMIT TO ONE BUG PER THREAD.

I always play single-player Skirmish against AI opponents.

Since September 23, 2026, I have experienced two issues with fishing ships.

  1. Fishing ships stop working

During the Dark Age and Feudal Age, fishing ships work normally. After depleting fish, they automatically move to other nearby fish.

However, after advancing to the Castle Age, fishing ships stop automatically moving to nearby fish after depleting their current fishing location.

  1. Fish remain visible after being depleted

Some fish remain visible on the map even though they appear to have already been depleted.

When I send a fishing ship toward these fish, they disappear as the ship approaches.

This makes fishing extremely difficult and time-consuming.

I have restarted the game and tested it in three separate Skirmish games, but the issues persist.

I have recorded two separate videos showing these problems.

:play_button: FREQUENCY OF ISSUE

:backhand_index_pointing_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • 100% of the time / matches I play (ALWAYS)

:play_button: REPRODUCTION STEPS

:backhand_index_pointing_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Start a single-player Skirmish game against AI.

  2. Build a dock and create fishing ships during the Dark Age.

  3. Continue fishing during the Feudal Age. Fishing ships still work normally.

  4. Advance to the Castle Age and continue fishing.

  5. Observe that fishing ships stop automatically moving to nearby fish after depleting their current fishing location.Observe that some depleted fish remain visible on the map but disappear when a fishing ship approaches them.

  6. Some depleted fish remain visible on the map but disappear when a fishing ship approaches them.

:play_button: EXPECTED RESULT

:backhand_index_pointing_down: What was SUPPOSED to happen if the bug you encountered were not present?

After depleting a fish location, fishing ships should automatically move to another nearby fish location and continue collecting food without requiring manual commands.

:play_button: IMAGE

:backhand_index_pointing_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.

Video 1: Depleted fish remain visible on the map and disappear when approached.

Video 2: Fishing ships stop working after depleting fish.

:play_button: GAME FILES (SAVE / RECORDING)

:backhand_index_pointing_down: Attach a SAVE GAME (.aoe2spgame) or GAME RECORDING (.aoe2record) of the match where you encountered the issue. Link it below if using an external file service.

Hi @yukihime9_8

Are you able to reproduce this issue when not using any mods in the game? I was not able to reproduce the fishing tiles being visible when they are depleted.

On the other hand, we are investigating the issue of the fishing ship going idle when there are fishing tiles available.

Hi, thank you for your reply.

I checked my installed mods and found that “Legacy ES Maps” was enabled.
I disabled “Legacy ES Maps” and tested the game again, but the same issues still occurred.

The issue where fishing ships become idle after depleting fish still occurs.

Regarding the issue where depleted fish remain visible on the map, I noticed that it becomes much more noticeable after reaching the Imperial Age.
By the later part of the game, this visual issue occurred 100% of the time.

The fish still appeared to be swimming on the map, but when I sent a fishing ship toward them, they disappeared because they had already been depleted.

So the issue still occurs even with “Legacy ES Maps” disabled.

Thank you for investigating this.