Uploaded June 2021 | Updated September 2026, 2 weeks ago

---

Provisional name, will change when it settles.

NEW GLITCH found by OrangePlasticCup while playing randomizer. Link to his twitch channel: twitch.tv/orangeplasticcup

HOW TO: Fish up any sort of treasure in the sea. Get Forest Water to expire at the same time your grappling hook hits the treasure. The forest water textbox should come up before the salvage animation happens. LET GO OF GRAPPLE WHEN THE TEXTBOX COMES UP. Then close the textbox while not holding anything. This results in you getting a different item. When closing the textbox for that item, the game crashes.

EXPLANATION (entirely by LagoLunatic):

"Something about forest water expiring on that exact frame causes the salvage point tag you're about to salvage to no longer count as the active one (maybe the grappling hook going back up for one frame puts it out of the trigger?) but it still triggers the salvage. Because there's no active tag, the active index is set to -1.
There's no sanity check in place to prevent the chest from coming up when the index is negative.
This means that it tries to read the item ID from 4 bytes before the start of the list in RAM. This is in free space, not in the DOL, so what comes immediately before this list can probably be literally anything.
The symbol name of the pointer is daSalvage_c::mTagData_p

You can avoid this assertion error if either of the 2 conditions are met:
* The negative-indexed tag's "Kind" is anything but 0 (kind 0 are the only types of salvages that require a chart). The tag's "Kind" is at (list start) - 5
* The negative-indexed tag's chart is a real chart (so it sets that chart as complete, even though it really isn't). The tag's "SaveNo" is at (list start - 7). I think this needs to be in the range of 0x01-0x80 for the chart number to wind up being within a valid range."

This would have been impossible to figure out this quickly if it was not for LagoLunatic, this explanation being provided so quickly is a miracle.