nodecore-cd2025/mods/nc_api/util_gametime.lua

-- LUALOCALS < ---------------------------------------------------------
local math, minetest, nodecore
    = math, minetest, nodecore
local math_abs
    = math.abs
-- LUALOCALS > ---------------------------------------------------------

nodecore.register_globalstep("gametime", function(dtime)
		local mtt = minetest.get_gametime()
		local nct = nodecore.gametime
		if not nct then
			nodecore.log("info", "nodecore.gametime: init to " .. mtt)
			nct = mtt
		end
		nct = nct + dtime
		if math_abs(nct - mtt) >= 2 then
			nodecore.log("warning", "nodecore.gametime: excess drift; nct="
				.. nct .. ", mtt=" .. mtt)
			nct = mtt
		end
		nodecore.gametime = nct
	end)
Standardize high-resolution gametime. Use high-res version in a few places we were using integer-res timer before. This should e.g. smooth time variation of wind strength for ambient sounds. 2019-11-10 08:10:34 -05:00			`-- LUALOCALS < ---------------------------------------------------------`
			`local math, minetest, nodecore`
			`= math, minetest, nodecore`
			`local math_abs`
			`= math.abs`
			`-- LUALOCALS > ---------------------------------------------------------`

Add profiler instrumentation metadata everywhere N.B. the MT built-in profiler doesn't yet actually support reading labels from bare-function registrations, so a builtin hack is needed. 2020-06-15 07:21:39 -04:00			`nodecore.register_globalstep("gametime", function(dtime)`
Standardize high-resolution gametime. Use high-res version in a few places we were using integer-res timer before. This should e.g. smooth time variation of wind strength for ambient sounds. 2019-11-10 08:10:34 -05:00			`local mtt = minetest.get_gametime()`
			`local nct = nodecore.gametime`
			`if not nct then`
Convert some action logs to info We were using action log level for a lot of things because by default MT does not seem to capture info logs to stderr. On "production" servers though this makes too much noise and makes it hard to find actual player actions. Servers that want info logging will just have to configure/compile it in. 2021-12-11 21:26:18 -05:00			`nodecore.log("info", "nodecore.gametime: init to " .. mtt)`
Standardize high-resolution gametime. Use high-res version in a few places we were using integer-res timer before. This should e.g. smooth time variation of wind strength for ambient sounds. 2019-11-10 08:10:34 -05:00			`nct = mtt`
			`end`
			`nct = nct + dtime`
			`if math_abs(nct - mtt) >= 2 then`
Clean up a few log items, fix levels 2020-06-09 19:05:39 -04:00			`nodecore.log("warning", "nodecore.gametime: excess drift; nct="`
Standardize high-resolution gametime. Use high-res version in a few places we were using integer-res timer before. This should e.g. smooth time variation of wind strength for ambient sounds. 2019-11-10 08:10:34 -05:00			`.. nct .. ", mtt=" .. mtt)`
			`nct = mtt`
			`end`
			`nodecore.gametime = nct`
			`end)`