Instead of using the saved jump range for your current ship, you can now
plot a route with a custom range; e.g. if you have temporarily changed
modules around or have more/less cargo than usual for this trip.
Now resides in `Sounds\scripts` for upcoming profile package compatibility.
Techincally the `Apps` directory would be more appropriate; as soon as
a profile package has that directory though you have to restart
VoiceAttack without plugin support to import the package.
In order not to confuse people that have not been using EDDI in the
past, the profiles will now automatically disable the speech responder.
To use it with the profiles, you will have to explicitly enable it
again.
If you set `>flightAssistOff` in the startup command, VA will now
automatically make sure that FA is off when you lift off a planet or
undock from a station. Defaults to on.
PC cases would have EVERYTHING till the end of the ratsignal as
platform. Didn’t cut correctly at end of platform. So I’m now just using
the ??_SIGNAL at the end instead of debugging the problem because I’m
a lazy fuck.
For one i made a bunch of small mistakes (of course), and I had to do
a dirty workaround for platform detection since IRC color coding messes
with VA really badly.
VoiceAttack will now keep a list of cases and case data. That
streamlines handling of multiple cases / opening an already announced
one after finishing the current one.
Now will only tell you about differences with EDSMM when EDSM knows
_fewer_ bodies (there are some issues with duplicate entries in EDSM,
e.g. in Dromi)
VoicaAttack can handle control characters within a commond definition.
Sadly it errors out if you try to _import_ a profile that has said
control characters in them …
The workaround is to set the delimiter variable (`^B`) in an inline
function. This way the character itself does not appear in the exported
profile and everything works fine.
