You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Cycamore reactor has the ability to change the input/output recipe/commodity pairs at specified times with the <recipe_change_times>, <recipe_change_commods>, <recipe_change_in>, and <recipe_change_out> tags.
This behavior matches the low fidelity vision for the NEAR archetype, thus implementing it for comparison is necessary to establish the addition to the ecosystem.
This PR can be closed with a PR adding in a single-deployment scenario of the Cycamore reactor with these features activated.
The text was updated successfully, but these errors were encountered:
It would be nice to revisit this idea at some point, but I was not easily able to get the aforementioned tags to work. #6 uses preferences to achieve the desired result.
Update:
I can get the reactor to use one or the other, but never both fuels for some reason. I'm going back over to look for bugs, but I don't think there are any.
The Cycamore reactor has the ability to change the input/output recipe/commodity pairs at specified times with the <recipe_change_times>, <recipe_change_commods>, <recipe_change_in>, and <recipe_change_out> tags.
This behavior matches the low fidelity vision for the NEAR archetype, thus implementing it for comparison is necessary to establish the addition to the ecosystem.
This PR can be closed with a PR adding in a single-deployment scenario of the Cycamore reactor with these features activated.
The text was updated successfully, but these errors were encountered: