This is asking for a complete re-write of how LuaObjects work on the engine side and is not something I have any interest in attempting.


Ok then what about extra data table containing equipment's shield, max_shield, energy, max_energy, etc?
You already provide some data like name and quality ...

#2 is kinda useless without #4
Btw, how does the event provide equipment name and quality if the instance is already gone?


Recording the ID (name and quality) before removing the equipment is simple. In Lua terms its as simple as:

local name = equipment.name
local quality = equipment ...

Unfortunately #3 is just not currently viable due to how many places and ways can send the event (the current count is 15 places across robots, mods, direct player actions, copy-pasting spidertron settings and so on). #4 is not possible because by the time the equipment is removed - it is gone ...

Interesting, what about ItemStack (#3)?

Hello!

Its really hard to do things with equipment as their events are inconsistent in naming, behavior and provided data.
Below is what i noticed so far an how I suggest fixing it.

Naming:
on_equipment_inserted and on_player_placed_equipment have different names ( "inserted" != "placed ...