Right to a Name

Right to a Name (abbreviated RTAN) is a policy enforced by ContentDB where every modname (the technical name of a mod) needs to be unique. For the official policy see Package Inclusion Policy and Guidance § 3.1. Right to a Name.

The reason for its enforcement is due to the Minetest dependency system requiring unique technical names and can’t distinguish several mods with the same technical name. They will be treated as the same mod and any mods depending on it would break if the wrong incompatible version was enabled.

Checking

ContentDB has a page where you can check whether a modname exists, both on ContentDB and on the Minetest Forums.

https://content.minetest.net/modnames/<modname>/

If you have uploaded your package, an alert will pop up on the package page if it contains technical names that already exist on ContentDB.

Just because this message shows up doesn’t necessarily mean you are violating the policy, as the name conflicts could fall under the exceptions mentioned below. The message is also used for ContentDB Editors to quickly check the validity of technical names used in a package during review.

Exceptions

The rule does not apply when a mod is included verbatim in a game. If the mod is lightly modified, then it should be fine too. Generally the mod should be roughly equivalent to its upstream counterpart API-wise, such that other mods depending on it still function.

This also means that reimplementations of mods are exempt, as they could serve as a drop-in replacement for the mod’s API.

Game namespacing

It is standard practice when making games to prefix your game’s modnames such that they don’t have any risk of conflicting with other modnames. For example, NodeCore uses the nc_ namespace. A list of namespaces used by games on ContentDB can be seen at Game Namespaces.

Game namespacing doesn’t apply for Minetest Game’s mods, assuming that they are compatible with mods that depend on Minetest Game’s mods and aren’t heavily modified.