Post your modding questions here

[kaeza]

Topic: How to know that user clicks "Esc" to exit a formspec?
Reason: I want to update my mod "Password Chest".

Check for a field named `quit` in your receive fields callback:

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

if fields.quit then
  -- Do something here
end


[D00Med]

https://s31.postimg.org/5nhckihnf/screenshot_20160616_081407.png
I've been trying to make a centipede for mobs_redo.
The head segment is a seperate mob, and it spawns segments behind it.
Unfortunately there are two problems;
1: there is a gap between the head and body(as shown in the screenshot)
Currently this is what spawns the bodyparts:

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

do_custom = function(self, dtime)
      local pos = self.object:getpos()
      minetest.env:add_entity(pos, "horror:centipede_body")

      minetest.after(0.5, function()
      minetest.env:add_entity(pos, "horror:centipede_body")
      end)
   end,

Is there a faster of better way I could do this?
2: The body segments keep running away and not chasing after the head as they should.
They are set to attack monsters(the head), so they should be following it. Is there a better way to make them follow the head?

[iangp]

Topic: How to know that user clicks "Esc" to exit a formspec?
Reason: I want to update my mod "Password Chest".

Documentation :D your best friend:
http://dev.minetest.net/minetest.regist ... ive_fields

"If a player uses ESC to exit a formspec, this will return {["quit"] = "true"}."

[KCoombes]

https://s31.postimg.org/5nhckihnf/screenshot_20160616_081407.png
I've been trying to make a centipede for mobs_redo.
The head segment is a seperate mob, and it spawns segments behind it.
Unfortunately there are two problems;
1: there is a gap between the head and body(as shown in the screenshot)
Currently this is what spawns the bodyparts:

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

do_custom = function(self, dtime)
      local pos = self.object:getpos()
      minetest.env:add_entity(pos, "horror:centipede_body")

      minetest.after(0.5, function()
      minetest.env:add_entity(pos, "horror:centipede_body")
      end)
   end,

Is there a faster of better way I could do this?
2: The body segments keep running away and not chasing after the head as they should.
They are set to attack monsters(the head), so they should be following it. Is there a better way to make them follow the head?

You can define a 'follow' item that is wielded by the head (could be invisible), but all body segments would "stand" on top of each other trying to follow the head - I've seen this happen with taming mobs.

[D00Med]

How does a mob hold an item? I had a look in the mobs_redo api, and it looks like mobs only follow what players are holding. I have managed to improve it a little by changing the speed of the segments and body, and the time after which they disappear. It works ok until the centipede hits a tree or a wall.

[Diamond knight]

What time speed do i set the minetest.conf to to make days last an irl hour and nights last an irl hour

[everamzah]

# Examples: 72 = 20min, 360 = 4min, 1 = 24hour, 0 = day/night/whatever stays unchanged. That's a setting, though, not a modding code. (The answer is 1.)

[KCoombes]

What time speed do i set the minetest.conf to to make days last an irl hour and nights last an irl hour

Based on the examples in the previous post, the time setting of 12 should give you a 2 hour day cycle (1 day and 1 night).

[TenPlus1]

DOOmed, if you add head and segments together you can use something like this:

local mob = minetest:add_entity(pos, "horror:centipede_head")
local ent = mob:get_luaentity()

mob = minetest:add_entity(pos, "horror:centipede_body")
local ent2 = mob:get_luaentity()
ent2.following = ent -- this makes body (ent2) follow head (ent) and can be used on as many segments as u like to follow previous parts...

...this gives you access to MANY of the internal variables that mobs api uses to control them from attack styles, health, gotten (for milk/wool) etc.

[D00Med]

Haha it's with two 0's :P
But thanks, I'll try this now

[D00Med]

