Can't place node at feet/near player model

[ak399g]

Don't know if this is a "feature" of 4.9 dev or not, but it's a bug in my book. Very much not happy with it, wondering how to disable it if possible. I used to be able to place nodes in the same space I occupy, which I admit makes little real-world-physics sense but is incredibly useful and needed, especially when placing microblocks. Upgraded from 4.9 to 4.9 dev and now I can't place nodes within close proximity.

[stormchaser3000]

Don't know if this is a "feature" of 4.9 dev or not, but it's a bug in my book. Very much not happy with it, wondering how to disable it if possible. I used to be able to place nodes in the same space I occupy, which I admit makes little real-world-physics sense but is incredibly useful and needed, especially when placing microblocks. Upgraded from 4.9 to 4.9 dev and now I can't place nodes within close proximity.

this is a feature. but this is also able to be disabled by removing some code (i don't exactly know what code so i would ask) and then compiling your build of minetest (ask someone how to do that on your operating system) and then yeah you have removed the not being able to place a block where you are standing thing

[LazyJ]

I agree with ak399g. This new "feature" makes working in tight spots even more difficult. The microblocks are hard enough to target as is. The other new features like the timed item clean-up are some nice improvements.

[cheapie]

If you're playing in singleplayer mode, grant yourself the "noclip" priv (/grant singleplayer noclip) and turn noclip on (press H). There isn't much you can do on servers, unless you've been granted noclip by an admin.

[rubenwardy]

I hate this. It means you can't make a tower by jumping and placing blocks below you.

[BlockMen]

I hate this. It means you can't make a tower by jumping and placing blocks below you.

Thats wrong. You can still do that.

[Amaz]

I hate this. It means you can't make a tower by jumping and placing blocks below you.

Thats wrong. You can still do that.

But it's much harder.
I don't like it.

[Kilarin]

While I agree that it can make some projects more difficult. The point is that you shouldn't be able to embed your own feet within a node of rock. Which makes sense to me.

[ak399g]

But if you did, you could just jump out of it immediately. It makes node placement incredibly obnoxious and at the very least I'd like to know how to turn it off at the source rather than finding a workaround (noclip)

[Kilarin]

But if you did, you could just jump out of it immediately.

But why can you jump out of a block of rock?

Of course, everyone plays the game differently. I find this feature annoying at times as well. But overall, I prefer the slightly added realism of not being able to place a node over my feet.

The idea that this should be able to be switched on and off makes a lot of sense. Different playing styles for different people.

[Amaz]

...The idea that this should be able to be switched on and off makes a lot of sense. Different playing styles for different people.

+1

[Sokomine]

I opened a topic about this very issue some time ago. For now, I constantly have to patch game.cpp in order for it to work correctly again. With microblocks (especially slabs) and other facedir-orientated nodes, it's sometimes impossible to build otherwise. And no, noclip is no alternative - it makes placing those nodes even harder.

In order to fix your own game, edit src/game.cpp:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

diff --git a/src/game.cpp b/src/game.cpp
index 6076ac4..f39126b 100644
--- a/src/game.cpp
+++ b/src/game.cpp
@@ -903,18 +903,9 @@ bool nodePlacementPrediction(Client &client,
                try{
                        LocalPlayer* player = client.getEnv().getLocalPlayer();
 
-                       // Dont place node when player would be inside new node
-                       // NOTE: This is to be eventually implemented by a mod as client-side Lua
-                       if (!nodedef->get(n).walkable ||
-                               (client.checkPrivilege("noclip") && g_settings->getBool("noclip")) ||
-                               (nodedef->get(n).walkable &&
-                               neighbourpos != player->getStandingNodePos() + v3s16(0,1,0) &&
-                               neighbourpos != player->getStandingNodePos() + v3s16(0,2,0))) {
-
                                        // This triggers the required mesh update too
                                        client.addNode(p, n);
                                        return true;
-                               }
                }catch(InvalidPositionException &e){
                        errorstream<<"Node placement prediction failed for "
                                        <<playeritem_def.name<<" (places "


That means: Go to around line 903 and delete all the lines that are preceded in the above code with a "-". Compile again.

[HeroOfTheWinds]

While it is easy to get spoiled by the un-realism of it, I would like to point out that some (if not all) versions of Minecraft have this function. However, I do notice a lot of complaints about microblocks here. Perhaps meet halfway and still allow placement of microblocks in this manner?

[Sokomine]

With 0.4.11, you can add this to your minetest.conf:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

enable_build_where_you_stand = true


It will get rid of the problem. That is, you can build again where you stand. But if you place a node at where your head is, well, then that's your own problem :-)