Post your modding questions here

[kaeza]

Is there any way to alter the node definition values on the fly? For example, if I wanted to smoothly transition a node's alpha using a node timer. Is such a thing possible?

Not currently, other than defining a bunch of nodes with different alpha values, and switch them on the fly.

[dannydanger]

how do i make lava torches?
like
nnn
nln
nsn

n - nothing
l - lava
s - stick

or how do i do it?

[PilzAdam]

how do i make lava torches?
like
nnn
nln
nsn

n - nothing
l - lava
s - stick

or how do i do it?

Ehm..... I dont think this question belongs in this topic.

[Evergreen]

I know this isn't related to modding, but what is the limit to the amount of days/votes that there can be in a poll on the minetest forums? I keep getting an error about it when I try to post.

[Evergreen]

Also, how would I go about detecting a dropped item on top of a node, and if detected, delete it?

[Dan Duncombe]

Are dropped items counted as entities? If they are, might that help?

[Evergreen]

Are dropped items counted as entities? If they are, might that help?

Yes they are entities. I already knew that.

[bdjnk]

I've got some code I'd like to execute whenever a certain type of node is added to the world, including when starting / playing / connecting to the game. Node definitions have lua functions for when hooking to events, for instance on_construct which seemed to most likely candidate, but that doesn't work. Is there some way to do this?

[kaeza]

I've got some code I'd like to execute whenever a certain type of node is added to the world, including when starting / playing / connecting to the game. Node definitions have lua functions for when hooking to events, for instance on_construct which seemed to most likely candidate, but that doesn't work. Is there some way to do this?

on_construct is only called when the node is placed. Unfortunately, what you require is not so easy (if even practical) to implement.

Edit: I assume you mean the code is run *only* once after connecting. Am I mistaken?

[bdjnk]

I've got some code I'd like to execute whenever a certain type of node is added to the world, including when starting / playing / connecting to the game. Node definitions have lua functions for when hooking to events, for instance on_construct which seemed to most likely candidate, but that doesn't work. Is there some way to do this?

on_construct is only called when the node is placed. Unfortunately, what you require is not so easy (if even practical) to implement.

Edit: I assume you mean the code is run *only* once after connecting. Am I mistaken?

I wasn't very clear, sorry. Yeah, I want it to run once, but probably just when the game / server starts. I don't think I need it for all connecting / joining. I would've thought there'd be some kind of mapping / node creation process that occurred which I'd be able to link into...

Still, I gonna try and use register_on_joinplayer or register_on_newplayer and a find_nodes_in_area. I don't think it's the "right" answer, but it might work.

Oh, on that note, what is the difference between register_on_joinplayer and register_on_newplayer? The wiki isn't very clear about it.

[kaeza]

I've got some code I'd like to execute whenever a certain type of node is added to the world, including when starting / playing / connecting to the game. Node definitions have lua functions for when hooking to events, for instance on_construct which seemed to most likely candidate, but that doesn't work. Is there some way to do this?

on_construct is only called when the node is placed. Unfortunately, what you require is not so easy (if even practical) to implement.

Edit: I assume you mean the code is run *only* once after connecting. Am I mistaken?

I wasn't very clear, sorry. Yeah, I want it to run once, but probably just when the game / server starts. I don't think I need it for all connecting / joining. I would've thought there'd be some kind of mapping / node creation process that occurred which I'd be able to link into...

Still, I gonna try and use register_on_joinplayer or register_on_newplayer and a find_nodes_in_area. I don't think it's the "right" answer, but it might work.

Oh, on that note, what is the difference between register_on_joinplayer and register_on_newplayer? The wiki isn't very clear about it.

on_join gets called every time a player joins. on_new is only called every time a *new* player joins your server (i.e. a player that never joined your server before).

[Dan Duncombe]

How do I make a node that plays a certain sound for a certain range upon receiving mesecon signal? Also, how do I change the range? The sound needs to loop as long as a current is being received.
EDIT: Also, with custom nodebox shapes, are the first 3 numbers the box shape, the second 3 the location of the box relative to the node centre?

[1244]

It is possible to write mod in c++?

[kaeza]

It is possible to write mod in c++?

A .dll or .so that can directly interface with the engine, nope.
Only way to "mod" in C/C++ is by writing patches for the engine.

[kaeza]

How do I make a node that plays a certain sound for a certain range upon receiving mesecon signal? Also, how do I change the range? The sound needs to loop as long as a current is being received.
EDIT: Also, with custom nodebox shapes, are the first 3 numbers the box shape, the second 3 the location of the box relative to the node centre?

the first three ones are one corner of the box, and the other three are the other corner.

All positions are relative to the *center* of the node, so -0.5 and 0.5 means the edge. Of course, you can use boxes bigger than a node, but the collision is buggy.

[Mossmanikin]

EDIT: Also, with custom nodebox shapes, are the first 3 numbers the box shape, the second 3 the location of the box relative to the node centre?

The dimensions of a standard node:

Code: Select all

--              { left  , bottom , front  ,  right ,  top   ,  back  }

local cube =    {-0.5   , -0.5   , -0.5   ,  0.5   ,  0.5   ,  0.5   }

[Dan Duncombe]

So...The first 3 are one half of the block, the other three are the other half of the block?

[Mossmanikin]

So...The first 3 are one half of the block, the other three are the other half of the block?

Sort of, yes. But you still need 6 coordinates to draw a "half block".

EDIT: Have you seen this post? VanessaE explains quite well how a nodebox works there.

[yohanes828]

i have edit blocks

[zoropig]

ok so im making a squid mod but everytime i try to start a minetest game i says that it faild. help plz

[zoropig]

how do i make it so that then there will be a boss health at the top of the screen?

[Thermal_Shock]

I have a couple of issues at the moment that are hampering me. Most likely entirely because of my limited experience with coding.

The first is that my modded blocks don't seem to work properly when adding them to the stairs mod from the Minetest game. The new node blocks were defined within the default folder in the nodes.lua file just like the Minetest game. These are my block definitions in the stairs mod.

Code: Select all

--
--This one works fine. The Limestone block uses the default stone ID.
--
stairs.register_stair_and_slab("Limestone", "default:stone",
        {cracky=3},
        {"hg_gls.png"},
        "Limestone Stair",
        "Limestone Slab",
        default.node_sound_stone_defaults())

--
--This one and any other new blocks won't work.
--

stairs.register_stair_and_slab("Red Sandstone", "default:red_sandstone",
        {cracky=3},
        {"hg_rss.png"},
        "Red Sandstone Stair",
        "Red Sandstone Slab",
        default.node_sound_stone_defaults())

My second question is, how do I go about adding a new furnace block that only accepts certain blocks for fuel?

[PilzAdam]

I have a couple of issues at the moment that are hampering me. Most likely entirely because of my limited experience with coding.

The first is that my modded blocks don't seem to work properly when adding them to the stairs mod from the Minetest game. The new node blocks were defined within the default folder in the nodes.lua file just like the Minetest game. These are my block definitions in the stairs mod.

Code: Select all

--
--This one works fine. The Limestone block uses the default stone ID.
--
stairs.register_stair_and_slab("Limestone", "default:stone",
        {cracky=3},
        {"hg_gls.png"},
        "Limestone Stair",
        "Limestone Slab",
        default.node_sound_stone_defaults())

--
--This one and any other new blocks won't work.
--

stairs.register_stair_and_slab("Red Sandstone", "default:red_sandstone",
        {cracky=3},
        {"hg_rss.png"},
        "Red Sandstone Stair",
        "Red Sandstone Slab",
        default.node_sound_stone_defaults())

There is no node called "default:red_sandstoe" in the default mod, so the recipes wont work.

[Thermal_Shock]

There is no node called "default:red_sandstoe" in the default mod, so the recipes wont work.

Oh. You misunderstand. My new node's are added to the node.lua file.

Edit:

Well this is interesting. It seems removing the space in "Red Sandstone" to "RedSandstone" fixed the issue and now it works as intended.

Code: Select all

stairs.register_stair_and_slab("RedSandstone", "default:red_sandstone",
        {cracky=3},
        {"hg_rss.png"},
        "Red Sandstone Stair",
        "Red Sandstone Slab",
        default.node_sound_stone_defaults())

What exactly is that first part for then?

[ch98]

My concrete 2.2 mod seems to shut server down when you dig the concrete.
Code causing the problem most likely is...

Code: Select all

minetest.register_node("concrete:concrete", {
    description = "Concrete",
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete4")
    end,
})

minetest.register_node("concrete:concrete1", {
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete2")
    end,
})

minetest.register_node("concrete:concrete2", {
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete3")
    end,
})

minetest.register_node("concrete:concrete3", {
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete")
    end,
})

minetest.register_node("concrete:concrete4", {
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete5")
    end,
})

minetest.register_node("concrete:concrete5", {
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete6")
    end,
})

minetest.register_node("concrete:concrete6", {
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
})

minetest.register_node("concrete:reinforced_concrete", {
    description = "Reinforced Concerte",
    tiles = {"concrete_concrete.png"},
    is_ground_content = true,
    groups = {cracky=1},
    drop = "concrete:gravel_mound",
    after_destruct = function(pos)
        minetest.env:set_node(pos, "concrete:concrete1")
    end,
})

can you find the problem?