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

Researcher gives the same pattern basically every time #500

Open
NathanDSimon opened this issue Aug 11, 2024 · 0 comments
Open

Researcher gives the same pattern basically every time #500

NathanDSimon opened this issue Aug 11, 2024 · 0 comments

Comments

@NathanDSimon
Copy link

NathanDSimon commented Aug 11, 2024

Issue description: Not sure if this is a bug or just a design flaw but either way it's extremely irritating.
When I put lost knowledge of any rarity into the researcher, the distribution of outputs is so far from uniform that it is frankly pretty ridiculous.
out of a quarter stack (16) of the same rarity (I tested all 4 so 64 total), a whopping 40 were the exact same tag (in this case, forge:mineable/digging_claws but I think it's just forge:mineable that has the obscene weight as when I used a pack that had mineable/aiot it essentially was 50/50 those two and virtually nothing else).
If this is a bug, please fix it. If it is intentional, still fix it, because I don't want to have to blow through an entire 64 stack of lost knowledge just for a CHANCE at getting that feature pattern, and I assume most people would feel the same way.
In all honesty, RNG-gated progression needs to not be a thing in general, but I'm not going to ask for a complete rework of the system in this sort of a PR.

Steps to reproduce:
Put lost knowledge into a researcher, then notice how wildly skewed the drop rates are

Versions:

  • Minecraft: 1.20
  • Forge: 47.3
  • CompatLayer (only if on Minecraft 1.10 or 1.11):
  • McJtyLib: latest
  • RFTools: latest 1.20 ver
  • RFTools Dimensions: latest 1.20 ver

Possibly incompatible mods:
N/A

Relevant logs, if any:
N/A

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

No branches or pull requests

1 participant