v1.72 equipmentDamaged

[Svengali]

SYSTEM: WIN

equipmentDamaged is not fired if you set the status from within a script.
So if OXP-A has to disable a equipment from OXP-B and the handling is inside these event-handlers - nothing will happen.

During a conflict it works.

[Eric Walch]

Strongly related to this topic: Wrong parameter transfer with equipmentDamaged and equipmentDestroyed.

From the 1.72 update notes:

New script events: playerBoughtEquipment(equipmentKey), equipmentDamaged(eqipmentKey), equipmentDestroyed(equipmentKey).

playerBoughtEquipment(equipmentKey) does work well, but the other two don't. Using it in code I got errors. On logging the "equipment" I noticed it is not using the key, but just the readable equipment name. And with the name you can't do much else than displaying it. With the key you can get all other essential info over the new "EquipmentInfo"
Looking in the code I noticed it is indeed only transferring the name not the whole key.

[Commander McLane]

That should be easy to fix then.

[another_commander]

Yes, it was really easy

[JensAyton]

equipmentDamaged is not fired if you set the status from within a script.

Fixed, player.ship.setEquipmentStatus(foo, "EQUIPMENT_DAMAGED") now triggers equipmentDamaged() handlers.

[Svengali]

Good news. Muchas gracias Ahruman and another_commander :-)