-
Notifications
You must be signed in to change notification settings - Fork 498
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
Medigoron not properly resetting Broken Giant's Knife flag #4601
Comments
Relevant information: This is not a ship-specific bug, this same behavior has been tested and proven on console. Repairing Giant's Knife after you break it without both Kokiri Sword and Master Sword in the inventory will not flip the "broken" flag, but it will restore the knife's health. Breaking it again will flip the flag to "not broken" and will no longer allow you to repair it. Perhaps make it an optional fix in the Enhancements tab? |
How do you not have both the Kokiri Sword and Master Sword? |
This issue affects randomizer, where both Kokiri Sword and Master Sword can be shuffled, so if Giant's Knife is found before both of those, this issue can be noticed. Also obviously this could happen in a vanilla playthrough if the player escapes the forest to skip Kokiri Sword. |
Forest escape into DoT skip or glitching past mido in kokiri forest lets you skip Ksword in vanilla. |
8mb.video-j2H-MxxNL5lC.mp4
When the player has Giant's Knife and breaks it, the flag for "Goron's Sword (Broken)" is set in the inventory, but when purchasing a new Giant's Knife from Medigoron, this flag is supposed to become unset but it never seems to do so. This can also affect the B button sprite of Biggoron's Sword to appear as if it is broken permanently. This may also cause another issue, if you break a Giant's Knife (setting the flag to Broken), buy a new one from Medigoron, and break that one, the flag becomes flipped again back to fixed, however the sword is still broken, and Medigoron no longer sells you a new one because he thinks the sword is not broken.
The text was updated successfully, but these errors were encountered: