Changing a nodes definition at runtime?

[DylanOwen]

Do you ever think minetest will have the ability to change a nodes, craft items, or tools definition at runtime? Is this already something that is under development?

Also... what is your opinion about this? Do you think it would be useful? I do... for example changing a nodes texture (instead of replacing the node), or changing the sounds it makes.

In my experience in programming, you NEVER KNOW what you may need in the future. One moment you say "that's ridiculous why would I ever need that", then later on you think "oh... that's why I need that".

[Hume2]

The annoyance I'm facing is that the node definition doesn't allow any variance. The only variance it allows is changing the metadata but one can't change the texture, collisionbox etc.. If I want a node to change its texture, I need either a different node or use entities. Entities are laggy and unreliable and using a different node requires me to register a node for each possible combination. And one can't register more that 32768 nodes.

[Pyrollo]

If you could change node definition on the fly, it would change all nodes of this type.
If you want to change a simple ocurence of a node, then changed stuff could not go in definition and has to be stored on a per node basis (IE in metadata).

Sure it lacks some flexibility, especially about textures (hope something will be done.. a day). If you want a somehow reliable entity hack, you can use display_api.

[Pyrollo]

If you lack the reality, go on a trip or find a job.

Love your signature. This is a very good answer to those who want Minetest to be a real world simulator.