Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore mod priority configuration option for Orechid outputs #4584

Open
wants to merge 1 commit into
base: 1.20.x
Choose a base branch
from

Conversation

TheRealWormbo
Copy link
Collaborator

If the configured list is non-empty, the first namespace ID on the list that is matched to blocks in the potential output tag is used to determine the output. If more than one such block is found, the output is randomized amon those blocks. If none of the namespace IDs matches any output block, the result is picked randomly as if no priority mods were configured.

If the configured list is non-empty, the first namespace ID on the list that is matched to blocks in the potential output tag is used to determine the output. If more than one such block is found, the output is randomized amon those blocks. If none of the namespace IDs matches any output block, the result is picked randomly as if no priority mods were configured.
@TheRealWormbo
Copy link
Collaborator Author

For reference:
This functionality no longer worked since ed5b860, which appears to have first been released with 1.16.4-415. The configuration option remained in the Forge version ever since, but was not ported to Fabric.

I became aware of it after someone asked about it on Reddit. While the Orechid is technically fully data-driven, someone (including us) might find this useful at some point, for example if we add back default weights for modded ore tags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants