machine and block aren't ground content v1 PROPOSED

Luke aka SwissalpS: 1
 machine and block aren't ground content

 1 files changed, 2 insertions(+), 0 deletions(-)

[PATCH] machine and block aren't ground content Export this patch

see https://github.com/pandorabox-io/pandorabox.io/issues/836

---
 init.lua | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/init.lua b/init.lua
index 49e720b..eef341d 100644
--- a/init.lua
+++ b/init.lua
@@ -179,6 +179,7 @@ minetest.register_node(
         paramtype = "light",
         paramtype2 = "facedir",
         groups = {cracky = 2},
+        is_ground_content = false,
 
         -- "Can you dig it?" -Cyrus
         can_dig = function(pos, player)
@@ -263,6 +264,7 @@ minetest.register_node(
     {
         description = S("Ehlphabet Block (blank)"),
         tiles = {"ehlphabet_000.png"},
+        is_ground_content = false,
         groups = {cracky = 3}
     }
 )
-- 
2.44.0

Blockhead <jbis1337@hotmail.com>

6 months ago

Hi SwissalpS,

Thanks for sending these patches through. I assume  you have a branch 
with them
as 3 commits in order. Could you either re-run git format-patch to create a
patch set for the entire branch (this creates files like 0001, 0002, 
0003) and
re-send that to the list, or at least tell us what order the patches 
should be
applied?

This isn't a lot of people's normal workflow, so here's a quick tutorial 
on the
email workflow. To send multiple patches as a set, first ask format-patch to
make a series for your branch, e.g.

  $ git format-patch master

That should create files prefixed 0001, 0002, 0003 with the commit messages.

Then to send the entire patch set, mention each file by name in order 
with git
send-email:

  $ git send-email 0001-... 0002-...

If you can do that it will help because gpcf will be able to apply the 
patches
easily in order with `git apply`. Thanks.