True a direct replacement of depreciated functions will break older Minetest servers or the "server" that runs a singleplayer game. But it won't break the "client." Couldn't mods check for versions < 0.4.16 and then make available the old or new setting_* or settings:* according to what was detected? It's true we can't detect that on a client, but a server shouldn't have any trouble detecting itself. Heck. Just include both style settings and require a entry in minetest.conf with the old setting_* as default to avoid breakage.Wuzzy wrote:Okay, fixed in development version.
This will break compability with Minetest 0.4.12, 0.4.13, 0.4.14 and 0.4.15. >_>
What a pointless Lua API change.
new_settings_object = false
A proper pull request to minetest for a "universally named" setting in the conf might benefit all the mod makers.
I just hate to see perfectly good mods having to leave slightly older servers behind, or be forced to use the old settings and bury the new servers in gigs of warning messages. Our server literally would have a log a gig+ a day.