Posted by: liveware
« on: March 03, 2021, 09:37:01 PM »Hmm
My experience is that contacts for hostile factions generate interrupts when they change. This is with unmodified databases.
This is because they trigger a "contact updated" event. These fire when something happens that updates the contact - either new information e.g. detecting the thermal or active sensor signature for the first time, or revising of old information e.g. the contact changes speed or raises shields.
The "edge case" which is not caught is that if a contact is lost and then reacquired with no change to its state (same speed, same sensors on/off, same shield levels, etc.) it will not fire a "contact updated" event, and there is no "contact reacquired" event. This really should be in the game because the edge cases are not uncommon, but right now it is not and we must deal with it somehow.
That's an asinine edge case but I suppose such edge cases should not be surprising.