Fix Client not displaying cruise engine flame for ships that come into range with cruise engine enabled.

[Caenen]

This affects any situation in multiplayer where a ship (NPC or player) is already spawned out of 'sight' of your client (who is outside of the range within the same system or outside the system outright). The client will not reflect the status of the cruise engine of the ship properly once it comes into range and its information is sent to the client, rendering it as inactive continuously, until the cruise engine is (interrupted and) started up (again).

This might be the exact same issue that affects the shield status of a target as well. Unless something such as damage being dealt to the shield creates an update packet to the client, the ship upon coming into 'view' of the client will show full shields as long as a shield bar exists (i.e. a shield generator is equipped) regardless whether it is fully charged or not. This is very easily noticible/reproducible if the shield has 0 or close-to-0 regeneration rate, by shooting the shield and then re-entering space (via dock or F1), which returns the shield from your client's perspective to full capacity until it takes damage again and it abruptly updates to its proper value.

According to a comment from Aingar, the shield status does get sent to the client in the packet that sends the ship info, however it may fail to get applied to the shield by the client as the equipment of the ship (including shield generators and engines) is not initialized when it tries. If this is true, then I would suspect that the cruise engine state is affected by the same issue.

Reproduction steps:

1. Have 2 clients (player 1, 2) connected to the same server.
2. Have player 1 and player 2 meet in the same area of space.
3. Have player 1 engage cruise engines and keep them engaged (and fly circles to stay near player 2, preferably).
4. Have player 2 use F1 or a nearby docking ring/station to leave space and re-enter it.
5. Player 2 will observe player 1 flying at cruise speeds without the cruise engine visual and sound effects.

[BC46]

@erikroe didn't you implement a solution for this in FLSR's FLHook? Or was that for something else?

[erikroe]

No solution to this as much as I can think of.

[Aingar]

Uh, not sure what I've said back then but the packet quite explicitly does NOT include any current-state of equipment or shield other than current hitpoints of various components.

While I don't handle the engine state at the moment, I do sync the shields.
See usage of shieldStateUpdateMap in this file:
https://github.com/Aingar/FLHook/blob/master/Plugins/Public/munitioncntl/Main.cpp

On FLHook5 it'll be handled through usage of one-time trigger with 0.5sec delay after detecting a CreateShip packet where the ship has less than full HP.

Identical logic could be applied to engines and their throttle/cruise states, as well as cloak devices.