Veran Warp crash avoision

This text assumes that the veran warp setup with the red ring is used; that is, you move to x-position $7a, select the tile to get the red ring, close the map, move left, open the map, select the tile twice, then veran spawns.

When performing veran warp, it appears that the one factor we're not consistently accounting for is the time between pauses. Here's the thing: it looks like the "animations" have a pretty severe effect on veran warp. This consists of water, flower, whirlpool, etc. animations. Even though there are no such tiles on the screen, the animations are still happening behind the scenes.

The good news is that animations reset when a menu is closed. So, as long as a consistent number of frames pass between closing and reopening the map menu, the crashes should be preventable. On Zmaster's file, there seems to be a 4-pixel-wide area near the center of the screen where it will never crash, as long as you hold left the moment you close the map, and you pause again without stopping. This range was a bit different on another file, though, which was more "normal" (not a speedrun file).

There are actually two 4-pixel windows, one from x-positions $49-$4c and one from $4e-$51. Or, you can think of it as a 9-pixel window where the middle pixel crashes.

These images illustrate range $4e-$51:

Pixel $4e: https://imgur.com/rBS0sf2l.png
Pixel $51: https://imgur.com/eWVCPNDl.png


Here is a list of tested X-positions. To clarify, it's not the X-positions themselves that are inherently good or bad (in fact, probably all of these work with veran warp); however, if you start from the red ring spot (pixel $7a) and hold directly left from the first frame you gain control, and pause without letting go of left, then these x-values appear to either crash or not crash consistently.

46 - softlock
47 - softlock
48 - softlock
49
4a
4b
4c
4d - crash (writes to $e00b)
4e
4f
50
51
52 - crash
53 - crash
54 - crash (after closing map)
55 - crash (writes to $e00b)
56 - crash (writes to $e00b)
57
58 - crash
5a - crash
5d - crash

You can see link's current x-position in address $ff8d (assuming link is the only object on-screen).

==========================================
Other notes
==========================================

According to my theory, it doesn't matter how long you spend on the map screen. The results are, in fact, determined the moment you open the map, not the moment you press A. This hasn't been fully verified.