FOSS gamedev and creative worlds

Are you making a new mineral/ore/gem/thing that shouldn't be physically possible to make into a tool but somehow need to be added to minetest anyway?

Are you going to make a tool out of that new thing?

Try the add_tool mod!

Latest at https://gitorious.org/marktraceur-minetest-mods/add_tool
See below for current release

Usage example:



Releases:

0.1 -- initial
Download at https://gitorious.org/marktraceur-minetest-mods/add_tool/archive-tarball/0.1
Last commit was https://gitorious.org/marktraceur-minetest-mods/add_tool/commit/0f984e86f2b36d1af721a037537823ba952da53d

cool )

Why make it a mod and not simply release the code, since it's just a function ?

ironzorg wrote:Why make it a mod and not simply release the code, since it's just a function ?

Well, since it relies on minetest-specific code, I figured it would be best to use the minetest dependency management structure, instead of simply calling it a Lua function. Plus, I greatly prefer organizing all of my minetest-related code on gitorious, it's a far simpler way to do things.

Other reason: End users know how to unpack mods, they don't know how to put a function in the right place (most of the time).

Cool Idea!

I have no clue how this thing works :/

Could someone please explain how this works??? I'm trying to make a few tool/weapon mods, but I can't seem to find a way how...

Yes.

First, put add_tool in your mod's depends.txt, so you can't run your mod without mine. This will ensure that users install mine before yours (suggest that you link to mine in your documentation).

Second, call register_tool_type with the specified options (see init.lua for more).

I understand now, thanks

Updated it for 0.4-dev-20120122-1: http://paste.pocoo.org/show/539320/

There should be a way to set the description of the new tools, though. A new parameter?