Variables {DEC:System X} {DEC:System Y} {DEC:System Z} for VA are not being populated on first entry into undiscovered system

[MalicT]

EDDI version in which issue is found

3.5.2

VoiceAttack version in which issue is found (as applicable)

1.8.3

Steps to reproduce

Create VA command that outputs {DEC:System X} {DEC:System Y} {DEC:System Z} to log
Enter system that has never been visited, by yourself or is on databases.

Expected

{DEC:System X} {DEC:System Y} {DEC:System Z} would return coordinates in system

Observed

{DEC:System X} {DEC:System Y} {DEC:System Z} returns as NOT SET NOT SET NOT SET

Investigation

{DEC:System X} {DEC:System Y} {DEC:System Z} is not populating on first entry into system, however
{DEC:Jumped X} {DEC:Jumped Y} {DEC:Jumped Z} are

https://github.com/EDCD/EDDI/wiki/Jumped-event lists system X, Y and Z to be populated on the jumped event, and everything else is, except those three. Am using premade scripts that had all the jumped variables listed to output everything in the jumped event.

The {DEC:System X} {DEC:System Y} {DEC:System Z} populate only after the first entry into the system, or if the system is in the databases (EDDB/EDSM)

[Tkael]

Writing variables to VoiceAttack can be CPU expensive so we only want to re-write data that has changed. It looks like this comes down to the way that we've been evaluating data for equality prior to posting a variable update to VoiceAttack. PR submitted.