Vitaliy

> I recently had an issue with digline_send causeing a stackoverflow exception on world load. Is that #467? The workaround you suggest is definitely inappropriate, it would break players’ builds...

Are you sure you didn’t connect them to each other? The LuaC should’ve burnt on such load way earlier, even in such short-circuit.

By the way, I’d not advise you to use such a poorly maintained mod as `wireless` (last commit from 2013, debug print here and there, and some code just waiting...

// Renamed as per: > Globally disabling mesecons to recover from serious errors on startup would probably be the way to go.

> No I connected a transmitter to one port and a receiver to a different port. That is, without any wires connecting them directly. That sound interesting: overheating was designed...

That way, there is no expensive resource at all.

#406

The original reason is that there was no node timers at the time. But currently, the API allows some nodes (Lua controllers primarily) to function continuously, independently of block activation.

looks like exposing a core bug

Yes there is obviously a core bug as it crashes in the engine code, but there is still a mod bug so that it calls the engine code wrongly.