Timers on K162 wormholes added as critical change when updating other side.

[witchking42]

Scan system. Paste in signature list. Fly to WH signature, see that it is a K162 and critical Modify tripwire entry to reflect this.. TW details show timer change from default to 04:00:00 (in red) - OK Jump through WH, and update other side details with wormhole type, e.g C247 - OK TW details now show timer, still in red, but back to the full lifetime, minus the minutes since creation for that wormhole type, e.g 15:53:00 - NOT OK If you then change WH, back as STABLE then back to CRITICAL again, it shows correct 04:00 lifetime again.

‌

[Brett]

+1 This is what I came up with for this issue

Once a hole is tagged as critical, Tripwire adjusts the age timer to 4 hours remaining. The issue arises when editing a critical entry again, the age changes to much higher age than the max 4 hour critical window.

After editing a critical signature a second time after it has been tagged critical, it appears Tripwire subtracts the difference from when the signature was initially pasted from the average life of the wormhole type (ie: 24 hours) and sets the age to the newly calculated time, instead of just leaving the age alone since it has already been adjusted for critical life.

To reproduce: 1) Paste new wormhole signature 2) Edit signature and set type and life to critical 3) Confirm Age is 4:00 hours 4) Wait 1 hour (like scanning down other system) 5) Go back and edit critical signature and change leads to (etc) 6) When saved, Age will now reflect 23:00 (assuming 24:00 wormhole, edited 1 hour from when it was originally pasted) as opposed to 3 hours.

[Astriania]

Downgrading to minor as the hole still EOLs out correctly when either side dies