GS:TLA OOB Memory Problem

	THE GS:TLA OOB WEIRDNESS PROBLEM

Certain encounters can influence what happens to the out of bounds landscape making some skips impossible or significantly changing the requirements (most notably in GS:TLA No S&Q categories).

The problematic encounters write values to the memory addresses between 0x02023000 and 0x02024000. Presently the utility script has been updated to include a diagnostic utility (enabled by shift+d) to check whether memory has been written into 0x02020000-0x02024000 upon a change in area. [Script available from my pastebin or discord]

Using this utility a few notable problematic encounters have been identified:
- An encounter with a Gorilla enemy in the second position.
- An encounter with a Mini-Goblin in the second position, unless paired with a Angle Worm
- An Angle Worm - Angle Worm - Mini-Goblin encounter

Since the cause of the problem depends on the enemies in an encounter as well as their position within the encounter it is very difficult to manually check every area to find an exhaustive list of bad encounters.

Hence, it would be convenient to know why this behavior occurs and deduce which encounters are likely to be problematic from this understanding.