Skip to content

Conversation

@jurrejelle
Copy link
Contributor

Actually take ember into account when calculating max parallel instead of saying "yeah just take as much as you want"
Specifically taking into account how much ember/t we can use per hatch.

Impl was copied from itemrecipecapability and heavily gutted to work with ember, it works in-game.

Fixes the bug where an LV ember hatch (2000/t I/O) machine would try to calculate parallels for 4 recipes at 750/t, not care, try to run 4 of them, then fail when actually starting consumption


@Override
public boolean isRecipeSearchFilter() {
return true;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should be false btw

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

idts, ember should be considered when doing recipe tree searching no? ember being in the list of primary inputs alongside items and fluids seems fine to me

@Ghostipedia Ghostipedia merged commit eae4f86 into main-1.20.1-forge Jan 20, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants