From the start my prior PR was aiming at compatibility with legacy clients and servers. If you scan the MT forum you will become aware that there seem to be quite many MT 0.4 servers around which are actively used by many players.
However, the best solution may be this example of a new piece of improved code, if I understand the MT Lua code correctly.
```
-- print to log after mod was loaded successfully
local load_message = "[MOD] XXX loaded"
if minetest.log then
minetest.log("info", load_message) -- aims at state of the art MT software
else
print (load_message) -- aims at legacy MT software used in the field
end
```
Hope this helps.
* Begin work on "armors as modpack" refactor letting anyone to enable/disable any armors they want as mods rather than obscure settings
* Fix some steel armor mishaps, remove pointless dependency on "default"
* Move admin armor into mod
* Make wood armor into a mod
* More consistent steel description text etc.
* remove wood references from 3d_armor api locale
* remove admin armor reference from 3d_armor locale template.txt
* Remove steel textures from api
* Bronze armor as mod
* Fix admin, wood armor missing local S translator var
Fix wood locale missing template.txt
* Fix bronze missing locale
* Cactus as mod
* Crystal into mod
* Diamond into mod
* Mithril and Gold as mods
* Register armor fix
* Nether as mod
* Clean-up, add optional depends for mod armors, remove armor.lua from 3d_armor
* Fix badly named mod.conf for admin, gold, nether armors
Fix attempt to register crafting recipe even though the armor is disabled via setting
* Fix steel and wood having bad globals for crafting section, turned them to locals
* Fix brazilian translation getting deleted
Fix cactus armor locales being incorrectly named
