Development of Final Fantasy XV

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The development of Final Fantasy XV, a Japanese action role-playing video game, began in 2006 shortly before its announcement at that year's Electronic Entertainment Expo. Square Enix is handling primary development on Final Fantasy XV, and is set for release on September 30, 2016; the total development time covers approximately ten years. The game was originally announced as Final Fantasy Versus XIII, a PlayStation 3-exclusive spin-off title built upon the company's proprietary Crystal Tools game engine. It was part of Fabula Nova Crystallis Final Fantasy, a subseries of games linked by a common mythos: while it retains links to the mythos, specific references were removed.

The game was originally directed by Tetsuya Nomura, who also created the story concept and main character designs. Nomura wanted to create a darker Final Fantasy title unsuitable for the main series. The initial development went slowly, and by 2007 the scale of the project generated discussions about rebranding the game as the next main entry in the series. Production on Versus XIII ended in 2012, when it was rebranded as Final Fantasy XV and transferred over to the PlayStation 4 and Xbox One. The PlayStation 3 version was abandoned due to concerns about the platform's shortening life cycle. Its engine was also changed to Luminous Studio, Square Enix's custom-built engine for eighth-generation gaming hardware.

After its change of platforms, the production team headed by Hajime Tabata, whose previous work included Crisis Core: Final Fantasy VII and Final Fantasy Type-0, was brought on board to aid production. Tabata became co-director, and was eventually promoted to sole director after Nomura was transferred to work on other projects within the company. After the transition to eighth-generation hardware, multiple changes were made so that it better suited the new consoles and its new status as a mainline game, including the alteration or removal of some scenes and characters from Versus XIII. Production of the game and the engine happened concurrently. Later in production, multiple other studios were brought in to help with various aspects of the game.

Since its original announcement, release of information became sporadic, leading to video game journalists labeling it as vaporware and eventually to rumors of its cancellation. After its public rebranding in 2013, the silence continued until its appearance at the 2014 Tokyo Game Show, at which point development and progress information was released on a regular basis. A demo for the game, Final Fantasy XV: Episode Duscae, was released in March 2015 with first print copies of Final Fantasy Type-0 HD. Promotion for the title was effectively restarted at the 2015 Gamescom. There were delays in its release due to polishing work and the wish for a simultaneous worldwide release, something no other mainline Final Fantasy title had managed to accomplish. Additional media was also created to help portray the world of XV.

Production

Staff

A one-winged woman in flowing robes rests with her head on her arms. Behind her is a crystal sphere twisted around it by a serpentine creature. She rests near the logo of Final Fantasy XV. The piece is done in a pastel watercolor style that fades from silver to blue to black.
The logo of Final Fantasy XV: designed by Yoshitaka Amano and incorporating the game's themes, the logo survived almost unchanged through the game's development.[1][2]

Final Fantasy XV was originally a spin-off title named Final Fantasy Versus XIII (ファイナルファンタジーヴェルサスXIII Fainaru Fantajī Verusasu Sātīn?), created by Square Enix, directed by Tetsuya Nomura, and produced by Shinji Hashimoto and Yoshinori Kitase. Nomura created the original scenario, designed the main character, and was also the original director and one of the original game designers. The CGI movies were directed by Takeshi Nozue, who had previously worked on Final Fantasy VII: Advent Children. The music was composed by Yoko Shimomura, and the script was written by regular Final Fantasy scenario writer Kazushige Nojima. Tomohiro Hasewaga was art director, the mechanical designer was Takeyuki Takeya, and the event planning director was Jun Akiyama. The image illustration and logo design was done by Yoshitaka Amano.[1][3]

After the game's name and platform change, there were multiple staff reshuffles, though Shimomura, Hashimoto, Hasewaga and Nozue retained their original positions. Nomura became co-director alongside Hajime Tabata, the director of Final Fantasy Type-0, then was moved to other projects and replaced as full director by Tabata. Saori Itamuro became the new scriptwriter, using Nojima's original scenario as a base for the new work.[4][5] Kitase left as co-producer, while Yusuke Naora, Isamu Kamikokuryo, and many artists involved in the development of Type-0 were involved.[6] Several pieces of Amano's original artwork were retained and used in promotion.[7][8] Non-Japanese staff included character designer Roberto Ferrari, game designer Prasert Prasertvithyakarn, and party interaction designer Wan Hazmer.[4][9]

The staff as formed in 2012, not counting later additions, was made up of the combined Final Fantasy XV and Type-0 development teams.[10] By 2014, between 200 and 300 people were working on the game.[11] Along with bringing in staff members from other sections of the company, they also recruited help from other development studios: HexaDrive was brought in to help with engineering the game, XPEC Entertainment helped with the design for the later section of the game and monster design, Shanghai company Plusmile helped with the design of buildings, Avalanche Studios was brought on board to help create the game's airship mechanics, while licensed middleware from Umbra was used to boost the game's graphics.[12][13][14][15]

Development

<templatestyles src="Template:Quote_box/styles.css" />

"The stories from the past entries in the Final Fantasy series are not exactly as I would have done, but that's as it should be because I didn't direct them. My only concern in terms of Versus XIII is that [Final Fantasy] always talks about human emotion and psychologies in a broad way, and I want to go deeper in terms of offering some crude reality in terms of human emotion or human [behavior]. The goal, when a player holds a controller and plays [a role-playing game], is to make them believe in another world – to experience a dream in a fictional world. It will be different in Versus XIII because of the intrusion of the real world, and things that are really happening. There will be less fiction and more reality."

Tetsuya Nomura on the story of Final Fantasy XV, then known under the title Final Fantasy Versus XIII[16]

Final Fantasy Versus XIII was created as part of Fabula Nova Crystallis Final Fantasy, a subseries within the Final Fantasy franchise featuring games linked by a common mythos which included Final Fantasy XIII and Type-0: apart from the mythos, they are completely separate, and each game’s staff are able to interpret the mythos for each game.[17][18] Versus XIII was one of the original titles created for the subseries alongside Final Fantasy XIII, forming the core of the series around which future titles would evolve.[3][17] Nomura intended Versus XIII to be a heavy departure from his lighthearted Kingdom Hearts series.[19] He attributed this move to his "love for extremes" and explained the direction he took as closer to his personal taste and completely different from what producers had requested him to do in the past.[16] Early into development, Nomura said that the concept and thinking behind the game was unfitting for a regular numbered Final Fantasy installment, thus explaining its original status as a spin-off.[20]

Production began in 2006 by the development team responsible for the Kingdom Hearts series as a PlayStation 3 exclusive.[20] There were even plans for the game to have a "unique" support setup for the Sixaxis controller.[21] Versus XIII was defined by Nomura as the dark side of XIII, which was emphasized by the game's title.[22] In 2008, it was reported that development was put on hold so the team could complete Final Fantasy XIII. This information was later clarified as a mistranslation, with the actual situation being that developers from the Versus XIII team were helping with XIII in their spare time, with development on both games going according to their original schedules.[23] By June 2010, Nomura reported that the game’s story, and the character and clothing designs had been completed. By June 2011, the game was reportedly still only in the pre-production phase.[21] Full production on Versus XIII began in September of that year.[24] According to later staff, Versus XIII was only 20-25% complete when the change of name and platform took place, with Tabata saying that the game "never really took shape".[25][26]

Due to the growing scale of the project, talks about changing Versus XIII into the next numbered entry in the series were appearing as early as 2007.[27] When Type-0, originally titled Final Fantasy Agito XIII, was renamed, and the PlayStation 4 and Xbox One were presented to Square Enix in 2011, it was decided to shift the game onto those consoles. For a time, a PlayStation 3 version continued development, but after a title change announcement could not be made in 2012, the shortening lifespan of the console caused concern for the company and team. After some trial and error, the PlayStation 3 was abandoned as lead platform in favor of a DirectX 11-based development structure that allowed for easy porting to the next-generation systems.[5][27] The game was rebranded as Final Fantasy XV and began development in this form in July 2012.[10] At the beginning of development, the new team reviewed the content of Versus XIII and decided what could be sensibly carried over to the new project. While many design elements were retained, some needed to be changed or removed. Tabata's new position as co-director and eventually as director was related to this change.[10][26] Intentions to turn the game into a musical after Nomura had seen the 2012 film adaptation of Les Misérables were vetoed by the higher-ups at Square Enix.[28]

Nomura remained as co-director alongside Tabata so the project could remain as true to the original vision as possible. In 2014, Square Enix then reassigned Nomura to other projects within the company including Kingdom Hearts III, while Tabata took up full directorial duties to bring the project to completion. The separate engine, gameplay, graphics and design sections of the team were also merged into one unit to help with development.[10][29] Development initially followed the pattern of previous high-budget games, but the team eventually realized that such techniques had become dated.[30] During the later part of development, Tabata's main concern was keeping the game on schedule instead of letting the development become delayed by experimentation with the technology. The company also kept the game's budget under strict control, despite the prolonged development.[31] When describing his attitude to development, Tabata described the team set-up as "horizontal", using a non-hierarchical staff structure to help speed up the exchange of information and feedback between departments.[32] Including the initial work on Versus XIII, the game's development spanned approximately ten years from conception to release: despite its origins, Tabata considers Versus XIII and XV to be two separate entities.[31]

Design

Story and characters

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The central theme of the story is "a fantasy based on reality": the setting is based on the real world and the fantasy elements grew out of familiar settings. Realizing this aspect of the game was quite difficult for Nomura before the game's move onto eighth-generation hardware. While the story was similar to other entries, he wanted to create more realistic characters.[33] Nomura wanted to make XV "about man in the real world", including less fantasy elements, describing it as the darkest entry in the series.[19] When Versus XIII became XV, multiple aspects were changed: these included the removal of story sequences and the redesigning of characters.[34][35] The most notable change was the replacement of the female character Stella with Lunafreya.[2][34] When consulted over the proposed changes, Nojima said that he would be content as long as the overall concept remained faithful to the original, giving the team the needed confidence to make the necessary changes.[36][37][38] The concept of reaper-worship in Lucis from the original scenario was toned down, as it would have been a violation of age-rating criteria in some countries; explicit references to those elements were replaced with the general impression of black being a special color.[39]

The game's main theme is "bonds", as represented by the relationships between Noctis and his comrades, and between Noctis and his father Regis.[40] A key narrative element was Noctis' personal journey from prince to king.[41] In contrast to many previous Final Fantasy titles, the playable cast of XV is all-male, although women still play key roles in the story. This was influenced by Nomura's wish for a road movie vibe and experiences from his youth.[42][43] The clothing for characters was designed by Hiromu Takahara, lead designer for Japanese fashion house Roen. He was brought on when Nomura was occupied with other duties including designing the main cast of Final Fantasy XIII: the main reason for his inclusion was the wish to preserve the game's realism by creating designs influenced by Western fashions. Roen's designs were retained during the transition as they were a core part of the initial project.[1][44][45]

World design

When first announced, XV used the mythos of Fabula Nova Crystallis, described by Kitase as "a backdrop and starting point" for the story.[16][46][47] For Versus XIII, Nomura decided to focus more on the world and on realistic human characters.[16][19] The terminology of the mythos, including the concept of l'Cie (magically-imbued warriors burdened with a pre-determined task), was originally present in Versus XIII.[46] A key figure in the mythos, the Goddess Etro, was originally represented in-game in a piece of artwork by Amano and was a key deity worshipped in the game world.[1][48] During the transition process between Versus XIII and XV, the game "disconnected" from the mythos' core framework, existing as a thematic base for the world and story without being overtly expressed.[2][7][30] While the adjustments were being decided upon, it was chosen to keep the mythos as part of XV, as much of the world was built upon it and would lose a lot of its substance if removed entirely. Instead, the team chose to adjust the mythos to fit the game's modern setting. Specific terminology, such as "l'Cie" and "fal'Cie", was removed so the game would retain an individual identity and introduce the concepts in an understandable way.[25] The revised cosmology drew inspiration from Japanese folklore and various Western mythologies.[7]

Shinjuku, Tokyo was the primary inspiration for Insomnia, capital of Lucis.[49][50]

Nomura had wanted to use a present-day setting for a Final Fantasy game ever since this idea had been considered but abandoned during the development of Final Fantasy VII.[17] As such, some of the designs in Final Fantasy XV are based on real-world locations: among them are the districts of Tokyo, the Piazza San Marco and St Mark's Basilica in Venice, the Bahamas, and natural locations such as a cavern in Chiba Prefecture.[12][49][50][51] Insomnia, the Crown City of Lucis, is specifically influenced by the Shinjuku, Tokyo area which houses the headquarters of Square Enix and which Nomura passes through every day. The highway and tunnel seen in the game are almost exact replicas of the Shuto Expressway and a tunnel in the Ginza district, respectively. The team created these by driving down the real-world locations repeatedly during their research.[52][53] The design inspirations for Niflheim ranged from the Roman Empire to pre-Germanic and Germanic civilizations.[45] The game's theme of "fantasy based on reality" was emphasized on multiple levels in the environments, such as the blending of realism and fantasy in Insomnia, and the camping equipment, which was included through a collaboration with Coleman Company.[53][54] Another factor in the original development of set pieces was the design of vast and seamless environments. They were meant to enable, e.g. levels in which the player character was shot at from a great distance, or in which a battle would change scenes between the outside and inside of a building. This corroborated Nomura's intended action-oriented system with more intuitive game controls. He instructed his team to study third-person shooters for reference, "not in simplistic terms, like controls or mechanics, but in the way they create tension and mood and incorporate the action within that".[16] This carried over into XV, with the stated aim being to distance the game structurally from XIII and its sequels, which featured divided zones rather than a large seamless world.[50] The original inspiration behind this approach was the world design of The Legend of Zelda: Ocarina of Time, with later inspirations being modern Western triple-A open world titles.[55] The environments are divided into three different segments, with separate teams working on each: the world map, locations in the game world, and dungeons. The dungeons were designed to be beautiful, frightening, and memorable.[56] Specific pieces of concept art were created to represent different regions and aesthetic concepts: a single building design was used to capture the essence of Altissia's Venice-inspired atmosphere, while older car designs when compared to the party's vehicle Regalia reflected the lack of human advancement outside Lucis.[57]

The game's summoned monsters, referred to in-game as both "Astrals" and "Archaeans" (Summoned Beasts (召喚獣 Shoukanjuu?) in Japanese), were designed to play integral parts in the story and world as opposed to being simple monsters to be called into battle. They were intelligent beings that Noctis needed to forge a pact with rather than simply commanding them. Due to their key role in the story, the staff chose traditional Final Fantasy summons (such as Leviathan and Titan) instead of creating ones unique to the game.[2][25][45] For the monster designs, Tabata told art director Tomohiro Hasegawa that their goal was a sense of realism equivalent to National Geographic. With this concept in mind, the first monster designed was the Behemoth. For mystical enemies, the team went towards "throwback" designs, using popular enemy designs from the series' history.[2] The monster designs were drawn from various sources. A difficult monster to design was the Catoblepas, one of the larger monsters: particular attention to detail was given to the head and legs, as they were the most visible areas to players. The Mesmerize, which was raised as an example of the balance between fantasy and realism, was designed with a horse-like body along with a horn inspired by the appendages on seahorses. The Goblins and Naga were not given an original design, instead being taken directly from their original artwork by Amano for earlier Final Fantasy games and inserted into the game in as realistic a form as possible. The Numb Blade was designed to resemble the traditional dress style of a ronin, with both the clothing and fabric created using descriptions from books and images of antique samurai clothing and swords.[58][59] The game's mounts, recurring galliform birds called Chocobos, were designed so players would feel affection for them. The most challenging part of the design was adding fantastic flourishes while keeping it from being garish.[58] Another recurring Final Fantasy creature, the Moogle, was originally present in Versus XIII, and was going to be similar in design to its Type-0 incarnation.[60] Initially it was decided that Moogles would be dropped from XV;[38] they were retained after getting a favorable result from a Twitter poll in November 2015. Due to the game being close to completion, it was a token inclusion that would not impact the main development.[61]

Music

A 2007 photograph of Yoko Shimomura, composer for Final Fantasy XV.

The music was composed by Shimomura, who was most widely known for her work on the Kingdom Hearts series. It was her very first time composing for the Final Fantasy series, so she took a more tentative approach than her Kingdom Hearts projects.[62] Shimomura was involved with the project when XV was still titled Versus XIII. In 2010, Shimomura was still forming a framework for the game's music, ensuring that the music fitted the game without it solidifying into an image that seemed wrong.[63] Shimomura worked on between 80 and 90% of the music: the rest was variations on her work and other themes created by others involved in the soundtrack. Its music was designed to encompass themes of "friendship" and "filial bonds".[64] During development, Shimomura discussed her music with the game's other developers so it fitted the game's world, along with reading the story.[62] The original commercial demo Episode Duscae featured music both from earlier trailers and new tracks.[65] The music for Episode Duscae was performed by the Video Game Orchestra, a North American orchestra specializing in video game music whose first Final Fantasy project had been Lightning Returns: Final Fantasy XIII.[66] The game's main theme, "Somnus Nemoris", was sung by Andrea L. Hopkins, had lyrics written by Nomura, which were translated and adapted into Latin by Taro Yamashita and Kazuhiro Komiya.[67] The tracks "Somnus Nemoris" and "Omnis Lacrima" from the game were included in compilation albums of Shimomura's music, and the former was released as downloadable content for Theatrhythm Final Fantasy.[67][68][69]

The game's theme song is a cover of Ben E. King's "Stand by Me", performed by Florence and the Machine and sung by the band's leader Florence Welch. It was used in all versions of the game.[70][71] The cover used a full orchestra, including brass, strings and timpani. Welch stated that she wanted to make a "mystical" contribution to the game. She also commented that "Stand by Me" was a difficult song to improve upon.[70] The cover also featured the "Prelude to Final Fantasy" as a backing track.[71] When deciding upon an artist who had their own unique "world" which would fit with the setting of XV, Florence and the Machine was one of many bands Square Enix looked at.[72] In the context of XV, "Stand by Me" was not intended as a love song, but rather as a message or prayer of gratitude from Noctis to all who had supported him on his journey, including Lunafreya, his father Regis and his three companions.[73] Theme songs have traditionally been performed by Japanese singers, with the exception of XIII which had the Leona Lewis single "My Hands" substituted for "Kimi ga Iru Kara" in its English release.[72][74]

Graphics

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

During its initial development, Versus XIII used Crystal Tools, a proprietary game engine created by Square Enix for seventh-generation gaming hardware that would be used throughout the company for multiple games, including XIII and Final Fantasy XIV.[75] Later, Tabata described the Crystal Tools hardware as an extension of the technology of the previous gaming generation.[26] During 2010, Nomura revealed that the team were using physical calculations to determine weather and cloud behavior.[76] By 2011, Nomura announced that the game was no longer using Crystal Tools, and instead used a specially-designed proprietary gameplay engine combined by lighting technology from Luminous Studio, an engine built for eighth-generation gaming hardware. The focus on realism influenced the decision to incorporate the more advanced lighting technology, while the specially-designed engine had a limited area of use.[77] The planned scale of the open world increased so much that the older technology eventually became obsolete as it was holding the developers back. The need to create new technology to cope with these problems further added to the difficulties.[78]

The original plan was to have interactive real-time event scenes. This was decided upon for two reasons: Nomura felt that regular storytelling cutscenes in other games interrupt the gameplay and that many players skip them for this reason. Furthermore, the development frame could be shortened as there was no need to create high-polygon character models from scratch to use only in cutscenes.[79] However, seamless transitions of these events into the gameplay were hard to achieve and instead increased the time that had to be invested by the team.[80] While CGI cutscenes created by dedicated Square Enix subsidiary Visual Works were present throughout its lifetime, there were far fewer than originally planned in the final game. The team instead relied on real-time cutscenes as much as possible, except for scenes whose scale would not have been shown properly using real-time graphics. The transition to next-generation hardware enabled the team to better realize their original vision for the game, as conveyed in the game's original reveal trailer.[81] Visual Works also worked closely with the team during development of 3D modelling systems, due to their previous experiences with such technology in cutscene development.[82]

To solve the issues faced by XV, the team used a similar development approach to Ubisoft: they created an approximate game system that they could build on and edit in real-time. Graphics and animation were developed first, followed by a cinematics editor and a system to manage events during transitions between cutscenes and gameplay. This latter element was what allowed the developers to create what would become the game's final version.[78] During the transition from Versus XIII to XV and the optimization of Luminous Studio for game development, the team created a conceptual environment using a prototype engine environment called "Ebony". After the initial reveal, the team ran into difficulties with the new hardware, prompting them to contact HexaDrive due to their experience with high-spec gaming hardware.[10][83] After the full shift onto next-gen, multiple elements were influenced by the new Luminous technology: for example, the in-game cutscene camera was optimized to work similarly to the one used in pre-rendered movies, and more environmental and gameplay elements could be included, such as more destructible environments and the player character's warping to faraway spots on the game maps.[5] It also enabled Nomura to start experimenting with higher facial detail for enemies such as behemoths.[84] During production, Tabata and the new development staff used experience from a failed attempt to develop an eighth-generation console sequel to Type-0 when handling the new hardware.[85] While using Luminous Studio for games other than XV was considered during production, the engine's technology manager Julien Merceron advised against it until it has been proven and released in a finished form.[86]

The game's real-time graphics used 5000 polygons per-frame, bringing its visual quality close to modern CGI cutscenes and to a level that would have been impossible for the previous generation's hardware. The game's native resolution was 1920 x 1080 pixels (1080p), with a 30fps frame rate: this was defined as being native to the game as opposed to upscaled games from the previous generation. For polygon models, the combined number of visible and occluded polygons was estimated as being 5,000,000. This number was approximately five times the amount of equivalent detail from last-generation games. Models used over 600 character bones: 150 bones were created for the face, 300 for the hair, and 150 for the body. A bone-based physical simulation technology was applied so that clothing would react to the body's movements.[87] To help maximize the realism of the characters, their hair was first created by a hairstylist using a mannequin's wig, then rendered into the game using the technology of Luminous Studio. The same technique was used for Agni's Philosophy, the engine's 2012 demo. The polygon count for character hair was estimated as 20,000, the same number used in an entire character in last-generation games.[87][88] All of these were achievable due to the fact that the eight-generation console hardware had approximately sixteen times the amount of storage available in the previous generation.[87] Character movements were created using motion capture technology: the animators' movements were first captured while they wore special suits, then their actions were adjusted in the team's computer to perfect them and make minor additions like finger movements. These actions were then implemented in the game environment for the intended characters.[89]

Gameplay

Versus XIII used an action-based combat system based primarily on the Kingdom Hearts battle system.[46] Gameplay elements from third-person shooters were also to have been incorporated.[90] Character movement was designed to be fast-paced. During earlier gameplay trailers, the pace of gameplay was deliberately slowed down so viewers could have a better view of events. In addition to Noctis, his companions were also controllable, each harnessing unique weapons and all being able to enter and control mechs and airships. Noctis was the only character with access to all weapon types within the game (including swords, axes, guns, lances and others), with the current selection of weapons leading to different combos. Group attacks could not be manually triggered, but party members would team up automatically for a "super attack". In addition, attacks could be chained together by players switching between characters during battle. Magic was available to all characters, but only when Noctis was a part of the party, a consideration that was closely tied to the story. A job system was in place, but it was exclusive to enemy units, with those present including dragoons and summoners. Environments outside cities also featured a day-night cycle and roaming enemies, with different enemy monsters appearing at different times of day.[46][91] Several initial concepts for the game had to be abandoned; a planned first-person view and the lack of a heads-up display were scrapped because these ideas were deemed incompatible with the style of the Final Fantasy series.[5] An overhead camera view was also considered for the open field areas, but it was decided against so the player would remain immersed.[91] When the final Versus XIII trailer was released, the HUD was a mixture of finalized and temporary elements.[46]

For XV, the battle system was dubbed the Active Cross Battle system. Noctis was made the only player-controlled character, with the others being relegated to AI-governed command functions similar to the Gambit system from Final Fantasy XII. The team did experiment with a multi-character battle system, but eventually decided that it presented too many development difficulties.[10] Noctis' weapons were to be arranged in a deck, and contextually activated in combat.[10] Later, this was changed so that weapon-switching could be done freely during battle, with special attacks using the standard weapons unless others were in place.[92] Instead of a multi-button combo system, combat became focused on single-button combat tied to timed attacks and contextually-activated special abilities, in addition to co-op attacks triggered with other members of the party.[10][51][93] One ability that was carried over from Versus XIII to XV was Noctis's Limit Break "Armiger Arsenal", where he summoned multiple weapons into battle to attack and defend; this was initially seen in the original trailer for XV, and later in both the demo and the final game.[10][94] Noctis was to have been the only character in the world of XV to wield magic, but as this would not have worked from a gameplay perspective, the team created a story-related pretext that allowed other characters to wield magic.[95] After the demo's release, the Cross-Link system was improved and other systems were put into place. Polishing work on the game is set to continue up until the final version is released.[96] The navigation was described after its 2014 re-reveal as "open world": Tabata later clarified that while character progression was driven by the story, the various areas within the world could be freely explored by players. He also wished for a fusion of gameplay and story similar to The Last of Us.[41] Based on feedback from the game's first commercial demo, adjustable difficulty settings were added in the form of players changing "battle modes" to alter the speed and complexity of battles.[97] The inclusion of an airship function into the party's vehicle came from Tabata's wish to keep the party in the Regalia while simulating the experience of landing an aircraft.[55] The team experimented with enabling compatibility with virtual reality headsets, but this proved impractical as players would likely be wearing them for hours at a time due to the game's size.[98]

Artificial intelligence

The lead designer for the game's artificial intelligence (AI) was Yoichiro Miyake, who was one of the core team members for the game's engine. Miyake, a designer noted for his work on AI, had an initial concept of creating an AI that would learn and memorize new actions, creating a smooth flow through the various steps it needed to take to make a smoother and more advanced experience. At the start of its development, the developers used the two standard "classic" designs for AIs for reference: behavior-based, which revolved around adaptation and decision making, and state-based, which made decisions based on the environment. For XV, it was decided to create an advanced hybrid of these basic behavioral AI functions. Due to the way Luminous Studio's staff was structured, the team first needed to develop an easy-to-understand tool for managing and developing the AI. This tool was dubbed the "Luminous AI Graph", which represented the multi-layered construction of an AI. The amount of effort put into the AI was directly inspired by experiences of developing games for the previous console generation: the emphasis had been put on graphics, causing the AI and other gameplay-related elements to suffer. Between the release of its commercial demo and the full release, the AI underwent further refinement.[99]

The AI functions were divided into three different categories: "meta", which governed the environment and in-game progression; "character", which was devoted to the guest and non-playable characters (NPCs); and "navigation", which determined the best route and pattern for characters and other moving elements such as enemies to travel. The tasks assigned to the meta-AI were so numerous and large that it needed to be divided into separate interconnected elements, which included implementing a hierarchical structure for task management, transitioning and the merger of functions to create an intelligent system, and the exchange of various elements with specific localities. For the character-AI, a major point was the coordination between the AI and character animations when responding to different situations. Different levels and styles of AI were created for different groups of non-playable characters within XV's world, from the main party members to NPCs around the world. To ensure the navigation-AI worked properly for enemies and monsters, a system dubbed the "Point Query System" (PQS) was created, which could direct and steer them in a realistic manner while avoiding collisions with objects in the environment or other moving elements. A PQS was created for each enemy type, and made small changes to their behaviors easier to implement.[99]

Business

Announcement

A screenshot from the original trailer for Final Fantasy Versus XIII, showing Noctis displaying his powers.

Versus XIII was originally announced at the 2006 Electronic Entertainment Expo (E3) through a CGI trailer.[100] The trailer, which showed Noctis advancing on a group of enemy soldiers, was created by Visual Works as a representation of what the development team were aiming for.[81] The trailer also featured a quote from William Shakespeare's Hamlet: "[There] is nothing either good or bad, but thinking makes it so." This quote was intended to evoke the atmosphere Nomura was aiming for.[101] After its initial announcement, the title was absent from multiple gaming events for several successive years, although a video showing an extended version of the reveal trailer was released in 2007 at a fan event. Two trailers were released in 2008, including in-game footage at the 2008 Tokyo Game Show (TGS). Footage of navigation was shown at TGS the following year in a closed theater.[21] Its appearance at E3 2010 was apparently prevented due to multiple technical issues.[76] Its final appearance as Versus XIII was at a Square Enix Press Conference in January 2011, appearing alongside other video games then in production.[21] Because of its sporadic appearances in the public eye and its absence after the 2011 event, industry commentators labeled Final Fantasy XV as vaporware while it was still known as Versus XIII.[102][103][104] In June 2012, it was rumored that the game had been cancelled, which was swiftly refuted by Square Enix's then-CEO Yoichi Wada.[21] After that, further rumors emerged claiming that it had either been quietly cancelled, or renamed and shifted to another platform during development.[105][106]

Its name and platform change were officially announced at E3 2013, with further trailers showcasing the game concept released later.[83][107][108] The game's next official appearance was made at TGS 2014, with the announcement of its commercial demo, and a tech demo to show off the game's engine.[109] After its reappearance, regular livestreamed shows called "Active Time Reports" (ATR) were broadcast, giving updates to the game and responses to fan questions. According to Tabata, the ATRs were created to help fans left confused by the game's change of platform and title, along with establishing a two-way communication with the fanbase.[25] After its appearance at the 2014 Paris Games Week, Tabata announced that XV's release window was "roughly decided", with the company recruiting new staff to work on the game's master build.[110] While it did not show at E3 2015, it did appear at that year's Gamescom, which Tabata said was the beginning of its official marketing campaign leading up to further announcements.[111] The game's minimal showing at the event caused a negative reaction from fans, with Tabata stating that Square Enix underestimated the importance of the event.[45] Between May and November 2015, the publicity was deliberately kept low-key so staff could focus on completing the pre-beta version of the game. Once done, XV became playable in its entirety, enabling developers to get a full view of the product for the final stages of development and testing.[61][112] Production on the beta version and progression to the debugging phase began in 2016.[41] During 2015, official forums were created to allow the developers to receive direct feedback from fans. Starting from February 12, the Japanese forums were discontinued and replaced with a developer's blog. Their stated reason was to offer a more accessible medium for both feedback and developer updates.[113]

Additional media

Due to the scale of XV's world and story, there was a chance that it would need multiple games to tell the entire story. To avoid this, the team instead moved to create additional media surrounding XV, turning it into a multimedia project: while the main game could be enjoyed on its own, the other media could be used as introductions to the setting for newcomers.[72] This project is being referred by Square Enix to as the "Final Fantasy XV Universe".[114] Additionally, a five-episode anime titled Brotherhood: Final Fantasy XV, was produced by Square Enix and A-1 Pictures and is being released through the game's official YouTube channel. Each ten-minute episode details the backstory of Noctis from his childhood to the game's opening, along with the backstories of his companions. The first and last episodes of the anime tie in with the Platinum Demo.[72][115] The anime is intended to give people a view into Noctis' mind that would have appeared incongruous within the context of a video game.[116] The first episode released on 30 March 2016.[115]

A 110-minute CGI feature film, Kingsglaive: Final Fantasy XV, is set for release prior to the game in July 2016.[117] While similar in appearance to Advent Children, Kingsglaive had a different goal behind its development: while Advent Children was made for dedicated fans of Final Fantasy VII, Kingsglaive was made as an introduction for newcomers to the world of XV, along with conveying some of Regis' backstory.[116][118][119] The film features voice performances from multiple well-known actors: Sean Bean portrays Regis, Lena Headey voices Lunafreya, while Aaron Paul plays Nyx Ulric, a member of Regis' Kingsglaive guard and the film's main protagonist.[8][118] Kingsglaive is being produced by Tabata, directed by Nozue, and written by Takashi Hasegawa. The music will be composed by John R. Graham, while the main theme will be composed by Shimomura. The main staff are the same as those who developed Advent Children in 2005.[118][119] Kingsglaive began development in 2013.[118] In addition to the staff of Advent Children, Western companies in gaming and film production are involved: Digic Pictures, who had worked on the graphics for the Assassin's Creed series; and Image Engine, who had worked on multiple films including Jurassic World and the television series Game of Thrones.[116] Nyx is an original character exclusive to Kingsglaive, designed as a repeatable character that would bring the game's lore and setting to a more comprehensible level.[72] A custom redesign of the Audi R8, acting as Regis' state vehicle, was featured in the film as part of a collaboration with its manufacturers.[120]

Release and localization

The game's year of release was officially announced at the 2015 Pax Prime event, with its release date set to be revealed at a special event the following year.[121] Another announcement from that time was that Tabata was aiming for a simultaneous worldwide release, which would have been a first for the Final Fantasy series.[122] This was later clarified by Tabata at the 2016 Taipei Game Show: Square Enix was aiming to release the game within the same time period across the world, although there would be minor variations depending on regions.[123] The special March event, called "Uncovered: Final Fantasy XV", took place on March 30 at the Shrine Auditorium in Los Angeles, California, and hosted by internet celebrities Greg Miller and Tim Gettys. The event was livestreamed worldwide.[124] Free limited tickets for the event were made available on February 5 for North American residents. By the next day, all tickets had been claimed.[124][125] Its worldwide release date, September 30, 2016, was announced on the first day of the event.[8]

In addition to the standard release, Day One, Deluxe, and Ultimate Collector's Editions were announced. The former will contain a copy of XV, an exclusive "Masamune" sword, and platform-specific elements such as Xbox Live avatars and PS4 themes. The Deluxe Edition will also include a copy of Kingsglaive on Blu-Ray, a steelbook case featuring Amano's official artwork, and promotional content in the form of an additional outfit for Noctis, and a recolor of their vehicle. The latter edition will include the content of the Deluxe Edition, alongside a Blu-Ray release of Brotherhood, a special soundtrack, a hardcover artbook, further promotional content in the form of in-game items, and a Play Arts Kai figurine of Noctis. Preorders opened on March 30, and the Ultimate Collector's Edition was limited to a 30,000 unit print run.[120] A further 10,000 copies of the Japanese Ultimate Collector's Edition were produced due to increased demand, alongside further copies for North America and Europe.[117][126][127] The limited quantity was due to the difficulties producing Noctis' figurine. No further additional shipments were created.[127] To promote the game, a mobile app titled Justice Monsters V was developed for release in 2016: based on an arcade mini-game from XV, it used gameplay similar to Monster Strike series gameplay.[116][128]

Sequels to Final Fantasy XV were hinted at with the line "A World of the Versus Epic" in the E3 2013 trailer. Nomura explained that the game had a self-contained climax and that it was the first part of an intended continued epic. He said that Square Enix was considering using online elements and developing shorter stand-alone titles to keep players interested and to avoid long waiting times for them.[129] This was interpreted as a move of the company towards a digitally distributed episodic format for possible sequels.[130] Nomura later clarified at the Japan Expo 2013 that no plans for sequels had been finalized.[131] Later, Tabata stated in interviews that it would be released as a single complete experience, and that no sequel was planned.[93][132] In addition, there were no plans for multiple endings or a cliffhanger ending, with Tabata citing XIII as a video game narrative style they were trying not to emulate.[123]

The English localization of XV was led by Dan Inoue.[133] One of the aspects of the localization was using different accents to show the characters coming from different regions of the world: a cited example was Ignis, who spoke with a British accent while the other main characters spoke with an American accent.[134] One of the early issues, which drew public attention with the release of Episode Duscae, was Noctis' English voice actor. In Episode Duscae, his voice was pitched rather low, making the character seem older and less energetic than his Japanese counterpart. This was explained as being due to tight scheduling removing the opportunity for Tabata to catch the issue and re-record before it was time for release. After Episode Duscae, the voice work was redone to better convey Noctis' personality.[135] Different issues raised later included Ignis' localized lines, which changed aspects of the character interaction, and the alteration of Cindy's name from the original "Cidney".[133] In an interview with Famitsu during Gamescom, Tabata revealed that the main reason for the delays in XV's release were related to the game's localization and debugging, as the team wanted to bring the game out in the west close to its Japanese release.[30] In addition to being released with French and German dubs and text translation for those respective regions, it was also localized for Latin America with Latin American Spanish and Brazilian Portuguese text: this was the first time a Final Fantasy title was localized into these languages.[136]

Demos

During its TGS 2014 presentation, the real-time demonstration footage was dubbed Final Fantasy XV: The Overture, which demonstrated the graphic capabilities in Luminous Studio and the effect of environmental changes on gameplay.[109] While it was intended as a one-off presentation, the team said they were considering creating a second demo for release in Japan based on The Overture.[51] A public international demo for the game was also created, titled Final Fantasy XV: Episode Duscae.[137] The idea behind Episode Duscae was to give players a personal look at the game due to its long absence from the public eye, as well as demonstrate its gameplay and the fact that it was being actively developed. It was named after one of the regions in the game.[11] The demo is set during the opening segment of XV, where the party temporarily lose their car and must gather funds for its repair by taking on jobs in the region. Gameplay and main story elements were tailored for a demo experience.[94][137][138] One of the features left out was the ability for players to rent Chocobos, while the battle system was a slimmed-down version of what was planned for the final game, using the originally-planned preset weapon deck feature. The character Cindy was also included.[51][92][94][139] A summon with a simplified method of acquirement was also put into the game: originally intended to be Titan, it was replaced with Ramuh due to the former being a key character in the story.[45][95]

After TGS 2014, where Episode Duscae was first announced, Tabata and the team adjusted the gameplay experience based on fan feedback. The original was a large area of the worldmap that players could explore using the car.[139] While the ability to drive the party's car was originally included, it was later cut as Tabata feared that the feature would be too new for older fans of the series, who might have mistaken XV for "a driving game." The team decided to focus on the characters and environment.[140] The demo includes English and Japanese audio for all regions.[141] The demo released in all regions alongside the physical and digital releases of Final Fantasy Type-0 HD. The physical version was exclusive to day-one editions of Type-0 HD, while the digital version was valid for two months after purchase. The code had to be redeemed within one year of purchase.[94][142][143] While players can save their progress in the demo, save data cannot be carried over to the main game. Despite this, the team announced its intention to create a bonus for those who purchased the demo.[94] A patch titled Episode Duscae 2.0 was released in June 2015, which included enhancements for the camera and controls, fixes for bugs, and adjustments to gameplay.[135][144] The demo ran on Version 1.5 of the Luminous Studio engine, while the final game was planned to run on Version 2.0.[51]

A new free tech demo, Platinum Demo: Final Fantasy XV released on March 30.[145] Birthed from the initial announced wish to develop a second tech demo, Platinum Demo was completed in two months using completed assets from the main game.[116] First announced in January 2016, it was designed to showcase the game's graphics and physics, along with elements of its final combat system.[14][145] Set in a dream world after Noctis is gravely wounded, it follows Noctis' journey back to consciousness, guided by a creature called Carbuncle that protects Noctis. Players who complete the demo are given access to the Carbuncle summon in-game.[145] According to Tabata, Platinum Demo serves a dual purpose: it both introduces players to the gameplay mechanics, and gives them an insight into Noctis' young life and his relationship with his father. It was originally intended to be a less emotive experience, but was instead made a story-driven experience to better introduce players to the game's world.[116]

References

  1. 1.0 1.1 1.2 1.3 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 2.3 2.4 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 8.2 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 10.2 10.3 10.4 10.5 10.6 10.7 10.8 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 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. 16.0 16.1 16.2 16.3 16.4 Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 17.2 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 19.2 Lua error in package.lua at line 80: module 'strict' not found. Translation
  20. 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 21.2 21.3 21.4 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. 25.0 25.1 25.2 25.3 Lua error in package.lua at line 80: module 'strict' not found.
  26. 26.0 26.1 26.2 Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 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. 34.0 34.1 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. Translation
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. 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. 41.0 41.1 41.2 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. Translation
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. 45.0 45.1 45.2 45.3 45.4 Lua error in package.lua at line 80: module 'strict' not found.
  46. 46.0 46.1 46.2 46.3 46.4 Lua error in package.lua at line 80: module 'strict' not found.
  47. 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. Translation
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. 50.0 50.1 50.2 Lua error in package.lua at line 80: module 'strict' not found.
  51. 51.0 51.1 51.2 51.3 51.4 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. 53.0 53.1 Lua error in package.lua at line 80: module 'strict' not found. Transcript in French
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. 55.0 55.1 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. 61.0 61.1 Lua error in package.lua at line 80: module 'strict' not found.
  62. 62.0 62.1 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. 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 Lua error in package.lua at line 80: module 'strict' not found.
  68. 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. 70.0 70.1 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. 72.0 72.1 72.2 72.3 72.4 Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. 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. Translation
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. 78.0 78.1 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. 81.0 81.1 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. Transcript in French
  83. 83.0 83.1 Lua error in package.lua at line 80: module 'strict' not found.
  84. 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. 87.0 87.1 87.2 Lua error in package.lua at line 80: module 'strict' not found.
  88. 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. Lua error in package.lua at line 80: module 'strict' not found.
  91. 91.0 91.1 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. 93.0 93.1 Lua error in package.lua at line 80: module 'strict' not found.
  94. 94.0 94.1 94.2 94.3 94.4 Lua error in package.lua at line 80: module 'strict' not found.
  95. 95.0 95.1 Lua error in package.lua at line 80: module 'strict' not found.
  96. 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. Lua error in package.lua at line 80: module 'strict' not found.
  99. 99.0 99.1 Lua error in package.lua at line 80: module 'strict' not found.
  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. 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. 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. 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 Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. 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. 115.0 115.1 Lua error in package.lua at line 80: module 'strict' not found.
  116. 116.0 116.1 116.2 116.3 116.4 116.5 Lua error in package.lua at line 80: module 'strict' not found.
  117. 117.0 117.1 Lua error in package.lua at line 80: module 'strict' not found.
  118. 118.0 118.1 118.2 118.3 Lua error in package.lua at line 80: module 'strict' not found.
  119. 119.0 119.1 Lua error in package.lua at line 80: module 'strict' not found.
  120. 120.0 120.1 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. 123.0 123.1 Lua error in package.lua at line 80: module 'strict' not found.
  124. 124.0 124.1 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. 127.0 127.1 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. 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. 133.0 133.1 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. 135.0 135.1 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. 137.0 137.1 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. 139.0 139.1 Lua error in package.lua at line 80: module 'strict' not found.
  140. Lua error in package.lua at line 80: module 'strict' not found.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. 145.0 145.1 145.2 Lua error in package.lua at line 80: module 'strict' not found.

External links