Recurring elements in the Final Fantasy series

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
The logo of the Final Fantasy series.

Final Fantasy is a media franchise created by Hironobu Sakaguchi, and developed and owned by Square Enix (formerly Square). The franchise centers on a series of fantasy and science fantasy role-playing video games (RPGs). The eponymous first game in the series, published in 1987, was conceived by Sakaguchi as his last-ditch effort in the game industry; the title was a success and spawned sequels. While most entries in the series are separate from each other, they have recurring elements carrying over between entries: these include plot themes and motifs, gameplay mechanics such as the Active Time Battle (ATB) system, and signature character designs from the likes of Yoshitaka Amano and Tetsuya Nomura.

The artwork for the series has been associated with multiple artists: the three most prominent being Amano, Nomura and Akihiko Yoshida: Amano designed characters up to Final Fantasy VI, Nomura has designed characters for multiple games since Final Fantasy VII, and Yoshida has been involved in Final Fantasy XII, XIV and titles associated with the fictional world of Ivalice. The original gameplay created by Akitoshi Kawazu was based around Dungeons & Dragons and Wizardry. Starting with Final Fantasy IV, the Hiroyuki Ito-designed the ATB system took prevalence: variations of the ATB system have been used in multiple entries since then. These various aspects have been positively received by critics over the series' lifetime, contributing to its overall worldwide success.

Overview

Final Fantasy began with the development of the titular first game in the series: developed at Square, later dubbed Square Enix after its 2003 merger with Enix.[1][2] Final Fantasy was created as creator Hironobu Sakaguchi's last ditched attempt at success within the video game market: Sakaguchi had long wished to create a role-playing title, but the company had denied him the opportunity until then. The first Final Fantasy released in 1987, and was a commercial and critical success that fueled the development of further titles.[1][3] The series garnered international popularity with the release of Final Fantasy VII (1997) for the PlayStation, which became the highest-selling Final Fantasy title to date.[4] Final Fantasy has become one of Square Enix's major gaming franchises: as of 2016, the series has sold 110 million copies worldwide across 48 video game releases.[5]

Scenarios

A man sitting in a chair and speaking in a microphone.
Series creator Hironobu Sakaguchi in 2007, who worked on multiple game scenarios.[6]

The Final Fantasy series consists of multiple games that, while generally having separate settings and narratives, share common themes and motifs in their worlds and plots.[7][8][9] Multiple writers have worked on the Final Fantasy series over its existence, the most prominent having worked on the mainline titles. The first Final Fantasy was Kenji Terada, who was asked on board the project by staff after impressing them with his work on the anime adaptation of Kinnikuman. His job was to create a narrative-focused game to contrast against the gameplay-focused Dragon Quest.[10] Terada would provide the scenarios for Final Fantasy II (1988) and Final Fantasy III (1990). After a "falling out" between Square and Terada, scenario work was delegated to Takashi Tokita. Tokita also wrote the scenario for Final Fantasy IV (1991), along with being the game's designer.[11][12] For Final Fantasy V (1992), the scenario was a collaboration between Sakaguchi and Yoshinori Kitase.[13] Final Fantasy VI (1994) was worked on by a group of four or five different writers, including Kitase.[13][14][15] Sakaguchi was responsible for providing the basic story from the original game until Final Fantasy VI.[6] Sakaguchi would also write the scenario for Final Fantasy IX (2000).[16]

One of the notable recurring writers is Kazushige Nojima: he first joined the development team for Final Fantasy VII, and would later write the scenario for Final Fantasy VIII (1999).[17][18] He was also a major contributor to Final Fantasy X (2001) alongside other writers. He returned to write the scenario for Final Fantasy X-2 (2003), despite initial reluctance due to its upbeat feel when compared to its predecessor. His later supplementary material would return to a darker theme.[19] Nojima also created the original scenario of Final Fantasy XV (2016), then called Final Fantasy Versus XIII. His original scenario was reworked for Final Fantasy XV by Saori Itamuro.[20][21] Another recurring writer is Daisuke Watanabe. His first job as a scenario writer was with Final Fantasy X.[22] He worked on Final Fantasy XII (2005) as a scenario writer after original writer Yasumi Matsuno left due to illness.[23][24] The initial script was written by Miwa Shoda, whose work was fleshed out by Watanabe.[25] Watanabe would later work on the scenarios of Final Fantasy XIII (2009) and its sequels, which would become one of his major projects.[26] The scenario for Final Fantasy XI (2002) was created by Masato Kato, who returned for the expansion Rise of the Zilart.[27] For Final Fantasy XIV (2010) the writer was Yaeko Sato, who also worked on Final Fantasy XI and Final Fantasy XII: Sato stayed on as lead writer for Final Fantasy XIV: A Realm Reborn (2013), alongside new writer Kazutoyo Maehiro.[28][29][30]

The first title to receive a direct sequel was Final Fantasy X: Final Fantasy X-2 is set in the same fictional world of Spira, while using a lighter tone than its predecessor. No sequel to Final Fantasy X was planned initially.[31][32] Final Fantasy XIII was also intended to be a standalone title, and was later expanded into the series' first official trilogy with the development of Final Fantasy XIII-2 (2011) and Lightning Returns: Final Fantasy XIII (2013).[33] Final Fantasy VII was later expanded into a multimedia series titled Compilation of Final Fantasy VII, which included video games (Before Crisis, Dirge of Cerberus, Crisis Core) and film projects (Advent Children, Last Order).[34][35][36] A different subseries linked by common elements, and indirectly inspired by the Compilation, is Fabula Nova Crystallis Final Fantasy: while the subseries' games have unique settings and stories, they all share a common mythos surrounding crystals and their associated deities.[37] Fabula Nova Crystallis was originally planned as a platform for the development of multiple games planned out in advance, compared to Final Fantasy producer Shinji Hashimoto to the Star Wars and The Lord of the Rings film franchises.[38] A world later incorporated into the Final Fantasy series is Ivalice, the setting for titles within the game collection known as the Ivalice Alliance. Taking place within a single world across a large time period, Ivalice is the setting for Final Fantasy Tactics (1997), Final Fantasy XII and Vagrant Story (2000).[39] Vagrant Story did not originally take place in Ivalice, being incorporated into the subseries by Square Enix long after its release. The game's references to other Final Fantasy titles were originally intended as fan service.[40][41] Ivalice itself was the creation of Yasumi Matsuno, the main creative force behind Tactics and Vagrant Story. It first appeared in Tactics.[39][42] Matsuno's work with Ivalice later inspired the scenarios for A Realm Reborn.[43]

Common elements

A screenshot from Final Fantasy V, showing a crystal in its temple. Crystals have had a central place in multiple Final Fantasy games.[44]

Stories in the series frequently emphasize the internal struggles, passions, and tragedies of the characters, and the main plot often recedes into the background as the focus shifts to their personal lives. Other aspects explored are the relationships between characters, which range from love to rivalry. Other recurring situations that drive the plot include amnesia, a hero corrupted by an evil force, mistaken identity, and self-sacrifice.[7][8][45][46][47] The central conflict in many Final Fantasy games focuses on a group of characters battling an evil, and sometimes ancient, antagonist that dominates the game's world. Stories frequently involve a sovereign state in rebellion, with the protagonists taking part in the rebellion. The heroes are often destined to defeat the evil, and occasionally gather as a direct result of the antagonist's malicious actions. Twin antagonists, with the second main antagonist being hidden for the majority of the game, is also a recurring element.[44] Other common plot and setting themes include the Gaia hypothesis, an apocalypse, and conflicts between advanced technology and nature.[44][47][48]

A recurring concept within Final Fantasy settings is the use of important magical crystals: in early games, they represented the Japanese classical elements, and would be instrumental in keeping the world in balance. Due to this, control over the crystals forms part of a chosen games' core narrative.[44] The concept of crystals was introduced into the original game by game designer Koichi Ishii.[49] Since then, crystals have taken prominent roles in Final Fantasy III, Final Fantasy IV, Final Fantasy V, Final Fantasy VI, Final Fantasy VII and Final Fantasy IX. They took minimal roles in Final Fantasy II, Final Fantasy VIII, Final Fantasy X and Final Fantasy XII.[44] Crystals also took a central role in Final Fantasy XIII and Final Fantasy XV, which both used the crystal-based Fabula Nova Crystallis lore.[50][51] Crystals were included in A Realm Reborn as a central plot due to being given "short shrift in recent titles".[30] Most titles feature names inspired from various cultures' history, languages and mythology, including Asian, European, and Middle-Eastern. In-game items such as weapons follow this tradition: the two most notable are Excalibur and Masamune, derived respectively from the Arthurian sword and legendary Japanese swordsmith.[7][8][44]

Characters and monsters have made appearances in multiple Final Fantasy titles, although they remain unconnected in a narrative sense.[7][44] A recurring animal in Final Fantasy is the Chocobo, a galliform bird that regularly acts as a means of transport for characters. The Chocobo was created by Ishii for Final Fantasy II from designs created during development of the first Final Fantasy, and have appeared in every mainline Final Fantasy title since then.[10][44][52] A second recurring race are the Moogles, whose Japanese name is a portmanteau of the words mogura (mole) and kōmori (bat): while frequently seen minding stores or assuming some other background role, they have also appeared as party allies or playable characters.[44][53][54] Other recurring races include common monsters such as the cactus-like Cactuar, the Malboro, the Behemoth, the Tonberry, and the Iron Giant.[55][56][57][58] A human character that has frequently appeared is Cid (シド Shido?). Making his debut in Final Fantasy II, he has appeared in multiple forms as everything from a player character to an antagonist. His most frequent occupation is an engineer, and he is commonly associated with the party's airship.[59] Cid was originally created as a character that would appear in multiple forms: his one common attribute was that he was an intelligent and wise figure "like Yoda from the Star Wars series".[60] Two other recurring human characters are Biggs and Wedge, duo named after characters from the Star Wars franchise who are often used for comic relief. Making their debut in Final Fantasy VI as footsoldiers, they have since appeared in multiple Final Fantasy titles.[7][58][61] A different character is Gilgamesh: first appearing in Final Fantasy V, he has made cameo appearances in multiple Final Fantasy titles since then.[62] Gilgamesh was created by Sakaguchi, and designed by Tetsuya Nomura and Yoshitaka Amano.[63]

Gameplay

Since the series' inception, gameplay in the majority of mainline Final Fantasy titles has followed certain conventions of the role-playing genre. Players take control of a party of characters, commanding anywhere between three and eight during battles. Players must face a variety of enemies who continually try to damage the player: in battle, the characters can select a variety of commands from a menu, such as "Fight", "Magic", "Item", as well as other special skills such as "Steal", "Throw" or "Summon". The battle is won when all enemies are defeated. Up until Final Fantasy XI, battles were triggered through random encounters: starting with Final Fantasy XI and continuing in following games, enemies were visible in the field and could be avoided. A recurring means of travel are airships, which are often unlocked for players fairly late in the game.[7][8][44] In common with other role-playing games, Final Fantasy most commonly uses an experience point-based leveling system, where each battle awards experience points, and gaining levels increases character statistics such as health and magic.[7][8][64]

Magic is another common role-playing element in the series. The method by which characters gain magic varies between installments, but is generally divided into classes organized by color: "White magic", which focuses on spells that assist teammates; "Black magic", which focuses on harming enemies; "Red magic", which is a combination of white and black magic, "Blue magic", which mimics enemy attacks; and "Green magic" which focuses on applying status effects to either allies or enemies.[7][8][65] Different means of transportation have appeared through the series. The most common is the airship for long range travel, accompanied by chocobos for traveling short distances, but others include sea and land vessels. Following Final Fantasy VII, more modern and futuristic vehicle designs have been included.[44] For Final Fantasy XV, a car dubbed "Regalia" was introduced as both a ground-based transport and later as a vehicle that could be converted to function as an airship.[66]

Battle systems

The Active Time Battle System in its first incarnation: the SNES version of Final Fantasy IV.

The battle system of the original Final Fantasy was designed by Akitoshi Kawazu. When creating it, he closely followed the mechanics created in the Western tabletop game Dungeons & Dragons, particularly the incorporation of enemy-specific weaknesses that were otherwise missing from Japanese games at the time. He also added elements such as weapon and item abilities based on their successful implementation in Wizardry.[67] This first version of the battle system was a traditional turn-based system with characters appearing on the left-hand side of the screen, a feature later adopted by multiple other role-playing games (RPGs).[8] For Final Fantasy II, Kawazu designed a battle system based around a more focused approach to story, along with accommodating for character classes being locked to specific characters.[67] In Final Fantasy II, character abilities improved based on the number of times they were used and the number of hit points accumulated during battles: if a character used magic, they would become strong in magic while other attributes would suffer.[67][68] For Final Fantasy III, the system changed back to a traditional class-based model: Kawazu stated that the reason for this was because no-one could fully understand the system he had created for Final Fantasy II.[67]

The battle system most closely associated with Final Fantasy is the "Active Time Battle" (ATB) system: while utilizing a turn-based combat system, action meters are assigned to all characters that are emptied when they act in battle. Each player character being issued a command when their action meter is filled: enemies could attack at any time despite player actions being in progress, adding an element of urgency to battles.[7][8][65] The ATB system was designed by Hiroyuki Ito. According to Kawazu, Ito was inspired while he was watching a Formula One race and seeing racers pass each other at different speeds. This gave him the idea of different speed values for the individual characters.[69][70] Ito himself described the inspiration as his wish to balance pure turn-based mechanics with real-time battle mechanics, which played into a movement in Formula One where cars were shifting towards using semi-automatic gearboxes. For Final Fantasy V, Ito evolved the system further as he felt the version in Final Fantasy IV was incomplete.[71] A mechanic introduced in Final Fantasy VII was Limit Breaks, special cinematic moves that have become a staple of the series.[72] The ATB system was in use until Final Fantasy X, which switched to a system called the "Conditional Turn-based Battle" system: while reverting to a purely turn-based model, it included additional elements such as in-battle party member switching.[7][8][65] Final Fantasy XI, Final Fantasy XIV and its sequel A Realm Reborn used real-time command-based combat systems and removed random encounters, playing in a similar fashion to other contemporary MMORPGs.[73][74][75][76] Final Fantasy XII used a similar real-time command-based system to Final Fantasy XI: dubbed the "Active Dimension Battle" system, characters fought enemies in environments without random encounters, with players acting on commands inputted by the player.[71][76]

The battle system for Final Fantasy XIII was designed to retain the strategic elements of earlier titles while emulating the cinematic action of Final Fantasy VII: Advent Children. While retaining the ATB system, elements such as magic points were removed, and a strategic role-change system dubbed the Paradigm System was implemented, with the roles being based on Final Fantasy jobs.[77][78] Final Fantasy XIII-2 continued using the Paradigm system with added gameplay functions based on criticism of the first game,[79] while Lightning Returns: Final Fantasy XIII changed to a more action-based, single-character version that incorporated design elements cut from Final Fantasy XIII.[80][81] Final Fantasy XV used an action-based system that was described as a "realistic" version of those used in the Kingdom Hearts series and spin-off title Final Fantasy Type-0. Unlike all previous mainline Final Fantasy titles, the players could only control one character out of the four-strong party. While the team experimented with multiple character control, it was decided that it presented to many development difficulties.[82]

Recurring mechanics

The Job System, represented in Final Fantasy V. First introduced in Final Fantasy III, it has been a recurring feature throughout the series.

Character classes have been present in Final Fantasy since the first title, where players chose a character class from the outset. Kawazu created this system to give players freedom to customize the party. For Final Fantasy II, jobs were attached to specific characters.[67] Each character class in a Final Fantasy game has unique abilities which develop as the player's level increases. In some titles, the player can assign a character with a specific class at the start of the game, while others allow characters to combine and learn abilities from a number of classes. In addition to other abilities, a character's class usually determines the types of weapons and armor that they can use.[44]

Final Fantasy III saw the introduction of the Job Change System: through special crystals, the four player characters were granted a variety of jobs or character classes that could be switched at any point by the player.[68] The Job Change system was initially proposed by Sakaguchi as he wanted to give players freedom to customize the party members: with five characters with eight jobs each, the team needed to create forty different pixel portraits.[83] The Job System have continued to have a strong role in the series, being most prominent in Final Fantasy V with twenty-two available jobs.[8][84] Jobs have recurring functions throughout the series. Some of the more traditional classes include the Warrior/Fighter, the Dragoon, the Thief and variations on magical classes such as White and Black Mages. More original classes have appeared throughout the series, such as Bards, Scholars, and Summoners. Due to the series' popularity, they have become staples of RPGs since their debut. The complexity and scope of the class system varies from game to game.[7][8] The original Final Fantasy XIV did away with the Job System in favour of a character class-driven system where equipment determined skills and growth.[73] For the later stages of Final Fantasy XIV and later A Realm Reborn, the Job System was reintroduced as a second level to the current class system.[85][86] Many Jobs, such as the Dragoon, the Summoner, and the Red Mage have become closely identified with the series.[74][84][87]

A different system is "Summoning", a mechanic where characters can call upon Summoned Monsters (Summoned Beasts (召喚獣 Shoukanjuu?) in Japanese) are evoked to aid the party through cinematic actions.[7][8][44][88] The concept of summoning was proposed for the first Final Fantasy, but it was not implemented until Final Fantasy III.[89] Summons can be either optional acquisitions unnecessary for progression of the narrative, or tied to story events and particular characters.[7][8][44] The names of summons derived from multiple cultures, including Egyptian, Middle-Eastern and Classical mythology.[7][8][44] As groups within the games, they have been referred to by several names (Espers, Guardians, Aeons, Eidolons, Archeans), and have taken either core roles in the story or less prominent roles as tools for the player characters.[44][88][90]

Art design

An artwork by Yoshitaka Amano depicting a group of fourteen characters, the playable cast of Final Fantasy VI.
An artwork by Tetsuya Nomura depicting a group of eight characters, the playable cast of Final Fantasy VII.
The artwork of Final Fantasy was defined by two different artists: Yoshitaka Amano (left) and Tetsuya Nomura (right).[91]

The artwork and character designs of the first Final Fantasy were created by Yoshitaka Amano, a noted artist who had worked with Tatsunoko Productions on multiple notable anime series including Gatchaman, and also did illustrations for Vampire Hunter D.[92] Amano was brought on board the first Final Fantasy as general artwork designer, filling that role for Final Fantasy II and Final Fantasy III.[49][92] For Final Fantasy IV, Amano was given more freedom to create elaborate character designs.[93] Amano returned as character designer and general artwork for Final Fantasy V.[94] Final Fantasy VI, in addition to featuring work by Amamo, also had contributions from other designers including Kaori Tanaka.[95] From the first Final Fantasy to Final Fantasy IV, Amano created his artwork based on specific descriptions from game staff, while for Final Fantasy V and Final Fantasy VI it was the game staff that took and adjusted his artwork to suit the games.[96] He returned as a character designer for Final Fantasy IX, working from specifications provided by the game's staff.[97] For Final Fantasy XI, Amano created the game's world map. One of the designs he recalled was for the summon Bahamut: while the original Bahamut was an aquatic monster, he did not know this at the time, so he designed Bahamut as a "mecha dragon".[96] As of Final Fantasy XV, Amano's artwork has been created fairly early in a game's development based on the basic themes.[90] Amano's most enduring contribution to the series is his logo designs: receiving design documents as primarily text-based requests and descriptions, he treats each logo as a piece of full artwork rather than a simple logo.[98] Since Final Fantasy IV, the current font style was adopted, along with a specially-designed logo by Amano. The emblem relates to a title's respective plot and typically portrays a character or object in the story. Subsequent remakes of the first three games have replaced the previous logos with ones similar to the rest of the series.[8] His work on Final Fantasy brought him international fame.[98]

