Destroying blocks miss

[Ygarr]

Minetest version

last

Behaviour: When you make 1 move to detroy block - its not enough to destroy 1 block. But when you make 2 moves by hand you destroy 3 blocks.

So you need to select duration of click mouse button to destroy only what you need, which depends on fps of your game e.g. And it`s hard...

Think it would be enough copy from minecraft`s creative mode behaviour in this case. 1 click or 1 hand move to destroy respectively 1 block

[neoh4x0r]

@Ygarr have you tried setting safe_dig_and_place to true in minetest.conf ? By default this is disabled

The main benefit of this setting is that only one node is placed or dug per mouse click -- no repeats.

#    Prevent digging and placing from repeating when holding the mouse buttons.
#    Enable this when you dig or place too often by accident.
safe_dig_and_place (Safe digging and placing) bool false

https://github.com/minetest/minetest/blob/c47313db65f968559711ac1b505ef341a9872017/builtin/settingtypes.txt#L120

[Ygarr]

Just tried. Thanks for the interesting option, in principle it can be considered a compromise solution, especially for the first time. Better than nothing

[Ygarr]

The "Repixture" have correct behaviour of destroying-breaking blocks. Practically Without frustration. It would be good to have opportunity repeat such experience in other games

[SmallJoker]

Minetest only handles dig_immediate groups in a special way. This means that, by default, no other node group can be dug using the wieldhand. https://github.com/minetest/minetest/blob/edf098db637bf74d4675ce900dc9c0b8ee528a03/src/tool.cpp#L189-L199

This is a Minetest Game issue because it overrides the wieldhand to allow digging of the common nodes. Relevant code: https://github.com/minetest/minetest_game/blob/c96cc55c406b00abaaf1f847eab8dbe4abc03286/mods/default/tools.lua#L6-L20

Please tweak those values and propose a PR so it can be discussed.

[Wuzzy2]

Umm, does anyone understand the bug report here? I don't understand a single word.

[appgurueu]

I believe safe_dig_and_place basically fixes the issue though (and this is thus not a MTG issue)? Krock seems to be suggesting that the values could be tweaked to "slow down" digging of some nodes?