Crash to menu when accessing colonist inventory

[jakeramsay007]

Is there an existing issue for this?

• I have searched the existing issues.

Are you using the latest MineColonies Version?

• I am running the latest beta/release version of MineColonies for my Minecraft version.
  I am also running the latest versions of other mods that are part of my problem.

Did you check on the Wiki? or ask on Discord?

• I checked the MineColonies Wiki and made sure my issue is not covered there. Or I was sent from discord to open an issue here.

What were you playing at the time? Were you able to reproduce it in both settings?

• Single Player
• Multi Player

Minecraft Version

1.21

MineColonies Version

minecolonies-1.1.847-1.21.1-snapshot

Structurize Version

structurize-1.0.758-1.21.1-snapshot

Related Mods and their Versions

1. Forge Version: 21.1.95
2. BlockUI Version: blockui-1.0.192-1.21.1-snapshot
3. Domum Ornamentum Version: domum_ornamentum-1.0.204-1.21.1-snapshot
4. Latest AllTheMods10 modpack

Current Behavior

When my wife opens the inventory of one of my colonists, every couple of colonists the game crashes to the menu with the attached error.

When she rejoins the colonist that previously crashed the game back to the menu then works, but another will cause the same crash.

Expected Behavior

Not crashing the game when she opens the inventory of one of my colonists

Reproduction Steps

Presumably, it happens when someone other than the colony owner accesses a colonist's inventory, but other than that I'm unsure how to reproduce the issue.

Logs

https://gist.github.com/jakeramsay007/37cf7a5d6ad7c44d2b6a942cef4256df

Anything else?

No response

Footer

---

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.

[someaddons]

could you go into the configs/connectivity.json file and turn on debugMessagePrint(or similar entry) to true, then reproduce the issue and upload that latest.log it produces?