published on November 16, 2026 in devlog
In this week's devlog Michi talks about the recent Orchestration release and upcoming bugfixes and improvements.

Michi (molp)
This week saw the release of the Orchestration update. Check out the release notes if you haven't seen them already. From a technical perspective, the release has been without any major errors or immediate hotfixes. After a day, I noticed something: a ship was caught in an endless loop, generating tons of "flight aborted" notifications for the user. A quick inspection revealed that the flight was part of a newly created route, and it was aborted due to missing funds for a gateway jump. Right after the jump was aborted, the route execution would try that leg again and run into the same issue. I fixed that with a quick patch that marks the route as blocked for good, which stops the endless loop.
After the release we received a lot of feedback on the shipping route feature. All in all it was positive, but many of you requested additional quality of life features, like additional step types and so on. Of course there are also a few bugs that need fixing. I already started working on a few issues and hope to release a bugfix release later next week.
I want to talk about one specific issue the route execution currently has, because it is non-obvious and has been reported many times. It is possible to set flight preferences for each waypoint. These encompass the STL fuel usage, the FTL reactor usage and gateway preferences. Right now it is possible to set the reactor usage to, say, 50% and a small or starter ship will happily execute that route. A larger ship, however, often requires reactor usage settings above 80%. Once the leg is being planned, the navigation fails because the reactor usage of 50% is way smaller than the required 80%, and the route execution is marked as blocked. Unfortunately, this is not visible in the UI other than the red "blocked" marker. We want to address this in two ways: First, if the required minimum reactor usage is larger than the selected reactor usage, we'll go with the required minimum usage. This will get rid of this entire class of blocked route executions. We also plan on showing the actual reason for blocked waypoints/steps in the RTE command. There are many examples: gateway inoperable, gateway link removed, not enough funds, not enough fuel, etc etc. Hopefully this will help with troubleshooting route executions. Another idea was to have a mechanism similar to blueprint test flights, where one could select a route / ship pair and it would show the blocks (if any) and a rough estimate of the flight times. Not sure if I'll find the time to implement it.
We also did a bit of marketing and wrote to many YouTube channels about the update. Luckily, we received some really nice responses, so we might see another sponsored segment or ad on YouTube for PrUn in the future!
As always, we'd love to hear what you think: join us on Discord or the forums!
Happy trading!