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

No Sweet Berries in AutoFarm #906

Open
NeGenaCidarmyan opened this issue Nov 25, 2023 · 6 comments
Open

No Sweet Berries in AutoFarm #906

NeGenaCidarmyan opened this issue Nov 25, 2023 · 6 comments
Labels
category:blocks status:never-stale Prevents stalebot from marking this item as stale. type:enhancement New feature or request

Comments

@NeGenaCidarmyan
Copy link

Why is there no sweet berries in the autofarm hack? He was in hack: #396

@v2i0
Copy link

v2i0 commented Nov 28, 2023

The pull request hasn't even been merged, that's why.

@Alexander01998
Copy link
Member

Hi @v2i0,

The reason that pull request wasn't merged is because it works by breaking the berry bush. This is not the correct way to farm sweet berries, as it destroys the plant in the process and means you have to wait for an entire new berry bush to grow.

Sweet berry support in AutoFarm would need to be implemented in a way that right-clicks on the berry bush instead.

@IUDevman
Copy link
Contributor

IUDevman commented Nov 30, 2023

Hi @v2i0,

The reason that pull request wasn't merged is because it works by breaking the berry bush. This is not the correct way to farm sweet berries, as it destroys the plant in the process and means you have to wait for an entire new berry bush to grow.

Sweet berry support in AutoFarm would need to be implemented in a way that right-clicks on the berry bush instead.

I've been working on my implementation for this feature. Code should be done, but testing is challenging. I hope to have a PR ready soon.

Copy link

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

  • They are duplicates of other issues
  • There is not enough demand
  • They are no longer relevant
  • There are not enough details

@Alexander01998
Copy link
Member

Still relevant.

Copy link

github-actions bot commented Apr 1, 2024

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

  • They are duplicates of other issues
  • There is not enough demand
  • They are no longer relevant
  • There are not enough details

@Alexander01998 Alexander01998 added status:never-stale Prevents stalebot from marking this item as stale. and removed status:stale labels Apr 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:blocks status:never-stale Prevents stalebot from marking this item as stale. type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants