Open kcaa opened 9 years ago
Not reproducible? This was once an issue on Linux with Dartium but no problem on Windows with compiled (dart2js-ed) client.
Still reproducible on Linux. Confirmed with Ashigara Kai-2.
Mystery explained:
Thus, if the client request ShipList before /api_get_member/slot_item happens (1 seconds delay after /api_get_member/ship3), this issue occurs. If there is enough update interval, this may not happen thanks to REFERENCED_OBJECTS priority list.
This can be fixed by re-updating the Ship's equipment list (on the client) when received EquipmentList.
That said, the priority is still low. Worth considering the trade-off of supporting this case v.s. the code complexity and CPU resource consumption.
This should be possible as the client does it. That said the priority is not that high as it will be refreshed when getting back to the port.