Ok... I just realised I have no idea what I'm doing with this, where do I put it?
Do I need to make a new way to spawn the centipede, using that function(that is a function isn't it?)?
Haha thanks for all your help with my mobs.

[TenPlus1]

When you spawn the centipede head, place body parts inside do_custom by adding a flag like this:

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

   do_custom = function(self)
      if not self.centipede then
         minetest.chat_send_all(">>> This message is only shown once at spawn")
         self.centipede = true
      end
   end,

... and remember on adding each segment to use the code above to have it follow the previous one.

[D00Med]

Ok I tried that(in lots of different ways since I still don't really understand), and I keep getting the error:
"Invalid position coordinate 'x'(expected number got nil)"
I have tried using local pos = self.object:getpos(), and adding 'pos' to function(blah, 'pos' here)...
This is difficult to explain without knowing the right terminology.

[TenPlus1]

Insert this code into the centipede head definition and see if it works:

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

do_custom = function(self)

    if not self.centipede then
        self.centipede = true -- flip switch so this part is done only once

        -- get head position and define a few temp variables
        local pos = self.object:getpos()
        local mob, ent, ent2

        -- get head entity
        ent = self.object:get_luaentity()

        -- add body and make it follow head
        mob = minetest:add_entity(pos, "horror:centipede_body")
        ent2 = mob:get_luaentity()
        ent2.following = ent

        -- add body and make it follow previous body segment
        mob = minetest:add_entity(pos, "horror:centipede_body")
        ent = mob:get_luaentity()
        ent.following = ent2

    end
end,

[D00Med]

Still the same problem. Even when I used a specific location instead of 'pos', I got the same error.
I tried googling the error too, and found nothing very helpful.

[Byakuren]

Still the same problem. Even when I used a specific location instead of 'pos', I got the same error.
I tried googling the error too, and found nothing very helpful.

Post your code and error on a paste site (like lpaste.net) in separate pastes.

[D00Med]

Why? can't I just paste it here?

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

2016-06-18 17:24:09: ERROR[Main]: ServerError: Lua: Runtime error from mod 'horror' in callback ScriptApiEntity::luaentity_Step(): Invalid position coordinate 'x' (expected number got nil).
2016-06-18 17:24:09: ERROR[Main]: stack traceback:
2016-06-18 17:24:09: ERROR[Main]:    [C]: in function 'add_entity'
2016-06-18 17:24:09: ERROR[Main]:    ...est-0.4.14-dev-win64-decbd39\bin\..\mods\horror/mobs.lua:84: in function 'do_custom'
2016-06-18 17:24:09: ERROR[Main]:    ...t-0.4.14-dev-win64-decbd39\bin\..\mods\mobs_redo/api.lua:2108: in function <...t-0.4.14-dev-win64-decbd39\bin\..\mods\mobs_redo/api.lua:2052>

like this?

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

do_custom = function(self)

        if not self.centipede then
            self.centipede = true -- flip switch so this part is done only once

            -- get head position and define a few temp variables
            local pos = self.object:getpos()
            local mob, ent, ent2

            -- get head entity
            ent = self.object:get_luaentity()

            -- add body and make it follow head
            mob = minetest:add_entity(pos, "horror:centipede_body")
            ent2 = mob:get_luaentity()
            ent2.following = ent

            -- add body and make it follow previous body segment
            mob = minetest:add_entity(pos, "horror:centipede_body")
            ent = mob:get_luaentity()
            ent.following = ent2

        end

and this?
I'll do it if it's needed though

[Byakuren]

It's so we can find the line numbers mentioned in the error. It's hard to figure out where they are without the entire file, and it's hard to navigate the entire file from the forum code viewer.

[D00Med]

Oh ok, well the code is here: http://lpaste.net/166733

[TenPlus1]

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

do_custom = function(self)

        if not self.centipede then
            self.centipede = true -- flip switch so this part is done only once

            -- get head position and define a few temp variables
            local pos = self.object:getpos()
            local obj, obj2, ent

            -- add body and make it follow head
            obj = minetest:add_entity(pos, "horror:centipede_body")
            ent = obj:get_luaentity()
            ent.following = self.object

            -- add body and make it follow previous body segment
            obj2 = minetest:add_entity(pos, "horror:centipede_body")
            ent = obj2:get_luaentity()
            ent.following = obj

            -- add body and make it follow previous body segment
            obj = minetest:add_entity(pos, "horror:centipede_body")
            ent = obj:get_luaentity()
            ent.following = obj2

        end
end,

[D00Med]

Still the same, perhaps it would be best if I just improved the method I was using before.

[Byakuren]

What gets printed out if you print(dump(pos)) before trying to add the entity?

[D00Med]

I think this is it: WARNING[Main]: Map::getNodeMetadata(): Block not found

[Byakuren]

It should be printing out a table, look for something like

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

{
   x = 42,
   y = 69,
   z = 666,
}


(Or post your debug output)

[D00Med]

I tried printing/dumping, but couldn't find anything in debug.txt, so I did it in chat, using pos_to_string, and I a similar result to what you have there, so that means that the position isn't the problem right?

[Byakuren]

I tested it on my own computer and found the bug after half an hour. You are calling add_entity with method syntax, which passes the minetest table as the first input.

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

minetest:add_entity(pos, "blah")

-- Which translates to
minetest.add_entity(minetest, pos, "blah")


add_entity's first argument is supposed to be the position, so it looks for the x coordinate in minetest, which of course there is none, and then complains. You need to call it as

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

minetest.add_entity(pos, "blah")


+ Spoiler

Aren't we glad that Lua functions have no arity?

[D00Med]

It works, thanks!
I am now kicking myself for not trying that earlier, I've had similar problems before.

[darkflamez]

I would like to know on how should I start modding the game since I am a newbie. Also I have read a few tutorials on the game but I am still not clear.

I would also like to know on how some of the modders on this forum got started.

[TenPlus1]

This is usually the first step in modding in minetest: http://rubenwardy.com/minetest_modding_book/

[Hybrid Dog]

I would also like to know on how some of the modders on this forum got started.

l edited other mods, at first just simple stuff and then gradually more and more complicated changes,
I DID NEVER LEARN FROM THAT MODDING BOOK, tenplus1

Even if you e.g. only change "Dirt" (the description of the default:dirt node) to "brown node" in the nodes.lua file of the default mod, you performed modding.