add priority_queue module

[A-lex-Ra]

Usage example:

-- world.lua
local tt = require("core:tick_timer")
local should_run_timer_tick = false

function on_world_open()
    if not tt.b_acquired_by_some_script then
        tt.b_acquired_by_some_script = true
        should_run_timer_tick = true
    end
    tt.interval(5, "inf", function() print("5t-callback called!!!") end)
end

function on_world_quit()
    tt.destroy_all()
    tt.b_acquired_by_some_script = false
end

function on_world_tick()
    if should_run_timer_tick then
        tt.tick()
    end
end

It turned out that on_world_tick hardly works in modules (It only works if the module is exported to world.lua that does not yet have on_world_tick.), so users (for now) will have to call Timer.tick() manually as in the example, and also ensure that Timer.tick() is called exactly once per tick (using the global flag Timer.b_acquired_by_some_script).

[Volcraft311]

Ворованный скрипт, переработанный с помощью нейросети.

[A-lex-Ra]

It's not stealing if there's almost nothing left of the original.

[MihailRis]

?

[A-lex-Ra]

i can't decide what to do when callback throws error

[MihailRis]

In any case, the complete misunderstanding of the engine events system, metamethods without metatables (is it even tested?), random indentation in different functions (like lazy copy-pasted), useless AI-generated comments completely undermines the credibility of the code work without Lua autotests (dev/tests)

[A-lex-Ra]

In any case, the complete misunderstanding of the engine events system, metamethods without metatables (is it even tested?), random indentation in different functions (like lazy copy-pasted), useless AI-generated comments completely undermines the credibility of the code work without Lua autotests (dev/tests)

it's mine dumb comments ;( sorry for that. But that's what code review is for, right?
Everything will be fixed.
Metamethods without metatables don't affect anything.

[MihailRis]

It's better to leave only PriorityQueue for now, and I'll create a PR for the correctly integrated scheduler today

[A-lex-Ra]

Ok. I recommend using update_front_priority to efficiently change the priority of the smallest element in the queue. And it might be worth creating a separate list for timers that are called every tick, as the queue isn't very efficient in this case.

[A-lex-Ra]

And also item must have an "id" field.