Passing parameters to VoiceAttack through the command line is not thread
safe. For RATSIGNALS coming in in rapid succession (either because,
well, several cases at once or when using an IRC bouncer, like I do) it
completely messes up the data.
see #51
Updated `elite-scripts` to take an optional age as parameter for old
station search, and addded it as a config option to the profile. Still
defaults to 365d = 1y.
There are a bunch of `target <thing>` commands powered by EDDI now. Put
them in their own fresh “navigation” category along with old commands
that fit in there.
EliteDangerous: now automatically detects the bindings profile in use
and loads that.
SpanshAttack: now loads bindings, like, at all. Guess I forgot that.
Also automated, of course.
* added a couple materials/engineering related commands
* added `Entered normal space` event; will throttle you to 0 if
`EliteDangerous.hyperSpaceDethrottle` is set
* added `[what;which] materials do i need?` command
* added `EDDI Material Threshold` event
* changed `EDDI Commander continued` event to `EDDI Commander loading`
which executes on game start rather than every time you log into
a game mode.
Will check if a system exists in the database before trying to plot
a route. If not, will ask for coordinates to find the nearest system
that is.
Now requires `elite-scripts`. **This change breaks compatibilty**.
If enabled, this will ask EDDI about the ship’s laden range and default
to that instead of asking for user input. Setting a ship’s range
manually in `SpanshAttack.getShipRange` will still have higher priority
(e.g. if you are usually using a ship with less than a full cargo hold).
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.
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.
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.
