CubicMelon/terumet

Machine control buttons are not 100% reactive

Closed this issue · 1 comments

More likely on machines with lower timers

Due to the flags potentially being saved and loaded to/from node meta by the machine's actions itself mid-click, the option change might be overwritten immediately after user clicks, causing button to appear to do nothing

This can be fixed but will require refactoring out a bit of the node meta saving related to the option flags

This is as fixed as it's going to get I think. Any remaining lag or failing to react is purely Minetest formspec code now.