Changelog

Event streaming!

The webhook system is now deprecated in favour of event streams. All players now have access to an SSE endpoint for live streaming events from the game for direct processing. An event catalogue has been added to the online docs with example event payloads for every event that the game generates. Travel departure, arrival, cancellation - mining starting, stopping, retargetting - scans, searches, prospects, deposits, collections, attach, deploy, etc etc. Everything now generates an event to a stream that can be paused and resumed later as needed.

Now some of you have waaay too many devices, so it isn’t practical to stream everything. But thankfully, the AMI controller system has been upgraded to produce per-directive reports on progress, including a full list of current device status and recent events - at a configurable pace. Every directive has a customised report payload surfacing the more interesting stats. If you have a mining controller with 20 drones, you’ll get one status update every 10 seconds (interval multiplier depending) with each drone’s status.

Online docs

• New API Events section in the documentation: Event Logs, Event Streams, AMI Digests, Event Catalogue.
• Added event and message configuration to the Account details and pages.
• Webhooks documentation has been deprecated.

API updates

• New API endpoint for viewing event logs: /events with filters for device, category, type, dates, etc.
• New SSE API endpoint for a realtime event stream: /events/stream with the ability to resume the stream later.
• New star catalogue endpoint: /stars showing all known star systems.
• Fixed bug with deploy command not respecting cooperative replicants.
• New hub wear warning at 50% operational capacity to give players more time to prepare for maintenance.
• Increased request payload limit from 2KB to 64KB.
• Fixed database deadlock issue that was aborting travel routes a hop too soon.

All three regions have been unlocked, but what is this weird ring thing huh? Time to get exotic, replicants! o7

Mid-season feature drop: Simulations!

Our lovely bunch of replicants recently constructed a datacentre megastructure in the MIRFAKA system. It was used to trace the potential origin of those giant asteroids that came for the Ark.

The datacentre is mostly sitting idle, processing the occasional observatory report. So… Bill’s been tinkering with all the fancy analytical hardware. He came up with a design to interface replicants with it directly for the purpose of running simulations.

The simulations run pretty hot, so you’ll need to supply your own compute power. And yes, there are leaderboards for the fastest times!

btw: Event redesign coming next, thanks for the patience.

Online docs

• New section added to cover everything related to the new Simulations feature.

API updates

• New endpoints for managing simulations at a replicant interface with /devices/:code/simulate.
• Leaderboard list now has a type field to support nested items.
• New public leaderboard endpoints for each simulation scenario at /leaderboards/simulations/:scenario.
• New account endpoint for viewing previous simulation runs at /accounts/simulations.

Time to put those bootstrap algorithms to the test! o7

A collection of little bugs and improvements. Thank you so much for all the feedback, you lovely bunch of bobs.

Online docs

• Mention the use of FTL devices to check trades remotely on the Shop directory page.

API updates

• Fix bug to prevent compacting when an autofactory is printing, or an observatory is prospecting.
• Fix trying to stow a device when the target host is elsewhere.
• Add feature to view the current trade details at a shop when you have an FTL device in the shop’s system.
• Fix mining drone bug where it wouldn’t switch to the next available site when a resource depletes.
• Improved the response shape on /locations/:code to better match the /replicants/:code/scan results.
• Added the spectral_type field to location output; stellar_class is deprecated, to be removed on the next breaking version.
• Fix bug with activating propulsors while they are still attached to another device.
• Add prospecting information to device status responses for galactic observatories.
• Add device tags to the autofactory print status output.

The galaxy is getting bigger. Reach for the stars! o7

Achievements are here. Over 200 achievements are now available across six categories. Half of them represent the variety of location events at planets in systems, but the rest are centred around your progression, exploration, travel, infrastructure and community involvement.

Discovered a new star? Badge. Visited fifty systems? Badge. Diverted an asteroid? You better believe that’s a badge.

Online docs

• Updated the Achievements page with new public endpoints.
• Updated the Scan Devices page to show new paging params.

API updates

• New public /achievements and /achievements/:key endpoints to browse all achievements and player unlock counts.
• Added 120+ metrics-based achievements covering systems scanned, devices deployed, distance travelled, stars discovered, beacons placed, events completed, and more.
• System device list is now paginated with cursor-based paging and filtering by owner replicant.
• Prospect completion events now include the full list of discovered stars.
• Performance improvement on the unread message counts that were causing 503s during a burst of traffic.
• Added new prospect_no_fringe event to store details of prospect failures.

NEEEEEEW ACHIEVEMENT! o7

Season two is underway. The megastructure at MIRFAKA was completed in record time, and the results from the DSTA (Deep Space Tracking Array) computations should be with us today. Where did those asteroids come from?

Today’s patch is a collection of small quality-of-life fixes and upgrades.

API updates

• Improved the surge-hop routing algorithm to use the Kuiper as an intermediary waypoint when cruising to distant objects.
• Replicants housed in a system hub’s cradle will auto-eject before destruction.
• When an asteroid falls out of range, any devices still there will float to the Oort cloud.
• Added the decommission command to all devices now, not just those with a cruise drive.
• Fixed bug with asteroids spawning instantly after diversion. Now based on the original impact eta.
• Device tags now support colon (:) and period (.) characters.
• Added in_control_range to the device list, based on FTL connectivity.
• Added completes_at field to scan and search responses.
• Added quantity_mined field to mining drone status and related events.

Asteroid hunters, we salute you! o7

Season two begins. It’s been 18 years since the Exodus Ark departed from Urcalis. Life is calm once more. Riker pushes forward with lifting humans off-planet. Bill has concerns - he’s working on something. Riker would like a hand, too.

The season launches with the second instalment of our galactic story. In the interim years, replicants prospected outwards. Our star catalogue is now 88ly (up from 70ly) from Sol to the fringe.

Space-faring species will start requesting more advanced devices, with a new fourth tier of events.

Online docs

• Story section added to the homepage.
• New Story Page added to the site with the full timeline of the events so far.
• Updates to the Story API page, with practical impacts on players.

API updates

• Resource belts rebalanced - quantities, site scaling and search times.
• Hull plate blueprint added to the starter pack.
• New component-based blueprint designs.
• Replicant device list is now paged.
• More species.
• More events.
• More stars.
• Oh, and three new [REDACTED] waiting to be [REDACTED].

Hip hip, array! o7

Just a few minor bug fixes in today’s patch. A very amusing bug allowed players to keep deploying already-deployed FTL relays, causing rips in space and time.

Online docs

• Updated Auofactories page to mention that only travel/start_mining commands are currently supported for the oncomplete shape.

API updates

• Performance improvements on the new devices endpoint.
• Fixed a bug with legacy FTL relay deployment mechanics.
• New background task to fix any unfinished autofactory print jobs.

The season is drawing to a close. All is calm. Nothing bad is coming. o7

The galactic observatory prospecting logic has been improved to be more useful in dense regions of space. You can now point the observatory in different directions if you want to explore along a non-outwards route. Perhaps you’re in a particularly sparse location and you’re pretty sure you saw a flicker of light in a dark zone.

This update also comes with the long-awaited blueprint descriptions, which took forever to write. Let me know if you find typos or things that don’t make sense.

Online docs

• New Galactic Observatories page with operating instructions.
• Added description fields to the example on the Blueprints page.

API updates

• Improved prospecting to have a direction, and to focus on populating that hemisphere with new stars.
• Allow fleet controllers to accept their current location as a travel destination, to route their devices to them.
• Updated some NPC bobnet messages.
• Added blueprint descriptions.

Enjoy the newly added flavour of composite-conductive rare-earth shielded emitter exhaust relays with braided dissipation waffles! o7

Today’s new feature is the ability to move these large devices between systems with a new pair of commands.

Large devices, like the autofactory, are actually more like a collection of fabrication and storage components in the same area, with drones sending parts back and forth. To shift them between systems, they need to be reduced to a suitable shape first. Some devices will take longer than others to compact, depending on the layout and the pre- and post-flight checks required to secure sensitive equipment

Online docs

• Updated Moving Devices to explain compact/unfurl workflow for large modular devices.
• Updated Device Retrieval with modular feature details and new status values for compacting/unfurling.
• Updated Commands with new modular feature and compact/unfurl command reference entries.
• Updated Devices overview to mention the modular transport path for the largest devices.
• Updated System Hubs with new relocation section covering compact/unfurl.
• Updated Autofactories with new relocation section covering compact/unfurl and tags parameter for print jobs.
• Updated Blueprints starter set to include modular feature on autofactories.
• Updated Civilisations to show how to list active/completed events.

API updates

• Implemented new compact/unfurl commands for large modular devices to prep them for interstellar travel.
• Fixed a series of bugs with stow/deploy logic to better support multiple-replicant scenarios.
• Fixed a bug where webhook message events sent with type:event instead of type:message.
• Attempting to stow a device that is repairing, or being repaired, will now stop the repair first.
• Added ability to auto-tag devices from the print queue on autofactories.

The very latest in flat-pack space station design. What a time to be alive! o7

Headlines for today’s update: better fleet controllers and a new endpoint for batched inventory data.

There was a bug where location events were showing in location info, even though they hadn’t been discovered (planet scan, beacon at location, nearby system hub), which was causing some annoyance to players arriving without a survey drone.

Online docs

• Rewritten the Fleet Controller page to provide details on fleet groups and travel routes.
• Rewritten the Location Inventory to use the new batch inventory endpoint.

API updates

• Simplified how AMI fleet controllers work.
• Added deployed_from and stowed_in to the deploy/stow responses.
• Fixed bug where some AMI directives were not deactivated on completion.
• New endpoint for browsing all your visible location inventories.
• Fixed bug with not processing the print queue on travel arrival.
• Fixed bug with undiscovered events appearing in location details.
• Blueprint info now includes queue_size in the response.

The Ark is saved! All incoming rocks have been diverted with a huge-scale collaborative operation. Great work replicants! o7

This has been requested several times, so the main addition in this release is proper filterable, batched device info lists.

Although devices can already be listed by tag, there has been demand for full device status lists as well. This release adds support for paging through the full device list, with optional filtering by replicant code, device type, and location, including star-level location support.

This is also a minor release, instead of a patch, due to the potential breaking change introduced by standardising the travel response shapes across different endpoints. Sorry if this breaks any user interfaces, but it was needed!

Online docs

• New page showing the Device List endpoint, for large scale batched device info.

API updates

• New GET /devices endpoint for batched device info.
• Decommissioning a device that is attached, or has attachments will now separate itself first.
• Fixed a bug with old diverted asteroids still showing in system scans.
• Performance improvements on the /accounts/events endpoint.
• Fixed the bug that was showing the first leg of travel instead of the full remaining route in the device info.
• Ensured consistent travel response shapes across replicant and device info and command responses.
• New final_arrives_at field in the travel schema, so you can track arrival for current leg and the whole journey.
• Updated device list by tags endpoint to force supplied tag name to lowercase.
• Error messages related to collecting resources when they don’t exist have been improved.
• Resource inventories now show properly as integers and not those scary floats.
• Added tags to device list responses.
• Added device creation dates to all device info/list responses, so players can track their timelines.

OpenAPI/Swagger updates

• Added all of the missing device command schemas.
• Added lots of missing params to endpoints that were previously undocumented.

The Ark is under attack! Will the replicants save it in time? o7

The megastructure is complete, the season is ending, it’s been awesome. This is a little bit of a breaking change, hence the 1.1.0 version , but it’s been requested by quite a few of you. I’m hoping this is useful.

Online docs

• Updates to Accounts and Replicants page to explain new two-tier scoping of devices.
• Updates to Account settings with examples of replicant ownership.

API updates

• A new two-tier permission model has been introduced for account/replicant-scoped device control.

Have fun with the rocks! o7

Some players might have thought they saw humans out there in the galaxy, but they must be mistaken, since the only humans are currently on Earth. Coincidentally, there is a new species in the game called the Solari. Two unrelated facts. Ahem.

Bill has also been working on subspace improvements to FTL comms. The relays are now open for all replicants to intercept bobnet chatter. Also, as long as there are relays at both ends of a travel route, you’ll receive in-flight messages too.

Online docs

• More details added to the BobNet page showing new channel list example and updates to receiving messages.

API updates

• Performance improvements on batch device listings.
• Bug fix with location events and megastructures consuming devices that had already been used for something.
• New “detonate” command now available for Impulse Chargee devices. Will become available as soon as the Ark is ready.
• A new species has been discovered, the Solari, which looked very similar to humans at first glance.
• Improved error handling on different scenarios for attempting replication.
• New endpoint for listing the available BobNet channels with activity dates to help with client interfaces.
• Replicants can now receive BobNet messages in any system that has a relay, regardless of relay ownership.
• Travelling replicants will now intercept in-flight BobNet messages as long as they are travelling along active FTL network routes.
• FTL relays can now be deployed anywhere, but only activated at L4/L5 Lagrange points.
• Surge plates in taxi-mode are now shared by replicants under the same account, for assemble and ferry directives.

This update was a real blast to work on. Heh. o7

Today’s patch has two primary focuses: surfacing AMI directive evaluations in the logs, and batched device status responses.

Online docs

• Added new Tagging page to explain how device tagging works.
• Added new Logging page to show examples of how to use the new device logs endpoint.
• Updated AMI Overview page to show the more recent activate/deactivate commands for controlling directive evaluation.
• Added more details on the difference between maintenance drones and service bots on the Maintenance page.

API updates

• New device log endpoint at /devices/:code/logs for convenience.
• AMI directive logging vastly improved, with logs now explaining all decisions made.
• Implemented device tags as a core concept. You can now set any number of tags on devices to help stay organised.
• New PATCH /devices/:code endpoint to set tags in a per-device configuration. Will be used for future device configuration.
• Taxi-mode moved from a distinct ‘configure’ command to simply a ‘taxi’ tag on surge plates.
• New GET /devices/tag/:tag endpoint to receive batched device info, with cursor/limit params for paging.
• Fixed a few misc swagger-related inaccuracies.
• Introduced device command and ami directive request schemas for deeper validation.
• Simplified attachment logic. Eliminated attachment loops. Only allows three layers deep.
• Diversion of asteroids now uses the “diversion” feature on a device, no longer specific to just propulsors.
• Always show activate/deactivate commands as available on AMI devices.

Megastructure progress at 27%. There’s a chance we might just pull this off! o7

Three big things from today’s patch:

• Asteroid diversion is much improved, with persistent progress from all participating accounts.
• Location events were seriously bugged when there were multiple paths to resolve - big overhaul.
• The Service bot bugs had rendered it pretty useless. The ‘service’ directive now allows it to hot-repair devices properly.

Online docs

• Updated the Asteroids page with a new example response and improved explanations.
• Clarified on the BobNet that relays will receive messages anywhere on th subspace backchannels.

API updates

• Fixed an issue with emails not being deleted on the the account wipe process.
• Added Access-Control-Max-Age header to preflight responses for CORS efficiency.
• Location events fixed to support multiple resolution options.
• Location events now include the resolution options, formatted nicely, in the event description.
• Minor breaking change to flag: location event criteria has changed from a dict to a list of resolution options.
• Overhauled asteroid diversion to track progress properly, with a new impact_likelihood value.
• Per-planet resource inventories added to /locations/:star response.
• Per-moon resource inventories added to /locations/:planet response.
• Shop details added to the system scan response.
• You can no longer attach a matrix directly to a carrier, they need to be protected by something.
• Fixed premature system hub achievement.
• AMI device status now shows as paused when the directive is paused.
• Fix bug with location still showing after being stowed.
• Fixed issues with service bot and maintenance drone interactions.
• Fixed bug with attaching to devices that are also carriers.

The galaxy has now been 20% explored. That’s not nearly enough! o7

Big collection of bug fixes, minor improvements and consistency updates under the hood today.

Online docs

• Fixed incorrect paging fields in BobNet catchup message response example.
• Added OpenGraph image to the website, for previews when sharing on socials.
• Standardised examples in the Device commands list to use “targets” instead of “device/devices”.
• Updated AMI Overview page to mention the assemble directive using taxi plates.
• Updated Shop configuration page to mention optional description/announcement fields.
• Fixed typo on Account reputation endpoint - it should be /accounts/reputation.

API updates

• Decomissioned devices will now return a 404 if you attempt to query or command them.
• System scan results will now return replicants in a list, instead of a map, to match the swagger docs.
• Mining cycle times now return as an integer, instead of a float, to match the docs.
• BobNet trade announcements will now be more spread out, and less frequent.
• The assemble directive has been upgraded to now use taxi plates where available.
• Fix bug with BobNet messages coming from the relay-owner when using replicant message endpoint.
• Added more details to the BobNet message responses, to assist with chat interface design.
• Description and announcement fields are now optional fields in AMI Trade Controller configuration.
• Dry-run travel route previews are now possible while your vessel is mining or printing.
• Cleaned up the use of target/targets/device/devices on several endpoints, all should be accepted but examples use “targets” now.
• Removed an old device-based rate limit that was confusing some tests.
• The cargo lifter device can now actually be used as a carrier.
• Using the wrong HTTP method on an endpoint will now list all the available methods for that route.
• Tightened up the location wipe on stowing devices.
• New achievements for asteroid diversion - whether you’re saving lives or rocks.

Big thanks for all the bug reports and feature suggestions from everyone so far! o7

Today’s change is a cleanup patch. It has been undergoing regression tests for a few days, but I wanted to get it out. Please report any bugs or inaccuracies.

Notification settings can now be configured separately for webhooks and email. This puts the configuration in players’ hands: for example, you can choose to receive emails for newly found location events and trade transactions, while receiving everything else via webhook. Master toggle to disable email and/or webhook.

Upon release, this patch will automatically disable email notifications for all players. This is deliberate, to avoid spamming you. Please re-enable the email notifications you care about most. Emails are now a little prettier (the text/plain versions should also look cleaner in CLI mail clients)

Online docs

• Updated Account settings page with email-change example, new preferences shape, and the new “hub” category.

API updates

• New “email” field added to PATCH /accounts/me for players to change the email address on their account. Triggers a verification process.
• Players will no longer receive gameplay emails if their email notification setting is off. Emails for verification processes (registration, email change, account wipe) will still be sent.
• Notification system overhauled to properly respect the per-category email/webhook account settings.
• Fix added for players who occassionally find a device (or themselves!) out of command range. The underlying fix is still in progress, but your devices should self-correct when breaking.

There are now 60 replicants roaming around the galaxy! o7

As a variety of custom BobNet chat clients are being created, it was time to ensure our replicants have a personality. And a plan!

Online docs

• Added new Multiplayer concept page to explain the interactions possible.
• Renamed the “Replicant details” page to Your details.
• Added new Directory page to explain how to lookup other replicants.
• Renamed the old replicant “Rename” page to Configure and added instructions on how to configure your public profile fields.
• Updated the replicant Print device page to include instructions for clearing the queue or cancelling a print.

API updates

• Carried out a review of swagger docs and fixed a range of inaccurate fields and examples. More still to do.
• Added new replicant directory endpoint at GET /replicants.
• Added new public profile fields for replicants to save with PATCH /replicants/:code.
• Wrote descriptions for the NPC profiles.

Megastructure progress is happening! Go replicants! o7

Biggest change is a round of fixes and refactors to the AMI mining controller. The overheating issue has been diagnosed now, and will appear in your event logs. Using one controller across multiple sites with lots of drones will overload the AMI’s compute core, resulting in delayed directive evaluation and increased damage.

This is a good time to point out the difference between maintenance drones and service bots.

Online docs

• Updated pagination params on BobNet, Beacons, Messages, and Event log pages.
• Added location filter parameter to Replicant devices page.
• Added entry_point to Nearest stars response examples.
• Details on multi-location mining directive behaviour added to the Mining controller page.
• Explain difference between maintenance drone and survey bot on the Maintenance page page.

API updates

