Forester doesn't do their job
Closed this issue ยท 2 comments
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.1006-snapshot
Structurize Version
1.20.1-1.0.780-snapshot
Related Mods and their Versions
No response
Current Behavior
Forester is constantly stuck at in a state of "START_WORKING", and just hangs around the forester hut block. Downgrading to .995 fixes the issue, so it suggests something between then and this version did something.
Expected Behavior
He's supposed to be cutting down trees and doing work.
Reproduction Steps
- Get a forester (Mine is level 3) and plant some trees around their hut block.
- Watch as they stare very very hard at their forester hut block. And then do nothing.
Logs
Anything else?
Like said above, downgrading to .995 fixes the issue for now.
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.
Can you confirm some saplings are turned on in that building tab? There was a recent change that made the lumberjack just wait for crafting requests if all saplings are turned off.
In attempting to reproduce this, I did note that lumberjacks loaded into a set sapling list idled. They went to work after I toggled a sapling in the list. After a server reset the same symptom presented itself. I will investigate further.
** Edit: I was unable to reproduce this at any point other than initially starting the updated version. Every subsequent test worked as expected. My suggestion for now would be to verify a non-zero sapling list and fire/re-hire the worker and see if they get back on the job...