FOSS gamedev and creative worlds

1. What is max_drop_level=# (tool)
2. What is max_level=# (also tool)
3. How (if possible) do you make a chat_send_all when a player digs a certain node?
4.How do you make a tool light up while you wield it? (like the mese pickaxe in the walking light mod)

I figured most of it out on my own. However, I did get this.



Here is the code.

For max_drop_level and max_level I suggest reading the documentation for the groups and damage in the lua_api.txt file that comes with the game download. For chat_send_all you'll probably want to set a custom after_dig_node callback on the node type. For a SPECIFIC node (as in one at a particular location) where you aren't in control of the node type you might not have that option, and might have to use the global minetest.register_on_dignode() instead (but avoid this if possible).

For making a tool light up, you really can't. The walking light mod is a really dirty hack that replaces nodes around a moving character with invisible lit up nodes (basically invisible torches). This doesn't work very well in water or if the player is moving past a real torch or something; the mod will actually replace other nodes as you move past them. That's not a dig at the mod creator; it's just unfortunately the only way to fudge a moving light in the game right now.

It looks like you forgot the equals sign for "description" in the tool definition.

Menche wrote:It looks like you forgot the equals sign for "description" in the tool definition.

Good catch. This should by all rights be a syntax error, but unfortunately the designers of the Lua language decided you should be able to call a function with a single string literal parameter without using parentheses. This is a thorn in everyone's side at some point or another.

There's another problem that is causing the actual error message though. The table with the tool definitions actually must be a parameter to the minetest.register_tool() call, but there is a closing parenthesis that terminates the function call before it. Compare the following:



(The same goes for the call to minetest.register_node() farther down.)

prestidigitator wrote:For making a tool light up, you really can't. The walking light mod is a really dirty hack that replaces nodes around a moving character with invisible lit up nodes (basically invisible torches). This doesn't work very well in water or if the player is moving past a real torch or something; the mod will actually replace other nodes as you move past them. That's not a dig at the mod creator; it's just unfortunately the only way to fudge a moving light in the game right now.

Is there a way to make an entity light up? Or to make it so the player is bound to an entity, but the player moves the entity(not the entity moves the player)?

Ok, I figured this out. The sword is effing awesome. One problem though, Mese and Trees will NOT cut for some reason. I hack away at them forever and they don't break. Also for some reason my node that drops the sword is not showing the image, instead it's showing the unknown block image. Any ideas? I would like to release this today if possible.

Here is the code.


Edit: The inventory image work, but not when I place it.
Edit2: My new node wont break with the sword either.

Fixed the image not displaying. (I forgot the {} brackets)

Made a TODO list.
1. Make it break; my new node, mese, and trees.
2. Write a callback to chat_send_all when my node is dug.
3. RELEASE!

Those are not in order. It's actually 1,3,2.

---Screenshots---
Sword on the ground.

Sword in hand.

Node (drops the sword)

rarkenin wrote:Is there a way to make an entity light up? Or to make it so the player is bound to an entity, but the player moves the entity(not the entity moves the player)?

At this time, no. Only nodes can generate light, not entities. Frustrating.

I hate to be a bug, but can someone help me with the sword not digging those blocks.
Also, could someone write the callback for when someone digs the node.

I would like it to say "<player> just found the Sword In The Stone and received the Sword Of Ultimate Power at <position>. Congratulations!"

If I can get help with these two things I can release by midnight. YOU WILL GET CREDIT FOR YOUR HELP!!!

Thanks in advance. ----Tedypig

Figured out the not digging, not it wont hurt other players. Help?

To hurt players you need the "fleshy" group in the tool capabilities.

The callback should be relatively simple. Just call minetest.chat_send_player() or minetest.chat_send_all() in the after_dig_node() callback on the node.

prestidigitator wrote:To hurt players you need the "fleshy" group in the tool capabilities.

The callback should be relatively simple. Just call minetest.chat_send_player() or minetest.chat_send_all() in the after_dig_node() callback on the node.

I have fleshy as the same setting as all the other groups, I just can't get it to hurt people. I have it as a one hit dig/chop/cut/kill.

