Romancing Saga 2 (ロマンシング サ・ガ2) is the fifth game in the SaGa series (second in the Romancing SaGa SNES trilogy). Like the previous SaGa trilogy, the only storyline connection between the three is the presence of "The Bard" (AKA: Haolahn, mascot of the entire trilogy).

Game composer Kenji Itō (who is also known for his work on the Mana series) composed the score.


An i-mode (exclusive to Japan) version of the game was released on November 1, 2011.

A rerelease (Japan exclusive) was released on the Wii's Virtual Console on March 23, 2010 with items from other SaGa games in addition to two new classes: Ninja and Onmyoji Monk. A new battle formation and a bonus dungeon which can be bought as DLC with four variants was also made available.

A remake for iOS, Android, and PS Vita has been released in Japan on March 24, 2016. It has been revealed that it will be released in North America for iOS and Android only. That was announced on April 7, 2016 on Square Enix's Japanese Twitter via account. On April 28, 2016, Square Enix confirmed that it will be released in North Anerica with a trailer and a website. On May 19, 2016, the release date for the iOS and Android version was revealed, May 26th, 2016, priced at $17.99. The PS Vita English version was announced on Twitter by the series creator Akitoshi Kawazu. This marks the official debut of Romancing SaGa 2 overseas.

Link to English Website:

In Romancing SaGa 2, the player plays as the Emperor or Empress of Barene, a castle located in the northwest corner of the game's world: Avalon. He or she begins the game as King Leon and later plays as his various heirs down through the years. Leon hands his kingdom over to his son, Gellard. At the end of Gellard's reign and so on, the player is able to choose his or her own successor and pass on Gellard's abilities to them. At the end of each generation, he or she will be given a choice of four heirs. Their identity is based on a combination of chance and anyone whom the player has assisted or allied within in a past generation.

The player has to defeat all Seven Heroes.


List of Romancing Sa-ga 2 Characters

Tech System

The technique system in Romancing SaGa 2 was the first of the series to utilize a "spark" system. This system would become one of the cornerstones to how later RS games handle tech learning.

In this game, using a weapon gives you the random chance to spark a new technique in battle. The requirements can be somewhat stringent an counter-intuitive at times. However, not all characters can spark all the techniques. The list of techs available for sparking to a particular character is dependent upon their spark type.

Generation System

Romancing Sa-Ga 2 functions off of a generational system, where after certain events, time moves forward, leading to a new generation of characters. This allows the players the chance to try a new set of characters and explore new story lines.

Generation Mechanics

Formation System

Romancing Saga 2 features a formation system where players can augment their party further through learning new formations. There are 16 total formations in the original SNES version (1 being inaccessible without a gameshark), and 18 in the remake on iOS, Android, Vita. (The original inaccessible one on the SNES was brought back and implemented with 2 additional added)

Formation System


Romancing Saga 2, unlike other titles produced by Square Enix, does not use a random chance encounter system. All enemy encounters only happen when you run into a visible enemy entity on the map. However, enemy generation within the encounter is impacted by the enemy type you ran into on the map screen and by your total battle count. (In the remake, you can find your battle count in the lower right hand corner on the second floor of the Avalon castle and speak to the minister sitting in the small room)

Romancing Saga 2 Enemy Data


Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.