Make Dispenser/Dropper able to place blocks
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the Dispenser and Dropper mechanics and the sign-based IC handling described in the request. Read how these blocks currently place shulkerboxes and how piston movement affects their mechanism. Done means a dispenser or dropper can be toggled between block-placing and block-dropping modes without losing that behavior when moved by a piston.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
It isn't.
Describe the solution you'd like
I believe it could be awesome if Dispensers and Droppers were able to place blocks like they are able to place shulkerboxes. This could be done with an IC (a Sign placed on the Dispenser/Dropper) but a more elegant solution would be a different way to toggle between block-placing and block-dropping mode. That way the Dispenser/Dropper could be moved around with a piston without the block placing mechanism being destroyed.
You could build automatic wall/floor builders and many amazing redstone creations. Combined with flying machines, elaborate redstone and pipe mechanisms you could event set up a system that might be able to build you a pipe storage system (without signs of course) in any size you want (really just depending, when you would stop the flying machine).
Describe alternatives you've considered
There really isn't one I have found.
- Dominant language
- Java
- Stars
- 321
- Forks
- 165
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EngineHub/CraftBook
-
status:pending type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
status:pending type:bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
status:pending type:bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
status:accepted type:feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
All issues in EngineHub/CraftBook
Similar issues
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OpenAEV-Platform/openaev#8334 ·
Maintainers usually reply within 2 days
-
discussion welcome security waiting for feedback
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
SkyblockerMod/Skyblocker#2767 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 2 days
-
Clock.MakeTime fails to validate hour, minute, and second ranges due to inert Calendar.set try-catchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
mit-cml/appinventor-sources#4139 ·
Maintainers usually reply within 1 day