EDDN
EDDN copied to clipboard
Consider allowing `DockingRequested` to the Journal schema.
EDO Update 5 is adding an array of available pads/sizes to both Docked
and DockingRequested
.
We might feel we get enough data about available pads at EDO settlements (specifically, but obviously it'll work for anywhere you could possibly dock) from just the enhanced Docked
events, but perhaps we want to gather it from DockingRequested
as well for those cases where the player was in a too-large ship.
I don't think there's any utility to adding DockingDenied
because:
- If it's due to occupied pads, a legality reason, or ship too large, we'd have picked it up from
DockingRequested
immediately prior. - If the settlement literally has no pads then you won't even be able to request docking, the option won't be on External/Contacts/
.
I imagine that we'd need to enhance the journal events with SystemName, SystemAddress, and StarPos data.
As per current policy these two events would either have a schema each, or share a new dockingpads
schema.