Jeija commented 21 days ago at
githubThis bug imo requires to make a decision concerning the whole overheat protection idea. As it seems to me, overheat protection is not really required anymore when using the ActionQueue. However, mesecons still maintains some compatibility for not using the ActionQueue and instead executing all actions right away (not wait until the next serverstep). That support however is hardly tested as it is disabled by default and rarely used.
Another problem might be, that having some kind of overheat support on servers at least will prevent the load to get too much, so idk if dropping it completely is good. Any experiences from the server owners on it (as gates don't overheat now - has that become a problem yet?).
Solutions might be:
1. Drop the non-ActionQueue system and overheat protection completely
2. Drop the non-ActionQueue system, but rework and maintain overheat support
3. Maintain a status quo that also supports direct execution (no ActionQueue), but fix the issue in another way
Fixes for this bug in 1 and 2 might be moving the cooldown to the ActionQueue and also rework the system so that gates, microcontrollers and luacontrollers all use the same functions.
I would go for 2; However, if noone had issues with higher load on servers due to no overheat protection I'd choose 1.
What option would you prefer?
looks like currently the discussion about mesecons happens somewhere there
https://github.com/Jeija/minetest-mod-mesecons/issues