Rethinking the bucket #1746
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#1746
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?
The bucket mechanic in this minetest is a pure rip-off of minecraft. You take an empty bucket (which stack), click on a liquid source node, which disappears, and you end up w/ an unstackable "bucket of liquid". Trying to "place" that bucket results in placing the original source node. Crafting things with fluids, or moving fluids around, becomes incredibly tedious, and all sorts of bugs happen regarding whether or not to return the bucket to the player or not when crafting.
What if, instead, the bucket behaved like other tools? You'd have to "dig" liquid source nodes, and you'd end up w/ the source nodes in your inventory. "Bucket of X" would not exist. Digging a flowing liquid node would destroy it, but not pick anything up - and then it'd probably reflow again immediately.
You could then create bucket "tiers" like existing tool tiers. Wooden buckets could be used to pick up water. Steel (or something stronger?) could be used to pick up lava. Special buckets might be able to dig liquids faster.
Buckets could have durability.
Perhaps only enchanted steel buckets could dig up lava.
Another variation: a bucket that automatically freezes liquid nodes when they are picked up (water -> ice, lava -> obsidian).
Downsides:
Pretty sure minecraft ripped that idea straight of RL ;-)
I really like your ideas about tiers and durability but wouldnt change how buckets work because everyone just understands that but bigger containers like barrels that can hold more fluids would be nice.
"It's totally unrealistic to stack multiple buckets of water!"
"Oh, sure, but its totally realistic to stack multiple cubic meters of rock"
Does this pose any danger? Can you do something with water blocks that is not possible with buckets?
To the contrary IMO, buckets are harder to detect than simple block placement.
We could alias every filled bucket to their respective source, but that would lose people the bucket.
Is it more generic than before? Yes. With this system we can pick up ANY liquid.
Problems I see:
not true, if the liquid doesn't belong to the appropriate group, just as not all nodes can be broken w/ a pickaxe.
cow milk comes to mind. looks like the other examples are "cactus pulp" from ethereal and bucket of chicken legs from petz, which are foods and could remain as they are. is there something i'm missing?
I took a tentative stab at this:
https://github.com/fluxionary/minetest-bucket_redo