Changelog

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.