Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Miner refuses to mine after encountering un-mineable block even after changing floor #7776

Open
2 of 3 tasks
RedlineTriad opened this issue Nov 16, 2021 · 3 comments
Open
2 of 3 tasks
Labels
Bug Gotta squash 'em all!

Comments

@RedlineTriad
Copy link

RedlineTriad commented Nov 16, 2021

Prerequisites

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

Context

  • Minecraft Version: 1.16.5
  • MineColonies Version: 1.0.87-ALPHA
  • Structurize Version: 0.13.252-ALPHA
  • Related Mods and their Versions: Valhelsia 3 modpack

Expected behavior

When a Miner encounters a block above the mining level of his pickaxe, he can be reassigned to a different mine level without obstructions.

Actual behavior

When a Miner is reassigned, he will still refuse to work, citing the un-mineable block that is on a different mine level.
Even if the Miner is fired and re-hired, he will only move a little bit before complaining about the same block again.
No order of changing level, hiring, and firing resulted in the Miner going to work on the new level.

image

Steps to reproduce the issue

  1. Build Mine.
  2. Hire Miner.
  3. Give Miner an iron pickaxe.
  4. Let Miner build vertical shaft.
  5. Add block above mining level of pickaxe such as obsidian to horizontal shaft.
  6. Assign Miner to mine on level with the obsidian
  7. Wait until Miner complains about obsidian.
  8. Assign Miner to work on a different level without obsidian.
  9. Observe Miner still refusing to work.

Logs

I don't have full logs because it was on a server, and I think this is probably just known un-implemented behavior anyways.
I can supply them by recreating them manually if needed.

Notes

I haven't tested this, but the pathological case for this bug would most likely be the end portal, as it is indestructible and because mining can't be canceled the Miner would be stuck forever and useless.
I assume implementing this would require the ability to cancel in-progress mining nodes.


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.
@RedlineTriad RedlineTriad added the Bug Gotta squash 'em all! label Nov 16, 2021
@Raycoms
Copy link
Contributor

Raycoms commented Nov 16, 2021

Little question, was the miner mining a horizontal shaft or vertical shaft when they got stuck?

@RedlineTriad
Copy link
Author

RedlineTriad commented Nov 16, 2021

Little question, was the miner mining a horizontal shaft or vertical shaft when they got stuck?

Horizontal, as not very clearly described in reproduction steps.

@RedlineTriad
Copy link
Author

But I think I also had a similar problem on the vertical shaft before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Gotta squash 'em all!
Projects
None yet
Development

No branches or pull requests

2 participants