Jammy reports: add the ability to use all blo ... #5713
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#5713
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Jammy reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I asked the user to clarify what they mean by that
I assume "all blocks of one type" would translate to all blocks in given group (i.e. group:trunk, group:wood .... ) as many recipes take as input any ingredient from certain group.
if you've got a 5.8 (or 5.7?) client, you can certainly pick up a stack of items, and right-click-drag it across all the slots in the crafting grid in the autocrafter. but you cannot do the same with a single stick. the sticks that are "placed" into the crafting grid, end up in your main inventory in their own stack:
you cannot fill the grid quickly while only wielding a single stick - each time you place it in the crafting grid, it goes back into your inventory.
i'm not sure whether or not this is fixable without a client/engine change, and possibly a fundamental one. i think the current behavior works by specifying an
allow_put
callback which adds the item to the grid, but reports to the engine (and client) that nothing can be put in that slot.if instead the
allow_put
callback indicated that the item could be put in the grid, we'd have to refund the item in theon_put
callback. but doing so would also put the item back into the player's inventory, and not into their "hand".