-
Notifications
You must be signed in to change notification settings - Fork 16
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
Key of Light / Dark - Multiple Issues #10
Comments
Can confirm. I might try to fork and fix this myself; does anyone have the API call handy for checking if a world has corruption or crimson? |
I believe I have fixed this issue. Here's a compiled release, if you'd like to check it out. |
Thanks! Confirmed working. While the randomization isn't exactly vanilla, this behavior is much preferred over the existing one. |
The Key of Light currently does not work at all - and the problem becomes quite obvious when looking at this line of code: https://github.com/Zaicon/InfiniteChestsV3/blob/master/InfiniteChestsV3/InfMain.cs#L373
The check is only looking for 3091, which is the Key of Night. Key of Light, 3092, was forgotten about.
The Key of Night works, but it only works when the current zone is Corruption / Crimson. This requirement does not exist in the vanilla game, and can be once again traced down to the same line of code: https://github.com/Zaicon/InfiniteChestsV3/blob/master/InfiniteChestsV3/InfMain.cs#L373
Edit: The error with Key of Light occurred with commit 5e386ca (otherwise known as 1.4 update). The issue with key spawning being bound to zones however appears to have always existed.
The text was updated successfully, but these errors were encountered: