Implement Factory Planner TURD support interface - #610
Merged
Conversation
protocol-1903
approved these changes
Aug 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds the remote interfaces FP would need to support TURD hidden beacon effects, recipe substitutions and machine substitutions. I tried to write the comments from the perspective of you guys, which felt weird but makes sense I think.
The very basic architecture for these is that Py offers a passive interface (
"fp-integration-pyalienlife") that allows FP to pull the data it needs on its own. Py also uses FP's"invalidate"interface to let it know that a set of data has changed and needs re-pulled.The FP side of this is still on a branch, I only want to merge it when this is merged so I can note the required versions of things in the changelog. Also, I'm happy to keep this integration updated myself if that's a concern. We already have another integration in FP, and there'll probably/hopefully be more.