From Final Fantasy VII onward, the main character designer for the series was Tetsuya Nomura, whose first major contribution had been character and monster designs for Final Fantasy VI. He was chosen by Sakaguchi as the character designer for Final Fantasy VII after being amused by his storyboards for Final Fantasy VI.[99][100] His greater involvement was also due to scheduling conflicts with Amano's overseas trips to open exhibitions in Europe and North America. Nomura would end up having a substantial input into the character stories.[17][101] While Final Fantasy VII would become Nomura's favorite project, its graphical limitations meant that his art style was limited in turn. For Final Fantasy VIII, he worked with other artists to make the characters more realistic.[18][102] Nomura returned for Final Fantasy X, designing the main cast and creating a setting influenced by the South Pacific, Thailand and Japan.[103] For Final Fantasy XV, Nomura created the main characters alongside being one of the main creative forces behind its development.[104] A trend with Nomura's characters is their names being related to the weather or the sky (Cloud, Squall, Tidus, Lightning).[102][105][106] He wanted to break this tradition when designing Noctis Lucis Caelum, but after Final Fantasy XIII's Lightning was given a weather-based name, Nomura gave Noctis his current name:[106] Noctis' name translates from Latin to "Night of Light Sky".[107][108]

Other notable artists include Akihiko Yoshida, Isamu Kamikokuryo and Yusuke Naora.[109][110][111] Yoshida's first major games were Final Fantasy Tactics and Vagrant Story, which he worked on together with Hiroshi Minagawa. He also did design work for Final Fantasy Tactics Advance, creating the Bangaa race that would later appear in Final Fantasy XII.[109][112] For Final Fantasy XII, he designed the main characters. As inspiration for their physical appearances, Yoshida used a variety of influences from multiple cultures.[109] He returned to work on Final Fantasy XIV, where he needed to adjust from working on a static project to designing for the more fluid environment of an MMORPG.[113] He would also contribute designs to A Realm Reborn, and its first expansion Heavensward.[29][114] Isamu Kamikokuryo first did work on Final Fantasy VIII and Final Fantasy X, then became art director for Final Fantasy XII. He would return to this role for Final Fantasy XII: Revenant Wings, and the Final Fantasy XIII games: he had a major role in the design of Lightning's new appearance in Final Fantasy XIII-2. He was also involved in the world design of Final Fantasy XV.[21][110][115][116][117] Yusuke Naora has had a presence within the series since Final Fantasy VII, for which he designed the kanji logo for the antagonistic Shinra Corporation. His involvement in the series has primarily been as an art director for titles such as Final Fantasy X and Final Fantasy XV, in addition to creating character designs for Final Fantasy XIII-2 and Final Fantasy Type-0.[21][111][118]

Other artists have also contributed to the series. Hideo Minaba contributed character designs to Final Fantasy IX, worked as an art director for Final Fantasy XII, and would later design characters for Final Fantasy XIII-2.[109][119][120] Italian-born artist Roberto Ferrari worked as a secondary character designer for Final Fantasy Type-0, Final Fantasy XV and Final Fantasy VII Remake.[121][122][123] Yusaku Nakaaki worked with Naora and Nomura to create characters for Final Fantasy Type-0, and along with Ferrari created secondary characters for Final Fantasy XV.[124][125][126] Akira Oguro created the character artwork for the mobile titles Final Fantasy IV: The After Years and Final Fantasy Dimensions.[127][128] Toshitaka Matsuda's first major work was on Final Fantasy XII: Revenant Wings, and he would later serve as a costume and character designer for Lightning Returns: Final Fantasy XIII.[129] Toshiyuki Itahana first worked on character designs for Final Fantasy IX, then later served as a main artist for the Crystal Chronicles spin-off series, Lightning Returns: Final Fantasy XIII, and the mobile game Mobius Final Fantasy.[129][130] A key designer for much of the series' life was Kazuko Shibuya, who did sprite designs from Final Fantasy to Final Fantasy VI. She also did work on Final Fantasy Dimensions.[94] A notable outside collaborator was Hiromu Takahara, lead designer for Japanese fashion house Roen, who created the clothing for the main cast of Final Fantasy XV.[104][131]

Influence

Lua error in package.lua at line 80: module 'strict' not found. The Final Fantasy series and several specific games within it have been credited for introducing and popularizing many concepts that are today widely used in console RPGs. Many console RPGs featured one-on-one battles against monsters from a first-person perspective. The side view perspective with groups of monsters against a group of characters used by the early Final Fantasy games has been frequently imitated, supplanting the prior RPG standard of one-on-one battles against monsters from a first-person perspective.[132][133][134] The class changing systems and multiple types of magic available were also influential on the genre, as were the use of a variety of vehicles.[135][136] The activity-based progression system introduced in Final Fantasy II has been used in later RPG series such as SaGa,[137] Grandia,[138] and The Elder Scrolls.[139]

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ 7.00 7.01 7.02 7.03 7.04 7.05 7.06 7.07 7.08 7.09 7.10 7.11 7.12 7.13 Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 8.11 8.12 8.13 8.14 Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ 21.0 21.1 21.2 Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ 30.0 30.1 Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ 44.00 44.01 44.02 44.03 44.04 44.05 44.06 44.07 44.08 44.09 44.10 44.11 44.12 44.13 44.14 44.15 Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ 58.0 58.1 Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ 65.0 65.1 65.2 Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ 67.0 67.1 67.2 67.3 67.4 Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ 68.0 68.1 Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ 71.0 71.1 Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ 73.0 73.1 Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ 74.0 74.1 Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ 76.0 76.1 Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ 84.0 84.1 Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ 88.0 88.1 Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ 90.0 90.1 Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ 92.0 92.1 Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ 94.0 94.1 Lua error in package.lua at line 80: module 'strict' not found. Translation
  95. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  96. ↑ 96.0 96.1 Lua error in package.lua at line 80: module 'strict' not found.
  97. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  98. ↑ 98.0 98.1 Lua error in package.lua at line 80: module 'strict' not found.
  99. ↑ Lua error in package.lua at line 80: module 'strict' not found. Translation
  100. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  101. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  102. ↑ 102.0 102.1 Lua error in package.lua at line 80: module 'strict' not found.
  103. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  104. ↑ 104.0 104.1 Lua error in package.lua at line 80: module 'strict' not found.
  105. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  106. ↑ 106.0 106.1 Lua error in package.lua at line 80: module 'strict' not found.
  107. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  108. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  109. ↑ 109.0 109.1 109.2 109.3 Lua error in package.lua at line 80: module 'strict' not found.
  110. ↑ 110.0 110.1 Lua error in package.lua at line 80: module 'strict' not found.
  111. ↑ 111.0 111.1 Lua error in package.lua at line 80: module 'strict' not found.
  112. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  113. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  114. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  115. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  116. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  117. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  118. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  119. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  120. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  121. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  122. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  123. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  124. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  125. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  126. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  127. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  128. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  129. ↑ 129.0 129.1 Lua error in package.lua at line 80: module 'strict' not found.
  130. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  131. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  132. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  133. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  134. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  135. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  136. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  137. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  138. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  139. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Recurring_elements_in_the_Final_Fantasy_series&oldid=721845376#Summoning_Magic"