You can now just pass a ratsignal to VA (without it being announced) by
calling `RatAttack.getInfoFromRatsignal`, or choose to also have it
announced in TTS by calling `RatAttack.announceCaseFromRatsignal`.
**Breaks interface compatibility!** `RatAttack.getInfoFromRatsignal`
behaviour has changed.
EDDI sets `Status near surface` near stations, but without
a corresponding event firing … so I had to change the logic there.
Also updating the state variables takes a couple seconds after an event,
so `EDDI Docked`, `EDDI Near surface` and `EDDI Undocked` now have a 5s
delay each. Let’s see if that is enough.
Handling of a ratsignal will be delayed by 5s if a signal is currently
being handled. That way all signals will find their way into VoiceAttack
even if they hit simultaneously / shortly after each other.
To reduce possible confusion though the “open case?” prompt has been
removed from `RatAttack.getInfoFromRatsignal`.
**Breaks interface compatibility!**
Now treats terraformables and ELW/Ammonia Worlds as worthwhile instead
of going by estimated scan value.
Also now tells you the map data value of high-value bodies you mapped.
If an event is about to send key presses, it will focus the Elite client
window now to make sure the first one won’t get swallowed even if you
are tabbed out right now.
For all non-event commands, I’m going to assume you are actively playing
and the client already has focus.
Fixes rare instances of key presses being swallowed, e.g. in the `EDDI
Jumped` command when you tabbed out of the game in hyper space. Should
make things more reliable in general.
Also replaced all occurences of focusing the client window with the
helper function to have a single point of change if the client window
title ever changes.
Basically the only thing that works and is “finished” already is pasting
ingame chat into Seals IRC. use `.sb <msg>` for \#Seal-Bob and `.rr
<msg>` for \#Repair-Requests.
You can now set a jump target. This will start writing the distance to
said target to `>jumpTargetFile` for inclusion e.g. in OBS.
If SpanshAttack currently has a target system, jump target will default
to that. A manually set target will take precedence.
Now actually notices when the script errors out for some reason.
Probably still won’t notice when it’s flat out missing, but hey, that’s
PEBKAC for not using the profile package.
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.
