MineColonies

MineColonies

65M Downloads

Builder stuck permenantly in INIT job state

doggosuki opened this issue · 1 comments

commented

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.20

MineColonies Version

1.20.1-1.1.1065-snapshot

Structurize Version

1.20.1-1.0.784-snapshot

Related Mods and their Versions

blockui-1.20.1-1.0.194
domum_ornamentum-1.20.1-1.0.291-snapshot-universal.jar

Current Behavior

Image

My 3rd builder is stuck in the INIT job state permenantly. I have had them hired for the past several hours, and yet they have not exited the INIT job state and have never started working on any buildings, despite there being multiple queue'd up work orders (including new level 1 residences so it is not an issue of the builder's hut level). I've tried firing them and rehiring them which did nothing except get rid of their uniform, and I tried pausing then restarting them, but that just scheduled them for restart and never actually restarted them. I also tried reopening the game and it did not change anything. They still go to bed at bed time, eat when they are hungry, wander around in the IDLE citizen state and visit recreation sites.

Expected Behavior

The builder would exit the INIT state at some point and start to work on one of the pending build orders.

Reproduction Steps

I don't know how to reproduce it, sorry. All I remember that might be helpful is that I manually hired the bugged builder at some point, and before that they were working a different job. I tried looking through old logs to find info regarding this but was unable to find anything sadly.

Logs

https://gist.github.com/doggosuki/1d0da843ccf6bd5b229e3979707c6910

Anything else?

No response

Footer


Viewers

  • Add a 👍 reaction to the bug report if you are also affected. This helps the bug report become more visible without cluttering the comments.
  • ⚠️ Only add a comment if you have new insights or background information not already mentioned. Off-topic or "+1" comments will be deleted to keep the discussion focused.
commented

Nevermind, it isn't a bug - it was due to the pending builds being outside of the maximum range and I did not know about the 100 block automatic assignment range. Sorry for the confusion.