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

Autoeat fails when using Autotool and excavator #316

Closed
tylerroost opened this issue Feb 16, 2021 · 6 comments
Closed

Autoeat fails when using Autotool and excavator #316

tylerroost opened this issue Feb 16, 2021 · 6 comments
Labels
category:items status:confirmed status:never-stale Prevents StaleBot from marking this item as stale. type:bug Something isn't working
Milestone

Comments

@tylerroost
Copy link

Other posts indicate that offhand eating may help this problem, but there has not been any explicit indication of this specific problem

Description

When using excavator and autotool in survival autoeat will trigger and force a back and forth switching between the suitable tool and the food, effectively diminishing the effect of the mining and causing food to not be eaten.

Steps To Reproduce

Please make a list of steps to reproduce the problem (ideally from a fresh Wurst installation):

  1. Enable excavator on a large enough area where you will get hungry while mining
  2. Enable autotool and autoeat with the appropriate tools and food in hotbar
  3. Let excavator run until food diminishes
@tylerroost tylerroost added the type:bug Something isn't working label Feb 16, 2021
@AndrewBruhMoment
Copy link

This could be fixed by putting a check in autotool to stop switching when autoeat is triggered or eating starts.

@Alexander01998
Copy link
Member

This could be fixed by putting a check in autotool to stop switching when autoeat is triggered or eating starts.

Not if Excavator is running at the same time, then it would try to mine with food...

This comment was marked as outdated.

@Alexander01998

This comment was marked as outdated.

This comment was marked as outdated.

This comment was marked as outdated.

@Alexander01998 Alexander01998 added status:never-stale Prevents StaleBot from marking this item as stale. and removed status:stale labels May 13, 2024
@Alexander01998 Alexander01998 added this to the v7.43 milestone May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:items status:confirmed status:never-stale Prevents StaleBot from marking this item as stale. type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants