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

Structurize Version

1.20.1-1.0.773

Related Mods and their Versions

1.20.47.0
structurize-1.20.1-1.0.773
domum_ornamentum-1.20.1-1.0.285
blockui-1.20.1-1.0.193.jar

Current Behavior

Expected Behavior

fix this bug ,the builder is inport

Reproduction Steps

1go builder station
2 build anything
3 atuo to Manual work
4ckick the assgin

Logs

https://api.mclo.gs/1/raw/q1b396C

Anything else?

nope just fix this bug :)

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.

Don't mark it as completed =)

I can confirm, I was testing this in latest 1.21.1 version (.1002) this morning. When you go to the task list, and click the "assign" button to manually assign a build, the button does nothing. Hiring the worker in the "build screen" to start the job manually worked, and automatic job pickup worked, but the "assign" button does nothing at all

yeah me 2 in build screen is ok

Taking a look at this now. Have reproduced. @Talyda or @mop2883 - do you happen to know if this is relatively new? (How recently do you recall this working as expected?)

Taking a look at this now. Have reproduced. @Talyda or @mop2883 - do you happen to know if this is relatively new? (How recently do you recall this working as expected?)

Yeah, sorry, I never use that button, so no idea =) Only used it to test for mop2883, cos they actually first reported it a few days ago, (maybe even a week ago?) and I didn't understand the problem at the time, yesterday I finally did, so tested =)

Ok, I can give a little more info as this is also happening to me. The builder doesn't detect builds in it's building radius on automatic, but does on manual, however it doesn't allow me to click the assign button that is shown in the image. The only way the builder will build a build is if you select a specific builder in the build/upgrade menu. I've had this issue since 1.1.994-1.21.1 until the latest build. Another thing I found (this could be connected) was that the farmer wouldn't assign themselves to empty fields. Another bit of context for me was that I was using the Minecolonies Official modpack when the issue popped up, and this wasn't an issue at the start.

I did test the automatic as well though, and they are working as expected with automatic assignment. Tried like 50 builds, all of them started with automatic assignment with no problem at all.

It was just the manual assign button is a problem.

Zaczumba, did you try the binary search?

I put in a pull request for a fix earlier in the day, so it should make it's way through the review process before too long!

Talyda, I did it but was a bit too extreme in turning off mods and turned off minecolonies, so since I got a new computer and the save is broken now, I started a new world and have not gotten this bug, the only thing I changed was add a few mods that shouldn't have changed anything, and gotten rid of Embeddium. I also checked and the logs from @mop2883 also has Embeddium. @mop2883, could you try turning it off (or replacing it with sodium if your computer can't handle without it) and see if it continues?

Would it be possible to also get a similar feedback in the game, instead of just in the latest.log?
That way it is easier to see for people that their builder could be too far away, and it is not just a button that does nothing (but printing a warning in the latest.log)

The assign button should probably override the distance check tbh, (as it should behave like manual assignment).

I of course chose the one example which should not matter in case of manual assignment

So to summarize: Remove distance check from enforcement of manual assignment, and move log message to in-game message? No problem. Tomorrow!