Warrior Within story progression explained, probably

Warrior Within uses two kinds of .bin-files, ones containing the word "wow" and others containing the word "wol". The wow-files contain small pieces of levels, for example the Access Room and all the triggers and such in that area is in one wow-file. The wol-files are lists of wow-files so for example, the Access Room's wol contains the wow for Access Room as well as a bunch of other wows near it, in this case some hallways leading to Access Room from all directions. When you walk into a loading trigger in the game, a wol-file is loaded.

Another part of the file name is a series of 3 numbers at the beginning, which is the area code. For the most part the area codes follow a simple logic so it's easy to tell where they lead. For example, area code for Access Room is 055 and the code for Hourglass Room is 065. Because the game isn't linear this doesn't always match nicely but it makes it easier to tell where the files are from.

Among the wow-files there is a file called Accessories, and it also gets loaded when a wol-file loads. In case of the area surrounding Access Room, it's 055_Accessories_wow. That file doesn't contain any models but instead has other important information that's needed to load the area correctly. In there are GPXXX_Manager.gao -files (XXX being an area code, for example GP710_Manager.gao is part of the final boss fight area). The manager files are what connect certain areas together so that the game can keep track of events in the storyline without just loading the same room the same way every time.

In 055-area, there is a StoryGateV10 and another trigger labeled with V10, which triggers the mask off cutscene. I'm not gonna go into why this is important because I don't know, but being the only V10s in the game we'll assume they're connected and important. The Accessories-wow of 055 refers to a bunch Managers. By cross referencing that list of Managers with the any%-route we can find some areas that are not visited and ignore them. Then by checking the Accessories files from the area codes that the Managers refer to, we have a way to backtrack a web of files and keep excluding area that are not on the any%-route.

By doing that with 055 being the starting point, I noticed that the web didn't go very deep and only went to four areas that are in the route - 055 (Access Room), 205 (second part of Mechanical Tower), 425 (Library) and 605 (Mystic Cave). Those four areas are linked by managers and from that I concluded that somewhere in those rooms (most likely Library as that's the first one you visit and it's visited as both SW and Prince) the game makes a check to see if you are Sandwraith. If you are, it's noted by the 425_Manager. Then you move on to Mystic Cave where the note in 425_Manager is checked to be OK and a note is made in the 605_Manager. Same repeats in Mech Tower and Access Room. In the final check in the Access Room Area this chain of notes in Managers activates StoryGateV10 which activates the cutscene trigger which makes you remove the mask. The mask off cutscene however isn't all that important as all the notes are made in the Managers and the chain continues all the way to 710, the final arena with Kaileena.

So basically what I said about StoryGateV10 and the trigger related to it is crap as they're unimportant when everything is handled by Managers. That's where my train of thought went while writing and it's probably way off the rails so if you didn't understand any of this don't worry, I'm not sure I did either.