Table of Contents
STEAM/ASPYR ONLY
In KotOR 1 and the legacy versions of KotOR 2, there is no error handling for loading a save where there is no module present for the destination module. For whatever reason, the Steam/Aspyr build does handle this scenario. Whenever you attempt to load into a module that does not exist on the save, this version will happily generate that module, and along with it a new Main Character: The Dev Character.
There are two ways the dev character can be obtained:
Saving in a module with the include-in-save flag set to false This occurs when by various innocuous means (i.e. an Anywhere Menu Glitch) you manage to gain control in a module that doesn’t normally get included in the save. Examples include the swoop minigames. By saving in one and then forcing the game to load such a save, the dev character will be acquired, because the game is loading a module with no data. An example of this process using Telos Swoops (Courtesy of 30cents)
Loading a save with incorrect metadata that targets a nonexistent module (Forward Hotshot) This occurs when performing the Hotshot glitch to a destination that either hasn’t yet been explored by the original save or was deleted from the original save. This could be done in it’s most simple form by saving outside of a module that you will be going to for the first time, entering this new module, and then hotshotting to this destination (As shown in the below video). This could also be done by saving in a location that will be deleted (such as the damaged Ebon Hawk) and then hotshotting)back their later in the game. Example(Courtesy of 30cents)