MineColonies

MineColonies

57M Downloads

Request system doesnt check if hut is built or has a worker assigned before sending a request to it

Bashkaaaa opened this issue ยท 0 comments

commented

Prerequisites

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

Context

Expected behavior

Request system checking if the hut is capable of fulfilling the request before sending it there

Actual behavior

If you have a hut placed, but not completely built yet, or have an unoccupied hut and a request is generated for a resource/ service hut can provide (e.g. stripped logs from a forester, or a default recipe/taught recipe for crafters), the request can be assigned to such hut. This request can not be fulfilled by that hut and player has to fulfill it manually, because even if we cancel it, it keeps popping up and getting assigned to the same hut (maybe based on distance?).

Steps to reproduce the issue

  1. Place a forester hut, build it and a assign a worker at certain distance from a builder (not sure if this is based on distance, if there is another factor deciding where the rests get assigned, please change the details here)
  2. Place another forester hut, but don't start the construction, this time much closer to the builder
  3. Start another building project involving stripped logs and observ that the request will be "stuck". It will be addressed to a forester, but marked as to be resolved by a player, while there is a second forester hut fully operational, which could fulfill this request.

Logs

N/A

Notes

  • We don't use the latest alpha, only the latest beta, because the modpack is being updated once a week when the new beta comes out

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.