Recap of my conversation with Lane: We were using the very first module (endar spire part 1, ie, Sheep's DLZ) as our example. We were looking for a specific UTT (instantiated trigger object) in the GIT file (which contains "game object instances and dynamic area properties"), but we could not find it. This UTT in question would transfer us to the Starboard Section module.

We could not find it in the save file either, which makes sense to me, seeing as its location is irrelevant to a save. In addition, whether we have interacted with it (triggered it) or not is not worth recording in the same way as a cutscene or animation.

I'm left with the idea that the UTT is instantiated (and exists only) during runtime, although we don't know how or when. Lane mentions that for doors like the one in question (starboard section door), the loading zone does not appear behind it until the door has been opened. Looking at our list of DLZs on record, it does seem that module-transition UTTs are linked to a specific instance of a UTD in some capacity (although this might be a coincidence; Sober's and mine are counterexamples).

The paragraph above poses some important questions. Why is the UTT not found behind the door until the UTD has been interacted with? Is the UTT instantiated when the module loads in? Is it instantiated upon interacting with a doorway in some way? And probably the most important question: how can I identify this UTT in the runtime heap?