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.
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!**
