rheo reports: when the crafting bench has st ... #6146
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6146
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?
rheo reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
note how there's 2 cobble in the first stack, and cobble is then ending up in the output. material doesn't seem to be lost or created ex-nihilo.
credit to AspireMint for discovering this
nevermind, you can dupe materials:
after putting 15 diamonds into the ingredients inventory:
put 90 rainbow into the ingredients side. result: free rainbow block
upstream issue https://github.com/minetest-mods/crafting_bench/issues/14
The insertion and taking is logged, the crafting is not.
So we do have a chance to catch dupers, but we should also add logging to the crafting process.
The autocrafter does it right
i'm tempted to just hard-fork the crafting_bench. upstream has rejected my attempts to fix them mod twice before. my version already fixes this issue.
according to the code it just says "player moves stuff in workbench @ (x,y,z)" without saying what was moved.
A possible temp solution would be to only allow one item to be placed in each grid.
i did a hard fork instead of trying to deal with minetest-mods again. https://github.com/fluxionary/minetest-crafting_bench
The hard fork is now on the testserver.
My advice is to limit some of the bugs like this to admin-only until it is fixed. This prevents abusing.
After testing:
I can't stack things in the recipe slots anymore, however now the workbench works closer to an autocrafter (as in, anything I put in recipe, it behaves as if it were in an autocrafter, putting it in doesn't actually make you place the item, but removing it just makes it vanish. that behavior.)
that's intentional. also, physical items that were previously put into the workbench's crafting grid will be refunded. my reasoning is that the previous behavior is nonsensical. the crafting grid in an autocrafter should be a schema and not an inventory.
Is this on main server now?
No, it will be delivered with the Next update.
QA
Nice, works. Bonus: No need to place the workbench again.
live