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

QuickCraft implementation #1002

Closed
4 tasks done
mdenials opened this issue Jun 1, 2024 · 3 comments
Closed
4 tasks done

QuickCraft implementation #1002

mdenials opened this issue Jun 1, 2024 · 3 comments
Labels
status:stale status:unconfirmed New issue. Needs triage. type:enhancement New feature or request

Comments

@mdenials
Copy link
Contributor

mdenials commented Jun 1, 2024

Pre-suggestion checklist

  • I have searched existing issues and didn't find any previous issues with the same suggestion.
  • This is only one suggestion. I understand that GitHub issues don't work well with lists.
  • This feature doesn't already exist in the latest version of Wurst. I've made sure my installation is up to date.
  • I have looked at the code and am reasonably confident that this suggestion is possible to implement.

What type of improvement are you suggesting?

Adding a new hack.

What type of player would find this improvement useful?

Builders, Miners, Other (please explain in description)

Description

Adding feature which automatically moves the created item to the inventory

@mdenials mdenials added status:unconfirmed New issue. Needs triage. type:enhancement New feature or request labels Jun 1, 2024
@mdenials
Copy link
Contributor Author

mdenials commented Jun 1, 2024

AutoCraftHack.txt

@mdenials
Copy link
Contributor Author

mdenials commented Jun 2, 2024

@Alexander01998, and a feature that speeds up the mass crafting of items

Copy link

github-actions bot commented Aug 2, 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 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:stale status:unconfirmed New issue. Needs triage. type:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants