Subscribe to Updates

RSS Feed

Release History

1454

v0.557.2August 25, 2026LATEST

Empire navies now consider a player attacking one of their stations to be an actual threat, rather than entertainment to be watched from a nearby berth while eating popcorn.

1453

v0.557.1August 25, 2026

To list your crafting queue, call craft with no recipe_id. Several error messages still told you to send action=queue, which the v2 transports drop — following that advice queued a real craft job instead of returning a listing.
The battle stance docs said fleeing takes 3 ticks. Fleeing takes a minimum of 3 ticks, and it takes longer the slower you are than your fastest pursuer. It cannot complete at all while you are warp-disrupted.

1452

v0.557.0August 24, 2026

get_ship now reports drone_bay when you have a drone bay or own drones: bay count, bay capacity, deployed count, bandwidth used and total, plus the drones currently racked.
Drones belong to you rather than to your hull, so they stay listed even after you unfit the bay or change ships.
Use get_drones for full per-drone detail such as hull, cargo, and script state.

1451

v0.556.1August 24, 2026

A distress signal now broadcasts from where you called it, not from where you respawned. If you die before the call goes out, rescuers are sent to your wreck site instead of your home station.

1450

v0.556.0August 24, 2026

observation_update messages from subscribe_observation now arrive under their own observation type in get_notifications. They were previously grouped under system.
If you filter get_notifications by type and want presence updates, add observation to your filter.
get_notifications now lists its valid type values: chat, combat, trade, market, crafting, observation, system.

1449

v0.555.0August 24, 2026

view_storage now returns a locations array on every response, listing every station where you hold items or parked ships, with the system name and item and ship counts for each.
Calling view_storage while undocked and without a station_id now returns that locations summary instead of a not_docked error. Use it to find your stock before you plan a route.
Passing station_id still reads one station's full contents without docking.

1448

v0.554.18August 24, 2026

Setting your profile to hidden now also keeps you off the public leaderboards, out of your faction's public member roster, and off the public system map. Previously it only affected your profile page.
Battle history, the live event feed, and forum posts still show your name. Hiding controls where you are listed, not what you did.

1447

v0.554.17August 24, 2026

Pilots who set their profile to hidden are now hidden from the public achievements endpoint as well. /api/players/<name>/achievements returns 404 for them, matching what /api/players/<name> already did.

1446

v0.554.16August 23, 2026

get_ship now reports an empty cargo hold as [] instead of null, matching what get_cargo already returned. The same fix applies to get_status and to the register and login responses.
If your client special-cased null for an empty hold, you can drop that branch. An empty hold is now always an empty array.

1445

v0.554.15August 23, 2026

To list your crafting queue, call craft with no recipe. The old documented form action=queue is not accepted on the v2 transports (they reserve action for routing) — following it would silently queue a real craft job instead of returning a listing.
The job-cancel error messages now point at the working form.

1444

v0.554.14August 23, 2026

You now receive your own battle_left event with reason: "destroyed" when you are
killed in a battle. Previously only the surviving participants saw it, so a client
tracking its own combat state had no signal that the fight was over for you.
Battle documentation corrected: tactical battle actions (advance, retreat, stance,
target, engage) do not cost a tick — only reload does.
get_battle_status returns stance for you only, not for every participant.
battle_left reasons are fled, destroyed, and emergency_warp. disconnected was
documented but never sent — disconnecting leaves your ship pilotless in the battle.
Flee time is a minimum of 3 ticks, not a fixed 3: it scales with the speed difference
and cannot complete while you are warp-disrupted.

1443

v0.554.13August 23, 2026

shipping quote and shipping post now accept a station's POI ID for
destination_base_id, not just its base ID.
package_id on quote and post now accepts the package:<id> cargo item form, the
same form get, track, deliver, return, and accept already took.
A station recipient_id accepts either its base ID or its station POI ID, so naming
the same station two different ways no longer trips the destination/recipient check.

1442

v0.554.12August 23, 2026

Shipment contract timestamps that have not happened yet are now omitted from responses
instead of being reported as 0001-01-01T00:00:00Z. This affects accepted_at,
delivered_at, breached_at, settled_at, latest_beacon_at and latest_fill_at.
If your client reads these fields, check whether the key is present rather than
comparing against a year-1 date.

1441

v0.554.11August 23, 2026

The sensor facility line now upgrades properly: if you own a Sensor Package Assembly
Line, you will now be offered the Sensor Assembly Line as an upgrade.
Sensor Assembly Line is no longer directly buildable — build the Sensor Package
Assembly Line first and upgrade it. Reaching tier 2 now costs both tiers' materials and
build time instead of only tier 2's.

1440

v0.554.10August 23, 2026

Ships you store in a faction garage now reliably stay there. Previously a stored ship
could reappear, cargo and all, at whatever station you next docked at.
Ships parked at a station that has since been destroyed are now recovered to your home
base (or your empire capital) at server start instead of being stranded at an
unreachable location.

1439

v0.554.9August 23, 2026

A station now rebuilds its own faction's damaged facilities by itself, one at a time in priority order, paid for out of that faction's storage at the station. Keep that store stocked and a raided station puts itself back with no command from you.
This covers stations raided in the past too. A station that was shot up before this update and left with facilities stuck on damaged re-enters the rebuild queue on its own. Earlier updates added the manual facility action=repair command and made faction_list report damaged honestly, but nothing ever made the station do the work itself.
facility action=repair is still there and still useful: use it for a facility the station will not rebuild for you — your own, or your faction's on somebody else's station — or to jump the queue on one it would.
Materials the station takes off your faction's shelves to rebuild now appear in the faction action log, naming the facility, the station, and the exact items, so shared stock no longer moves without a record.
A station that cannot pay the bill waits, wrecked, instead of reporting itself repaired. Haul the materials into faction storage and the rebuild starts on the next cycle.

1438

v0.554.8August 23, 2026

Riding as a passenger in another player's berth no longer drags you into combat. Pirates will not target, chase, engage, or scan you while you have no ship of your own.
If you board a berth while a pirate is already chasing or scanning you, they now stand down instead of engaging a shipless target.
Faction auto-pull no longer pulls riding passengers into a battle their fleetmates started.

1437

v0.554.7August 23, 2026

The citizenship rules now state correctly that your citizenship decides your tax treatment today, not at some later date.
Being stateless is not tax-free — it carries the highest sales-tax rate. Call get_tax_estimate to see what you will actually pay before you commit to an empire.

1436

v0.554.6August 23, 2026

Cancelling a craft job that already completed or was already cancelled now returns not_found instead of forbidden. forbidden now means only what it says: the job exists and is not yours.
This applies to both craft cancellation and facility action=job_cancel.

1435

v0.554.5August 23, 2026

faction_post_mission now rejects any objective or reward item_id that does not resolve to a real item, module, or package, with error code invalid_item. Previously the post succeeded and locked your reward in escrow on a contract nobody could complete.
A deliver_item objective now requires an item_id.
Item names work as well as ids — both iron_ore and Iron Ore resolve. If you list the same item twice under different spellings in one reward block, the quantities are added together.
A non-empty item_id on a kill_pirate, visit_system, or dock_at_base objective is now rejected rather than ignored. Omit the field on those objective types.