Huh. And PVP is enabled? Do other weapons hurt other players?

prestidigitator wrote:Huh. And PVP is enabled? Do other weapons hurt other players?

If by PvP you mean damage enabled, then yes I do. Also, yes the other weapons hurt. I don't friggen get it. Lol.

This is how the damage system works:


You can have up to 0.8 of "punch time" (silly self-invented term). You'll deal 2 damage (= 1 heart) to entities with fleshy=3, 1 damage to entities with fleshy=2 and no damage to entities with fleshy=1.

Q:How Many Players can be on one server?

Likwid H-Craft wrote:Q:How Many Players can be on one server?

Probably thousands. :P
If you want to ask a question, you should create a new topic instead.

Calinou wrote:This is how the damage system 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

minetest.register_tool("default:sword_steel", {
    description = "Steel Sword",
    inventory_image = "default_tool_steelsword.png",
    tool_capabilities = {
        full_punch_interval = 0.8,
        max_drop_level=1,
        groupcaps={
            fleshy={times={[1]=2.00, [2]=0.80, [3]=0.40}, uses=10, maxlevel=2},
            snappy={times={[2]=0.70, [3]=0.30}, uses=40, maxlevel=1},
            choppy={times={[3]=0.65}, uses=40, maxlevel=0}
        }
    }
})

You can have up to 0.8 of "punch time" (silly self-invented term). You'll deal 2 damage (= 1 heart) to entities with fleshy=3, 1 damage to entities with fleshy=2 and no damage to entities with fleshy=1.

Right, I know. I read the ones for the wood,stone, and steel swords, but I wanted a "one hitter quitter". Is there a way to do that? Right now everything else is one click destroy, I don't see why this can't be set to fleshy also.

(I meant PVP as in there is a server option that can be used to turn off PVP damage. This is separate from whether damage is enabled at all, I believe. Anyway, this isn't the issue if other weapons are working.)

I really don't know what the behavior will be if the times are set to zero. You could try a really small value (e.g. 0.001) instead, maybe. As Calinou said, you might try defining full_punch_interval too. This could be a small value too. Basically I think the ratio of full_punch_interval/times[...] it going to be the maximum damage the weapon does, and it will do this much damage on the first swing and if you wait pull_punch_interval between swings.

More about entity damage can be found in lua_api.txt, and I've added a synopsis to the LuaEntitySAO article on the dev wiki.

Of course, if you want a really, really sure way to kill a player with a weapon in one hit, forget the built-in damage and do something like this:


That should do a one-swing kill on literally anything. The code is untested, so there might need to be a small change or two.

Everything is still the same, but now it takes two hits to remove a node instead of one. No damage to other players or mobs.

With THAT code? Erm.... Maybe throw some debug statements in then and see what branches of the code you are reaching with various uses. I don't know what else to tell you.

prestidigitator wrote:With THAT code? Erm.... Maybe throw some debug statements in then and see what branches of the code you are reaching with various uses. I don't know what else to tell you.

I hit a vombie.

13:45:24: ACTION[ServerThread]: LuaEntitySAO at (266.17,11.7,-260.087) punched by player Teddypig, damage 0 hp, health now 8 hp

This is how I did the code. Is it right?

Oh. No, it's not. "on_use" should come before or after "tool_capabilities", not inside it. Actually you could probably just REPLACE tool_capabilities with it, since I don't think the tool capabilities will be used if you have an explicit on_use handler.

NOW, still no damage (doesn't even register that I swung it), and no continuous hitting. It DOES however remove a block with one hit. I apologize if I'm being a bother.

No bother at all. Try putting this statement just before the if-statement in on_use:

That should tell us what the weapon thinks you are swinging at, and if the "pointed_thing" is behaving the way we're told is does.

Well I feel like it.

Debug info.

I dug two dirt_with_grass, swung at a sheep a few times and the dug two/three stone.

Oh! Sorry. I guess ObjectRef:get_player_name() returns an empty string for non-players, not nil. Change the conditional to read:



That should fix it for non-player entities. You tested it on a player also?

OK, this is what I have right now.


Where do I put what you said?