[Solved] How to redefine a minetest.register_craft recipe?

[Hamlet]

---2nd edit begin

Thanks to GreenDimond and Linuxdirk, the correct method is:

To remove the old recipe:

Code: Select all

minetest.clear_craft({output = "mod_name:node_name"})

To create a new one:

Code: Select all

minetest.register_craft({
   output = "mod_name:node_name",
   recipe = {
      {new recipe},
   }
})

---2nd edit end

Example of the recipe to be redefined:

Code: Select all

minetest.register_craft({
   output = "mod_name:node_name",
   recipe = {
      {"default:dirt", "default:stone",},
   }
})

Example of how I am trying to redefine it:

Code: Select all

minetest.override_item("mod_name:node_name", {
   recipe = {
      {"default:gold", "default:silver",},
   }
})

---EDIT: Just to make it clear (if it wasn't already), it doesn't work.

From the lua_api.txt (v0.4.16):

--- quote start
* `minetest.override_item(name, redefinition)`
* Overrides fields of an item registered with register_node/tool/craftitem.
* Note: Item must already be defined, (opt)depend on the mod defining it.
* Example: `minetest.override_item("default:mese", {light_source=LIGHT_MAX})`
--- quote end

Given that the registration method isn't register_node/tool/craftitem, it isn't possible to redefine such a recipe using minetest.override_item; if I have understood it correctly.

Any hints/help please?

[Linuxdirk]

If it is a registered node, tool, or craftitem you can overrride it as shown in the documentation using minetest.override_item(). As stated in the documentation the thing has to be registered already. Since the function does not care HOW the thing was registered it is just important THAT the thing was registered.

OT: Registering things in Minetest not using the designated API function for that is stupid and should be avoided.

[Hamlet]

If it is a registered node, tool, or craftitem you can overrride it as shown in the documentation using minetest.override_item(). As stated in the documentation the thing has to be registered already. Since the function does not care HOW the thing was registered it is just important THAT the thing was registered.

OT: Registering things in Minetest not using the designated API function for that is stupid and should be avoided.

Out of curiosity, have you read my post's contents before replying or have you read just the title?
Just for the record (in reply to the OT): http://dev.minetest.net/minetest.register_craft

[GreenXenith]

This is the way I do it, though I have no idea if this is the best way.

Code: Select all

minetest.register_craft({
   output = "mod_name:node_name 0",
   recipe = {
      {original recipe},
   }
})

(note the 0 in the output)
and then

Code: Select all

minetest.register_craft({
   output = "mod_name:node_name",
   recipe = {
      {new recipe},
   }
})

[Linuxdirk]

Out of curiosity, have you read my post's contents before replying or have you read just the title?

You mean before you edited it to clarify what the actual issue is? Your English and your posting style make it hard to understand what you actually want.

As far as I understand you want to alter a craft recipe.

The intended way of doing this is first deleting the craft recipe and then registering a new one.

http://dev.minetest.net/minetest.clear_craft
http://dev.minetest.net/minetest.register_craft

[Hamlet]

This is the way I do it, though I have no idea if this is the best way. [snip]

It works nicely!
Go figure that I had thought about that method but immediately discarded the idea 'cause I thought that would have registered an alternative recipe for the same item, when it actually just redefines it.

This tells a lot about wrong assumptions!

Thanks for your help, you've saved a lot of my time since I need to tweak some mods' recipes for my subgame - manually modifying them isn't exactly the best way.

[Hamlet]

You mean before you edited it to clarify what the actual issue is? Your English and your posting style make it hard to understand what you actually want.

Do you mean that by simply adding
"---EDIT: Just to make it clear (if it wasn't already), it doesn't work."
my whole post has become intelligible? Impressive.

As far as I understand you want to alter a craft recipe.

The intended way of doing this is first deleting the craft recipe and then registering a new one.

http://dev.minetest.net/minetest.clear_craft
http://dev.minetest.net/minetest.register_craft

Brilliant, this is indeed the best way; GreenDimond's method works but I guess that if there is a "minetest.clear_craft" probably it's better to remove the old crafting recipe and then register a new one instead of forcing a new recipe for the same item - just to be double sure.

Thanks for your help, this will ensure that no possible side-effect glitches will happen.

[Linuxdirk]

but I guess that if there is a "minetest.clear_craft" probably it's better to remove the old crafting recipe and then register a new one instead of forcing a new recipe for the same item - just to be double sure.

Yes, feels much cleaner than overriding the item definition.

[Lone_Wolf]

minetest.clear_craft({output = "mod_name:node_name"})

This works for tool and craftitem recipes too?
EDIT:
Assuming you just change

Code: Select all

minetest.clear_craft({output = "mod_name:name"})

to

Code: Select all

minetest.clear_craftitem({output = "mod_name:name"})

[Linuxdirk]

This works for tool and craftitem recipes too?

The name is a bit misleading. You can delete whatever you want that is identified by the provided definition.

Beware: Deletion by recipe is extremely slow.