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

[Feature Request] Show the tree of itemgroups for item spawn locations #103

Open
Venera3 opened this issue Sep 3, 2022 · 2 comments
Open

Comments

@Venera3
Copy link

Venera3 commented Sep 3, 2022

Testing itemgroups in the wild pretty much comes down to eyeballing beyond the "spawn 100 groups" debug option, and the nesting of groups especially makes finding out where a certain rare spawn came from. The guide's loot location tables can help point you in the right direction, but it would be extremely helpful if the groups / spawn weights it used to land on a spawn chance were less obfuscated.

@nornagon
Copy link
Owner

nornagon commented Sep 5, 2022

This is a cool idea, and I've also wanted something similar, but unfortunately the way the Guide's spawn stats code works, we intentionally throw away all the item group tree info as we go, in order to sum up the final probabilities. The code would need to be completely rewritten to be able to show that information, I think.

I'll leave this issue open in case I (or someone else) get the taste for rewriting all the spawn stats code someday, but I don't plan to work on this currently.

@nornagon
Copy link
Owner

nornagon commented Jan 9, 2024

Coming back to this to say that I discovered another reason why I want this: reverse engineering why a particular item spawns where it does. Basically, given a "99% chance / 1.8 avg count" item, answer the question: what item groups does that chance/count come from? I could imagine this being exposed as a debugging tool somewhere in the guide.

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

2 participants