Prerequisites

• I am running the latest alpha version of MineColonies and Structurize for my Minecraft version.
• I checked the MineColonies/Structurize wiki and made sure my issue is not covered there.
• I made sure that this issue is not a duplicate of any existing issue.

Context

• Minecraft Version: 1.16.4
• MineColonies Version: 0.13.525
• Structurize Version: 0.13.105
• Related Mods and their Versions: Valhelsia 3 Modpack, latest version: 3.1.0

Expected behavior

Our server updated to the latest valhelsia 3 modpack, which uses 0.13.525 minecolonies. We expected that our colonies would carry over relatively uninterrupted.

Actual behavior

We updated the server. The colonies apparently still exist (the folders are still in the world folder) but they are not present in game. Listing all colonies in game shows that no colonies exist. However, the town halls say that no colony can be founded in the original spots, because it is too close to a colony (labeled as the original colonies). So the colonies both still exist somewhere, but also don't exist according to the commands. We cannot delete the old colonies.

Steps to reproduce the issue

1. Create colonies in Valhelsia 3 pre7-3.1.0. Obtain colonists and at least one building outside the townhall.
2. Update from pre7-3.1.0 to the latest Valhelsia version, 3.1.0 (released yesterday).
3. Check to see whether the colony still exists. Buildings say "This block is missing its respective building, try restarting or loading a backup" twice when you click on their core block. The town hall will say "Colony with ID 1 is nearby. You do not currently own a colony. There is an existing colony too close."

Logs

• latest.log: https://gist.github.com/Shanman150/ff45c8ad79cb1032ac01439c5b8895a6
• crashlog: No crash.

Notes

Viewers

• Add a thumbs-up to the bug report if you are also affected. This helps the bug report become more visible to the team and doesn't clutter the comments.
• Add a comment if you have any insights or background information that isn't already part of the conversation.

Solved this myself, the naming conventions on the files seem to have changed or screwed up between versions. The .dat files were inside a folder called "colony1_ResourceKey[minecraft_dimension", and the .dat file was called "minecraft_overworld].dat". That seemed to be the source of the issue, as when we tried making a new colony, it created a .dat file called "colony1_minecraft:overworld.dat". Renaming our old files to this new format solved the issue.