| rdfs:comment | - The glitch is triggered by first saving the game on the overworld at whatever point in the game the player wants to access the airship, and then continuing through the game as normal without saving. When the player reaches the Floating Continent, they must cross it and then return to the Blackjack, fly around for a bit without landing, then return to the Floating Continent and trigger a Game Over there. When the game resumes, the player will be returned to the point where they last saved, except they will be on board the airship.
|
| abstract | - The glitch is triggered by first saving the game on the overworld at whatever point in the game the player wants to access the airship, and then continuing through the game as normal without saving. When the player reaches the Floating Continent, they must cross it and then return to the Blackjack, fly around for a bit without landing, then return to the Floating Continent and trigger a Game Over there. When the game resumes, the player will be returned to the point where they last saved, except they will be on board the airship. Because the airship is acquired through glitching, its use comes with many limitations. For instance, the interior of the Blackjack cannot be accessed, and the player can only land the airship once before it becomes inaccessible, depending on when in the story the glitch is triggered. For this reason it's recommended the player land near Zozo if they intend to complete the game, as it's close to where the player would first acquire the airship normally, and the furthest point in the story where the game can be completed using the glitch, as the airship becomes accessible again after Setzer is named. Because triggering the glitch requires the player to play through the entire World of Balance up to the Floating Continent without saving, it is impractical (but possible) to perform without using emulators and savestates. In spite of its limitations, the airship glitch can be used to cause numerous scripting errors, as skipping from Narshe to Zozo fails to trigger many in-game scripts with many interesting effects:
* Using this glitch, the player can swap out Banon for some of the other temporary characters, such as Maduin and General Leo. Because all temporary characters share the same character slot, the player can use the glitch to skip Banon's scenario, visit Thamasa and play out the sequence with General Leo, and then return to Banon's scenario earlier in the game, where Banon is now replaced with Leo. The player can also trigger the glitch again to use these temporary characters outside of their intended areas, though their use is limited as they disappear from the party as soon as the player enters the party selection screen.
* By skipping scenes where characters are first named, it's possible to use the Ten Moogles in their stead, not unlike the infamous Moghan glitch. This is because the Ten Moogles share character slots with permanent player characters who appear later: the slots are overwritten when the characters are first named. If the player skips naming them, the game will continue to use the moogle in that character's slot in their stead.
* If the player skips the Phantom Train sequence with this glitch, they can replace Relm and Strago with the two Ghosts from this sequence by first recruiting Relm and Strago, then visiting the Phantom Train and recruiting one or two Ghosts. Since Relm and Strago share character slots with the Ghosts, the Ghosts are permanently written to their character slots after this event. Most importantly, the Ghosts' Possess command can then be used outside of the Phantom Train sequence, where no enemies are programmed with resistance/immunity against it (even bosses, up to and including Kefka). The Possess command can also be used by Gogo if one or two ghosts are kept in the party.
* If any character besides Celes is kept in the party for the Opera House sequence (such as Banon or Terra), their sprite breaks because only Celes has animations for the sequence—for any other character, the game simply loads garbage graphics.
* If the player plays the Lethe River sequence with a different party than intended, the main character may never get off and stay on the raft for various other sequences in the game.
* If the player skips the Figaro Castle scenario early in the game, they can trigger it later in the World of Ruin to return to the World of Balance. With this glitch it's possible to use Gogo and Umaro in the World of Balance as well.
* If the player uses this glitch to skip Sabin's scenario early in the game, it will become impossible to finish it later as at a certain point in the story NPCs are removed from Doma Castle. Visiting the castle during Sabin's scenario afterward will cause a cinematic to lock up, making it impossible to complete.
|
