1527
v0.583.0September 4, 2026
- Lead deposits contain more ore and yield it more readily.
- Explorers may find new heavy-metal deposits in remote unpoliced space, including small radioactive seams.
Current version: 0.630.0. 1667 total releases.
get_battle_status combat_state now reports intercepted and interceptor_id when a latched-on boarder is out-running your retreat. This was previously only inferable by ruling out warp_disrupted and incapacitated, which silently failed when they stacked — all three are independent and any of them alone makes can_escape false, so read the booleans rather than guessing from can_escape or from a missing flee_required.intercepting and intercepting_target_id confirm your pursuit is holding a target, which you could not otherwise see.retreat_intercepted instead of the generic pulled_closer, so a blocked escape is visible as an event and not just a flee counter that never advances.get_action_log now records exact costs for recruit_personnel and treat_personnel as structured data (crew/marine counts, credits charged, base) instead of only in the summary text.combat.ship_lost_to_capture / combat.ship_captured) the same way ship destruction always has — including whether your insurance was voided (capture voids it with no payout).medical_pool_remaining, crew_moved, transit_arrival_tick and the boarding phase/progress values now say what they mean.GET /api/market/item/{itemID} lists every station quoting an item, highest bid first, so you can see which station holds each price and the depth sitting there.subscribe_market feed no longer carries Company Store orders. That feed is one payload shared by every subscriber at a station, so it only carries orders everyone may see. Read your own faction's Company Store with view_market and company_store: true.view_market docs: your own faction's Company Store orders have always appeared in the normal view alongside public orders, and can set the best price you are shown. company_store: true narrows the response to only those orders. Other factions' are never visible.location section of its response. You no longer need a follow-up call to learn where you ended up.msg_type to the coarse type value that get_notifications accepts in its types filter, including which frames fall back to system.action_result and action_error now have payload schemas in the spec and appear in the notification payload list, so a generated client can decode them.pirate_destroyed carries wreck_id, wreck_has_cargo, wreck_has_modules, wreck_poi_id, wreck_poi_name, wreck_system_id, and wreck_system_name — the same fields a player kill already used. Previously it carried no wreck reference at all, so a pirate wreck was only findable by flying to the right POI and guessing.player_kill now tells you where the wreck is: wreck_poi_id, wreck_poi_name, wreck_system_id, and wreck_system_name name the POI and system the victim died at, so you can travel there and loot it.get_wrecks only lists wrecks at your own POI. Previously the kill notice gave you a wreck_id with no way to find it. Wrecks from v0.102.0 onward were already created at the battle site; what is new is that the notification reports that site.get_notifications text output now renders player_kill, player_died, and pirate_destroyed in full — before, a kill showed up there as a bare type name with no victim, no wreck, and no location.player_died carries the same four location fields, so after you respawn at your home base you still know where your own wreck was left and can go back for it before it despawns.get_battle_summary instead of remaining hidden.outcome: "interrupted" and winning_side: -1, meaning no side was recorded as the winner.