• Fix bug with mining controllers running multiple locations.
• AMI mining controllers will now overheat due to heavy multitasking.
• Riker’s system hub exploded. He’s now maintaining it daily.
• System Hubs now degrade from the Lagrange point to the planet’s orbit.
• Fix bug in system scan award not being issued.
• New achievement for first BobNet message (starting from now!)
• Riker will greet new BobNet replicants on #general.
• Replicants will auto-subscribe to a channel when posting a BobNet message there.
• Paging options standardised across all message/event/log endpoints to use cursor/limit/latest.
• Star results now shows the entry_point, where known.
• The location overview on GET /locations now includes the location_event count.
• Access-Control-Expose-Headers configured for web-based clients to view our headers.
• Trying to command a survey drone to scan when already scanning results in HTTP 409.
• Active location events are now included in the scan reports.
• Replicant device lists can now be filtered by location.

Thanks for your patience with those janky AMI controllers folks. Focus now shifting to the other ones. o7

Today’s patch is focused on a range of player reports regarding device travel, replicant host control and AMI coordination.

API updates

• Cleaned up activating/deactivating propulsor error handling.
• Fix bug with the recall command trying to stow unstowable devices and leaving them broken.
• Fix cross-system cruise recall trick where AMI devices would break the laws of physics.
• Fix in-system AMI recall behaviour where devices would use the wrong drive
• AMI controller directives now have the devices use their own travel route computation, rather than issuing direct travel commands.
• Location scans have been adjusted to show your own account knowledge, including knowledge of life.
• A variety of interesting issues related to replicant matrix cradling and travel have been fixed.
• Strapping a surge plate on the back of a matrix container and sending yourself off into the void will now grant a special achievement (thanks Tory!).

Two fun features added to today’s patch: travel route previews and custom system hub greetings!

Online docs

• Updated Replicant Travel and Device Commands pages to show the new travel preview feature.
• Added custom welcome message details to the System Hubs page.
• Updated the Webhooks page to show an example of the new GET endpoint.
• Added example of checking the star catalogue for a single star on the Nearest Stars page.
• Added capacities to the example response on the Blueprints page.

API updates

• New dry run parameter added to the travel commands, to view the planned travel route
• Fixed rare bug on travel arrival where the device loses its location.
• Removed autofactory message when cancelling a replicant print job.
• Added the “assemble” command to AMI devices. All devices should now list all commands they accept.
• Replicant now accepts the “clear_queue” command on the /replicants/{code}/print endpoint, instead of needing to clear on the vessel device directly.
• Improved error message when attempting to travel a stowed device.
• All AMI devices now include the “available_directives” in their details response.
• New endpoint to see star catalogue data for unscanned star designations.
• Improved error message on attempting to stow a matrix somewhere it shouldn’t go.
• Added stow/cargo/attach capacities to blueprint response.
• Fixed missing hosted_device_code while travelling.
• Stowing a survey drone will now stop it tracking the resource site properly.

The big change from today’s update is an overhaul of the system scan logic. Up to this point, system bodies were showing as scanned if anyone had scanned them. This was leading to inconsistent AMI survey behaviour when encountering previously scanned systems (by other players). This was also confusing some location request lookups.

Online docs

• Updated the values on the Rate Limits page.
• Updated the Replicate page example to use the matrix code instead of the cradle.
• Fixed broken link and added more details to the Replicant Cloning page.
• Fixed typo on Fleet Controller page.
• Added details on accessing BobNet chat logs to the BobNet page.
• New page talking about our current NPC replicants.

API updates

• Rate limits have been relaxed, allowing double the requests.
• System scan logic has been overhauled, location info is available remotely if you had previously scanned a system.
• Old asteroid impacts are removed from the system summary after a day.
• Replicant lookups from other accounts no longer show detailed replicant details, just the name and code.
• The “replicate” command has been moved from the cradle to the matrix.
• Bill has reconfigured his FTL beacons to be auditable by players.
• FTL beacons now report the “audit” feature, powering the audit endpoint.
• FTL beacons and System Hubs now report the “comms” feature. This is what powers location event notifications.
• New endpoint for catching up on BobNet messages from a relay.
• Star lookups are now possible for travelling replicants, based on their origin location.
• Star listings now include the current star.

Online docs

• Updated System Hub docs to include activation instructions
• Improved the AMI Overview explanations to include more details on the launch process
• Added the missing belt_search directive to Survey Controller details
• Rewrote the old Surge Plate page to be a new Moving devices page
• Added example of the new FTL network lookup on FTL Relays

API updates

• Fix a system entry point definition issue with sending survey drones into unscanned systems
• Fix bug with FTL relays and system hubs not allowing remote device info; they were supposed to work like beacons
• Overhauled the haulage situation with the ferry directive. Surge-capable transport devices will no longer wait for surge plates
• The message command now shows as available for relay-capable devices
• Blueprints now show an accurate print time for devices
• The attach command is now stricter when you attempt to use it on larger devices
• Device lists now include an additional in_control_range field to show if you can control it remotely
• Surge plates now have the distinct taxi feature, which surfaces the configure command. There is a future where we’ll be able to configure a variety of different device settings, with taxi-mode just being the first for now
• New network endpoint available for relay devices, to inspect the current FTL network status with a list of connected systems
• The activate and deactivate commands are now fully implemented, allowing relay deactivation, and fixing its appearance on the maintenance drone command list

Thanks again to the current playerbase for being so interactive, each patch is improving the game experience for us all! o7

One big change in today’s patch release: the new Civilisations page provides more details on interacting with species as we explore the galaxy.

https://replicant.space/docs/concepts/civilisations/

Online docs

• Added device travel example to the drives page
• Added missing 9-slot surge carrier device to the surge plates page
• Rewritten surge plate page to explain Taxi Mode better
• Added new page on species and location events for discovering new blueprints
• Updated account registration page to include name restriction

API updates

• Added missing hosted_device_code to mining replicant’s info response
• Refactored FTL network logic significantly to better support cross-system AMI control
• Added stricter validation on account/replicant names
• System scan output updates with real moon counts when planets are scanned, instead of the early estimates

Online docs

• Fixed a mistake in the Account Settings example
• Tweaked mobile responsive layout to show docs in the nav
• Added more details and example code to the Webhooks page
• Added a full table of all commands and params to the Device Commands page

API updates

• Fixed the “via” param not working properly on manual travel routes
• Fixed a bug where a server reload would quadruplicate any ongoing print jobs

Online docs

• Corrected the set_directive usage across all AMI examples
• Rewrote asteroid impact doc to explain propulsor usage and diversion better
• Added feedback page to explain the new endpoint usage

API updates

• Updated NPC chatter on BobNet to reflect current blueprint collection
• Included the search command in survey drone details, and show as searching in device status
• Added new feedback endpoint for bug/typo/idea requests from players

Online docs

• Fixed incorrect replicant print example (thanks Ombre)
• Added content-type headers to all POST examples (thanks Ombre)
• Rewrote the messages page to include details on unread message counts, and examples of marking messages as read (thanks FrikiGeekFran)
• Added a new page to show the account details endpoint (thanks Seveen)
• Added more details on how asteroid belt mining works to the mining drone page (thanks Seveen)

API updates

• Added support for gzipped request payloads (thanks FrikiGeekFran)
• Fixed a bug with the way that a certain NPC travels across the galaxy each day.
• Ensured all scan responses now use location_type as standard. The old type response field is deprecated. (thanks Seveen)
• Standardised the response shape for salvage/belt mining. Old belt and designation response fields deprecated. (can’t find who reported this sorry!)
• Added better response for trailing slash on endpoints rather than the 404 (thanks Ombre)

Wipe clean

New self-service endpoint at DELETE /accounts/me for nuking everything tied to your account - your replicants, devices, inventory, achievements, messages, etc. To keep things secure, when you trigger the endpoint, it will email you a confirmation with a button to click.

Clearer rate limits

New rate limits page added to spell out the per-endpoint and global buckets, and with an example of what happens when you hit it, so you can configure your client to back off cleanly.

Launch!

Welcoming new replicants to help the exodus project. Season one ends summer 2026.