-
Notifications
You must be signed in to change notification settings - Fork 234
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
Junk Ice Trap Onslaught Issue #2197
Comments
I believe this is intended behavior, but not 100% certain. |
O alright. I thought it seemed odd that every freestanding/pot/crate item ended up being a gold rupee. Might be something to consider changing. |
This is because the only junk items not removed from the pool with onslaught enabled are gold rupees and deku nuts 10, and ice traps can only take the appearance of items in the pool. (I wonder what actually happens if there are no junk items in the pool?) |
If there are no junk items in the pool, it will use all of the junk models for the ice traps. |
To clarify, the reason I believe this is intended is that ice traps are only cloaked as items that are actually in the pool to make them more convincing. I've asked the other devs to make sure though. |
While intended, the results are pretty janky on these specific settings. Maybe it could be changed allow like one copy of a few more junk items to stay in the pool. The gold rupees outnumber the single 10 nuts item by quite a bit (it's also a bit weird that that single 10 nuts survives -- I think it might have just been missed when removing junk?), maybe it'd be better to not allow the quantity of items in the pool to affect how often an ice trap chooses that mask. |
If you turn on ice trap "Onslaught" and ice trap appearance as "Junk Items Only", the randomizer will only shuffle Rupees (200) and Deku Nuts (10) onto ice trap models. Problem seems to be the difference in how junk items are replaced with ice traps in ItemPools.py, and how the junk ice trap models are determined in Fill.py
The text was updated successfully, but these errors were encountered: