Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Kingdom Hearts III

From CartoonWiki

Template:Short description Template:Pp-vandalism Template:Use mdy dates Template:Infobox video game Template:Nihongo foot is a 2019 action role-playing game developed and published by Square Enix for the PlayStation 4, Xbox One, Windows, and Nintendo Switch. It is the twelfth installment in the Kingdom Hearts series, and serves as a conclusion of the "Dark Seeker Saga" story arc that began with the original game. Set after the events of Kingdom Hearts 3D: Dream Drop Distance, returning protagonist Sora is joined by Donald Duck, Goofy, King Mickey, and Riku in their search for seven guardians of light as they attempt to thwart Xehanort's plan to bring about a second Keyblade War. Their journey has them cross paths with characters and visit worlds based on different Disney and Pixar intellectual properties.

Concepts for Kingdom Hearts III began as early as 2005 after the release of Kingdom Hearts II in Japan, with the game's development not being officially announced until 2013, following years of rumors and speculation. The game features recurring gameplay elements from the series, while expanding parties to five characters total, introducing new "Attraction Flow" attacks that incorporate various Disney Parks attractions, and including minigames inspired by classic Mickey Mouse cartoons in the style of 1980s LCD games.

Kingdom Hearts III was released worldwide in January 2019 and received generally positive reviews from critics. Critics praised its visuals, soundtrack, art style, gameplay, and variety of combat options, while reception towards its plot and presentation was more mixed. It sold over five million copies within its first week of release, becoming both the fastest-selling and best-selling game in the series' history in North America.[1] A downloadable content expansion of the game titled Template:Nihongo foot was released on January 23, 2020, for PlayStation 4,[2] and on February 25, 2020, for Xbox One.[3] A version of the game bundled with the DLC titled as Kingdom Hearts III + Re Mind was released on Windows via Epic Games Store and Steam on March 30, 2021, and June 13, 2024, respectively.[4][5] The same version was released on the Nintendo Switch via cloud streaming on February 10, 2022.[6]

Template:TOClimit

Gameplay

Gameplay in Kingdom Hearts III is similar to its predecessors, with hack and slash combat,[7] which director Tetsuya Nomura stated would be along the lines of the system seen in Kingdom Hearts II, with an evolution similar to what was seen from Kingdom Hearts to Kingdom Hearts II, and closely tied to the gameplay in Kingdom Hearts 3D: Dream Drop Distance.[8][9][10] He also revealed that the handheld games of the series were where he could experiment with the combat mechanics, and that some of the well-received additions could appear in Kingdom Hearts III.[8][9] Nomura noted that new gameplay elements are the "skeleton" of the game, saying development starts with a "fun element" for gameplay or system to then build the story and concept around.[11] Additionally, the development team "always want to try something new", taking previously introduced mechanics and making small "tweak[s]" to them so they are customized for Kingdom Hearts III.[12]

Sora returns as the main playable character, once again joined in the party by Donald Duck and Goofy,[13] with the ability to have two additional characters join the party for a total of five-player parties. This is an increase from previous main entries in the series, where players were limited to two additional party members at any given time along with Sora.[14] Certain parts of the game have Riku and Aqua as playable characters.[15] Describing the gameplay, Nomura called the action "pretty frantic", as well as "really flashy and exciting. The enemy AI is a lot more intricate, too, and I think the gameplay will reflect that new dynamic balance."[16] Sora can perform magic, with a new, powerful tier of each spell available to him, similar to what Aqua has available to her in Kingdom Hearts 0.2: Birth by Sleep – A Fragmentary Passage.[17] Magic performs differently in underwater sections of the game, with Kingdom Hearts III introducing a new spell, Water.[18] Team-up attacks are also featured, which combine Sora and various party members into one attack.[19][20] Players can equip various abilities for Sora and his party members, with the system to do so "an evolution of sorts" from the system used in Kingdom Hearts II.[21] Character summons make a return from previous entries, this time known as "Links", where an additional character joins the battle to assist the player with specialized attacks.[22]

File:Kingdom Hearts III Summons Gameplay.jpg
Sora performing an "Attraction Flow" attack that utilizes Disney Parks attractions, a new feature for Kingdom Hearts III

Sora faces Heartless, Nobodies, and Unversed in the game,[23] with new variants of these enemy types appearing.[19] In addition to these traditional "smaller" enemies, the player faces giant bosses, which give "Sora greater freedom of movement and room to experiment with attacks—including the new theme-park-ride summon attacks,"[11] known as "Attraction Flow".[24] These attacks are inspired by the Disney Parks attractions Mad Tea Party, Big Thunder Mountain Railroad, Buzz Lightyear Astro Blasters,[22] and Grizzly River Run,[25] and generic pirate ship and carousel attractions;[22][26] these attacks draw visual inspiration from Disney Parks' Main Street Electrical Parade.[22] Sora also has the ability to jump on certain enemies, such as ones shaped like a vehicle.[16] Regarding traversal, Nomura noted the new mechanic, called "Athletic Flow" in Japanese, was refined from the Flowmotion mechanic from Dream Drop Distance, which players felt was "a little too free... and it was kind of hard to control on their end."[27] "Athletic Flow" allows the player to utilize the environment to access previously unreachable areas.[28] Co-director Tai Yasue stated this mechanic was created "to try something new" and "radically change the gameplay" for the Hercules world, which led to its use in the other worlds. As a result, each world was able to have "more height, scale and sense of discovery."[29]

Situation Commands also return from previous entries,[30] which can trigger the Keyblade transformations. Nomura revealed that Keyblade transformations were conceived as early as the development of Kingdom Hearts II: Final Mix and would be similar to Aqua's ability in Kingdom Hearts Birth by Sleep, saying, "Each Keyblade transformation is unlocked by clearing all missions in one of [the game's] worlds, and each individual world offers its own unique Keyblade transformation."[11][31] He further elaborated stating there were two forms each Keyblade can take, with "multiple layers in terms of transforming" starting with one transformation and achieving the second after "successfully connect[ing] your combos".[28] The Keyblade transformations active the various "Formchanges"[23]–Power, Guard,[32][33] Magic,[33] and Speed–[33] and change Sora's outfit,[33] similarly to the "Drive Form" mechanic in Kingdom Hearts II.[32] Various Keyblades are linked to each form;[33] for example, the Toy Story world Keyblade actives Power Form for Sora, with the Keyblade's transformations changing into a hammer and then into a drill.[34] There is also "Second Form", which changes Sora's battle skills rather than transform the Keyblade.[35] Unlike previous games in the series, players are able to quickly switch between different Keyblades seamlessly during gameplay rather than from the game's equipment menu,[36] and each Keyblade can be leveled up to increase their abilities.[7] Shotlocks also return, which use a focus meter that can target and lock on to individual enemies with the attack depending on which Keyblade is equipped.[23]

Each world offers a specific gameplay element,[37] such as first-person shooter "Gigas" mechs in the Toy Story world,[22] downhill sledding in the Frozen world,[18] and naval, underwater, and aerial combat in the Pirates of the Caribbean world,[38] which also features numerous smaller islands at sea which can be explored.[18] The Gummi Ship also returns as a means of travel between the different worlds of the game.[12] The mechanic has been split into two phases: exploration, which has been likened to being more open-world without a fixed travel route as in previous games;[39][40] and combat, which has increased its scale from previous games, with more enemies present.[39] Gummi Ship customization also returns,[21] with more options available than in previous Kingdom Hearts games.[29]

Various mini-games playable throughout Kingdom Hearts III,[41] including a cooking-themed game featuring Remy from Ratatouille,[41] and a music game in the Tangled world.[42] Additionally, the "Classic Kingdom" features over 20 games presented in the style of 1980s LCD games such as Game & Watch,[43][29] while the 100 Acre Wood world features puzzle games.[44] Members of the development team suggested each type of mini-game featured, with Nomura working on the "Classic Kingdom".[42] Kingdom Hearts III also has a "Memory Archive" feature, which has several short films explaining the basic story elements of the series from the previous games.[29]

Story

Template:Kingdom Hearts chronology

Setting

The story opens with the final scenes of Kingdom Hearts 0.2: Birth by Sleep – A Fragmentary Passage, and serves as a conclusion of the "Dark Seeker/Xehanort Saga" that occurs in most preceding games.[16][45] Most of the worlds featured in the game inspired by Disney properties are new to the series,[46][47] including the Kingdom of Corona (based on Tangled),[48][49] Arendelle (Frozen),[50][51] San Fransokyo (Big Hero 6),[52][53] and the Pixar-based worlds Toy Box (Toy Story) and Monstropolis (Monsters, Inc.).[54][55][39][56] Two new original worlds created specifically for the game also appear: a limbo for dying hearts called the "Final World";[57] and Scala ad Caelum, a "seat of power" for past Keyblade wielders, where the game's final battle takes place.[58][15] Returning Disney worlds include tutorial stage Olympus (Hercules),[53][35][7] the Caribbean (Pirates of the Caribbean),[38][51] and the 100 Acre Wood (Winnie the Pooh),[44] while original worlds include Twilight Town,[59] the Dark World,[60] the Land of Departure,[61] and the Keyblade Graveyard.[62] Worlds such as Yen Sid's Mysterious Tower,[63] Radiant Garden,[64] Disney Castle,[65] and the Destiny Islands[66] appear exclusively via cutscenes. The "Classic Kingdom" mini-games are inspired by classic Walt Disney Productions Mickey Mouse cartoons, including Giantland, The Karnival Kid, Musical Farmer, The Barnyard Battle,[43] The Klondike Kid, and Mickey's Mechanical Man.[67]

The Toy Story, Monsters, Inc., and Big Hero 6 worlds feature original stories, with the former set between the events of Toy Story 2 and Toy Story 3, and the latter two set after the events of their respective films.[68][52] This is different from previous worlds in the series, which have often loosely followed plot lines from the films on which they were based,[69] including the Tangled, Frozen, and Pirates of the Caribbean worlds.[42] On the amount of worlds featured in the game, Nomura noted the development team focused on creating "rich gameplay in an individual world... designed so players can take their time and enjoy the gameplay that's available" opposed to having "multiple different little worlds".[69]

Characters

The main protagonist and playable character of the game is Sora,[47] a 15-year-old boy who uses a key-shaped weapon called the Keyblade to battle the forces of darkness. Sora is accompanied by Donald Duck and Goofy,[47] the royal magician and knight captain of Disney Castle, respectively. The three are supported by other Keyblade wielders, several of whom they must rescue in preparation for their final confrontation with Master Xehanort,[47] the series' primary antagonist, as "guardians of light"; Mickey Mouse,[47] an experienced Keyblade Master who is Donald and Goofy's king; Riku,[47] a Master and Sora's best friend; Kairi,[27] another of Sora's friends, a Princess of Heart and a novice wielder; Aqua, a Master trapped in the realm of darkness; Ventus, a comatose boy whose heart has merged with Sora's; Terra,[70] a young man who was possessed by Xehanort; Axel/Lea,[27] a former member of Organization XIII and fellow novice with Kairi; Roxas,[71] Sora's Nobody, who merged his existence with Sora's; and Xion, a replica member of the Organization whose existence was erased from her friends' memories.

Organization XIII returns as the game's antagonists, led by Master Xehanort, with different members from previous games such as past incarnations of himself, as established in Dream Drop Distance.[34] Kingdom Hearts III also introduces a new original character named Yozora, who features prominently in an in-universe video game commercial in the Toy Story world, and later in the secret ending. As with previous games in the series, a multitude of Disney characters appear in worlds based on their respective films and properties. Disney characters who serve as members of Sora's party include the returning Hercules and Jack Sparrow;[13][72] new to the series are Woody and Buzz Lightyear,[54] Sulley and Mike Wazowski,[39] Rapunzel and Flynn Rider,[73] Marshmallow,[74] and Baymax.[75] Characters that appear as summon "Links" for Sora include Dream Eaters such as the "Meow Wow" from Dream Drop Distance, Wreck-It Ralph from the film of the same name,[22] Simba from The Lion King,[76] Ariel from The Little Mermaid,[73] and Stitch from Lilo & Stitch.[65] Remy from Ratatouille (who is referred to in-game by his nickname of "Little Chef") appears in one of the game's mini-games at the bistro.[41]

Most Final Fantasy characters were excluded from the initial game release as Tetsuya Nomura felt that they would detract from the story,[77] and that the Kingdom Hearts characters needed less support than they did before;[78] the Moogle character returns as the item shopkeeper,[23] while the Re Mind DLC sees previous Final Fantasy characters appear.[79]

Plot

Yen Sid begins preparing seven Keyblade wielders as guardians of light to counteract Master Xehanort's plan of forging the χ-blade. Sora, accompanied by Donald Duck and Goofy, resumes his travels across other worlds to regain his "power of waking", the ability to restore lost hearts, which he lost after nearly being possessed by Xehanort.Template:Efn Sora's group is antagonized by members of Organization XIII, who target the seven Princesses of Heart as substitutes for the guardians while seeking a new member for their thirteenth and final spot. Meanwhile, Riku and King Mickey search the realm of darkness to retrieve Aqua, while Kairi and Lea train as Keyblade wielders.

Sora and Riku are contacted throughout their travels by former Organization member Ienzo, who uncovers research notes from Ansem the Wise revealing that the hearts of Roxas and two others—later identified as Ventus and Xion—are dormant within Sora's heart. Sora suggests implanting Roxas's heart in an artificial Replica body made by Vexen, one of the Organization's reserves, after learning that the Organization's time-traveling members are using the same method to exist in the present. Meanwhile, the Heartless Ansem abducts Ansem the Wise from the realm of darkness, but Vexen rescues Ansem the Wise. Revealing himself as a double agent, Vexen enlists fellow reserve Demyx to deliver a spare Replica for Roxas to inhabit.

Riku and Mickey are attacked by Aqua, who has become corrupted by the dark realm's influence. Discovering Master Eraqus's Keyblade on the Destiny Islands, Sora uses it to enter the realm of darkness and aid his friends, defeating and restoring Aqua. Aqua then travels to awaken Ventus at Castle Oblivion, which she transforms back into the Land of Departure. When she is attacked by Vanitas, Sora rediscovers his power of waking and revives Ventus, who fends Vanitas off.

The seven guardians arrive at the Keyblade Graveyard to battle the Organization, only to be consumed by a swarm of Heartless summoned by the possessed Terra. Sustained by Kairi's power, Sora awakens in a limbo realm called the Final World, where a Chirithy guides him in restoring his fragmented body. He then uses the power of waking to revive his friends and travel back in time to the moment before their defeat, which is averted by the appearance of Terra's lingering will. In the guardians' ensuing battle against the Organization, Terra regains control of his body and reunites with Aqua and Ventus, while Roxas and Xion—the latter of whom was duplicated as the Organization's final member—regain their hearts from Sora and reunite with Lea.

After the other Organization members are defeated, Xehanort provokes Sora into attacking him by destroying Kairi's body, allowing Xehanort to acquire the χ-blade and unlock Kingdom Hearts. Sora, Donald, and Goofy hinder Xehanort by transporting him to his boyhood home of Scala ad Caelum, where they eventually defeat him. In Xehanort's dying moments, Eraqus's spirit emerges from Terra and convinces Xehanort to surrender the χ-blade. After sealing Kingdom Hearts, Sora decides to use the power of waking to save Kairi, despite being warned about the grave consequences of doing so. Afterwards, Sora's allies gathers at the Destiny Islands, where a revived Kairi stays beside Sora before he fades away.

In a post-credits scene, Organization member Xigbar summons the Foretellers and reveals himself to be Luxu, their fellow Keyblade apprentice. In a flashback to their youth, Eraqus and Xehanort—having finished a chess game reminiscent of Sora's final battle with Xehanort—begin a new game that predicts a battle with Luxu and the Foretellers.

Kingdom Hearts III Re Mind

Kingdom Hearts III Re Mind is a downloadable expansion set during and after the climax of the game. It is divided into three separate scenarios—"Re Mind", the "Limitcut Episode", and the "Secret Episode"—which are unlocked in sequential order after the original game is cleared.

The titular scenario depicts Sora's rescue of Kairi during the game's ending scenes. Assuming an incorporeal form, Sora travels back in time to the battle between the guardians of light and the Organization, passing through the guardians' hearts to reach Kairi. Despite his initial failure, Sora finds and assembles fragments of Kairi's heart in Scala ad Caelum before his past self's final battle with Xehanort, restoring Kairi. After revisiting the Final World to invite Chirithy to the realm of light, Sora visits his friends' worlds with Kairi before his disappearance.

The "Limitcut Episode" is set one year after Sora's disappearance; his allies have since led an ongoing search for him, while Kairi has entered stasis after volunteering as Ansem the Wise's test subject to help Sora. During a visit to Radiant Garden, Riku analyzes digital copies of Sora and the Organization's members programmed into Cid Highwind's computer, hoping to uncover clues to Sora's whereabouts through their battles. After the analysis proves inconclusive, Riku is approached by the Fairy Godmother to meet with Yen Sid, who has determined a method of finding Sora through Riku and two others.Template:Efn

The "Secret Episode" focuses on Sora, who has become trapped in the Final World since his disappearance. There, Sora encounters Yozora, who claims to have been requested to save Sora, but questions Sora's identity and battles him atop a skyscraper in a modern-day metropolis.Template:Efn If Sora wins, Yozora fades away before Sora returns to the Final World; if Sora loses, Yozora crystallizes him and goes to the Final World instead. Afterward, regardless of who wins, Yozora awakens in a car while a closing narration ensues in his and Sora's voices, with the battle's victor saying, "None of this makes sense to me."

Development

After Square Enix finished development of Kingdom Hearts II: Final Mix, Tetsuya Nomura was approached by Disney, who expressed interest in a sequel. In regard to a possible release of Kingdom Hearts III, Nomura said "We have various ideas, but we're not at the point where we can say that." He added that due to the development of Final Fantasy XV—titled Final Fantasy Versus XIII at the time— which was being developed by the Kingdom Hearts II team, it was "physically impossible at the present. I feel that it's not the right time to talk about the future of Kingdom Hearts."[80] In response to questions about the secret film in Final Mix, Nomura noted that it was of a "new series" in Kingdom Hearts rather than Kingdom Hearts III. When asked about Kingdom Hearts III, Nomura noted that fans and partners alike were interested in its release, and would work to "realize it" as soon as possible.[81] In the Kingdom Hearts Birth by Sleep Ultimania guide book, Nomura announced three upcoming titles, one of which was Kingdom Hearts III. However, Final Fantasy XV was still his primary focus, preventing him from starting production on Kingdom Hearts III.[82] He later noted that Kingdom Hearts III would not see a release until after 2012, due to his continuing work on Final Fantasy XV, regardless of the tenth anniversary of the series occurring in that year.[83] The Nintendo 3DS video game Kingdom Hearts 3D: Dream Drop Distance was announced to connect to Kingdom Hearts III, both in terms of gameplay system and story.[84]

Sony announced Kingdom Hearts III for the PlayStation 4 with a teaser trailer at its E3 2013 event in June 2013.[85] Square Enix later confirmed the game's cross-platform release for the Xbox One as a port of the PlayStation 4 version.[86][87] Though some development and concepts for the game began during the seventh generation of video game consoles, it was always intended that the game would release during the eighth generation.[88]Template:Rp Unlike Kingdom Hearts and Kingdom Hearts II, which were developed by Square Enix's Product Development Division 1 team, Kingdom Hearts III was developed by Square Enix's 1st Production Department, who developed Birth by Sleep, Dream Drop Distance, and worked on the HD 1.5 Remix collection and Square Enix's Business Division 3.[89][90] Rie Nishi serves as the game's producer.[91] The game began using the in-house Luminous Studio engine to develop the game after some initial development tests had been done using Unreal Engine 3.[88]Template:Rp

Directly after E3 2013, Nomura claimed that Kingdom Hearts III was announced early, based on where the game stood in development. He continued by saying, planning alongside Final Fantasy XVTemplate:-".[92] Kingdom Hearts III is not intended to be the final game in the series,[45] and serves as the final chapter of the "Dark Seeker/Xehanort" saga.[16][45] Series producer Shinji Hashimoto stated in September 2013 that since Nomura was director of both Kingdom Hearts III and Final Fantasy XV, it was expected that there would be a significant gap between the release of the two, "as [they] want each game to be perfect in terms of quality." Hashimoto also reiterated Nomura's statements about the game's announcement at E3 2013, as "the company thought it was about time it addressed speculation about the long-awaited conclusion to the trilogy."[93] A short teaser for the game appeared at the end of the Kingdom Hearts HD 2.5 Remix trailer at E3 2014. Yasue revealed that the sequence seen in the teaser was the opening scene for the game. He added that it was created by Nomura, who had "a real clear picture of [what] the starting sequence" should be, and that the text seen and heard was going to "be a real integral part of the story".[94] As Nomura stopped working on Final Fantasy XV, focusing his attention on other projects, including Kingdom Hearts III.[95] Nomura revealed that the game had switched to using Epic Games' Unreal Engine 4, due to a "variety of reasons", with the development team having the full support of Epic.[96]

In January 2015, Yasue revealed that working on HD 2.5 Remix simultaneously allowed the developers to learn all the best qualities from the series to aid in creating III. Additionally, he stated the Kingdom Hearts team was sharing knowledge with the Final Fantasy XV team to expand the game and get the most out of the PlayStation 4 and Xbox One.[97] A gameplay trailer was released during the Kingdom Hearts Orchestra World Tour in Los Angeles in mid-June 2017.[13][98] The possibility of a Nintendo Switch version of the game might be created, but wanted to focus on the development and promise of completing the PlayStation 4 and Xbox One versions was thought.[99] Nomura noted the long development was due to internal Square Enix corporate decisions, such as changing to the Unreal Engine 4 about a year into the game's development, which led to "extensive delays" and "a bit of time that needed to be rewinded and started over", and "certain timing and resources challenges within Square Enix", despite submitting and getting approved a plan for when more personal resources would be needed on the project. Regarding downloadable content (DLC) for the game, Nomura stated that "nothing is set in stone" regarding it, but he told the development team to "be prepared to be able to accommodate for something like that. We can't Template:Em develop a system where we're accommodating for downloadable content. So it's not confirming or denying either way, but just so that the development team will be prepared".[100] He would later add that he wanted to have some sort of additional content for the game, but nothing in depth had been discussed. Nomura was open to potentially adding customizable accessories, as was able to be done in Kingdom Hearts 0.2: Birth by Sleep – A Fragmentary Passage with Aqua, as that feature does not return for Kingdom Hearts III.[101] Nomura also preferred DLC to expand or change the game over releasing a Final Mix version as had been done with some past entries in the series.[42]

At D23 Japan 2018, Square Enix revealed the game was being developed in three sections, with approximately three worlds in each section. At that time, the worlds in the first section were said to be 90 percent complete and development of the middle section at around 60 percent. No update was given on the final section of the game, though Nomura stated its contents were "something he's always wanted to do and put into Kingdom Hearts, ever since the days of working on Final Fantasy... It is bound to surprise everyone."[39] In April 2018, the "Classic Kingdom" mini-games were revealed for the game, while also announcing the games would be playable in the mobile game Kingdom Hearts Union χ.[43] A selection of the mini-games were made available in Union χ in its "χ3" mode added in September 2018, which enables players to obtain the "Starlight" Keyblade in Kingdom Hearts III by completing certain objectives.[102] By June 2018, the secret film for the game had been created. Additionally, Nomura revealed the development team was concerned with the size of the game and if it would fit on the game disc. To help with this, the team was turning some of the cutscenes into pre-rendered films to help reduce load times.[42] Nomura had requested the use of Oswald the Lucky Rabbit in the game, which he called his favorite Disney character, but was denied such a proposal.[103][104]

At E3 2018, Nomura also provided an update to the development of the Big Hero 6 world, revealing all the gameplay had been created, with the cutscenes still needing to be completed.[51] At X018, a world based on Winnie the Pooh was revealed.[44] Shortly after, it was reported that the character of Winnie the Pooh would be censored in China. This was due to the Chinese government banning any depictions of the character after the character's appearance had been compared to that of Chinese Communist Party general secretary Xi Jinping.[105] To improve the Gummi Ship gameplay, a criticism in previous entries, the development team who created the scrolling shooter 1997 game Einhänder was brought in to handle this portion of the game, along with other programmers and engineers who have worked on driving games.[40] Development of the game was completed by November 20, 2018.[106]

World selection

Nomura revealed the Tangled world was one of the first determined to be in the game, as the development team wanted to include Rapunzel due to her strong personality and her hair, finding it fitting for the gameplay.[24] The Pirates of the Caribbean world was included because Nomura wanted at least one world based on a live-action Disney film, stating that the Caribbean location allowed for "interesting" gameplay opportunities.[107] He also chose to have the world be based on the third film, At World's End (2007), over other films in the series, particularly Pirates of the Caribbean: Dead Man's Chest, because Dead Man's Chest is "setup" for At World's End and the game would "have to end [the story] in the middle as well".[38] The world also mimics the color palette from the film, being "deliberately washed-out", with the sky, for example being more grey-blue over "[t]he typical fantasy blue".[88]Template:Rp

Since the release of Kingdom Hearts II in 2005, The Walt Disney Company acquired Pixar, Marvel Entertainment, and Lucasfilm. When asked in 2013 if any of these properties would appear in Kingdom Hearts III, Nomura said he contacts Disney after he hears of an acquisition, though he noted that "Disney's pretty honest [on the possibility of an inclusion]. If the situation is really difficult, they'll say, it's really difficult. If it's impossible, they'll say it's impossible."[108] He later stated that even though the Disney Company had acquired these properties, Disney Interactive Studios may not necessarily have the ability to license the content due to existing deals, such as Disney's deal with Electronic Arts for Star Wars games.[109] Yasue added that they were "looking at all of Disney, the new ones as well" when choosing worlds for the game, including worlds potentially based on Marvel Comics and Star Wars properties. He expanded, saying, each world needed originally to stand out.[110]

Nomura had hoped to include a world based on Toy Story since Kingdom Hearts II, saying he felt "Sora really fit in and matched well with that world" and being "able to execute that into the game is something I'm really excited for."[69] Nomura felt Pixar worlds were extremely important to include in Kingdom Hearts, specifically one based on the film Toy Story, and stated he considered not making Kingdom Hearts III if he could not get the rights to use Pixar properties from Disney. This world was the first submitted to Pixar for approval shortly after the completion of Kingdom Hearts II, with Nomura presenting them a general outline of the story he had planned for the world. It would take Pixar "several years" to approve the story and character designs, as Nomura and Square Enix were negotiating through Disney, not with Pixar directly.[88]Template:Rp

Nomura noted the approval process for each world was more difficult than with earlier games, because many of the worlds are based on some of Disney's more contemporary films, making it harder to take creative license with the worlds.[58] He explained, "Previous to Kingdom Hearts III, I think these companies kind of saw it more as like, secondary rights permissions. They saw it more as a product, like you would a branded toy or something."[88]Template:Rp Continuing, Nomura noted, "Because we are working with more recent titles, the staff who were on the original project are the ones we go to for approvals. For instance, Frozen. The staff is still there and they work with us on Frozen. Because we go directly to the creators, they have the most passion for their titles."[58]

Design

In June 2013, Nomura discussed the updated visuals, saying that the development team tried to return the character's texture to the original "paintbrush art from Disney productions". The resulting visuals were referred to as the Kingdom Shader. Nomura felt it might not seems a massive change, it was still a notable evolution of previous visuals.[16] Nomura also revealed that Sora is the same proportions as in previous games; however, they "muted the volume on his hair—it's not Template:Em wild." Regarding updating Sora's look from his Kingdom Hearts II design, Nomura noted that outfit's popularity, but felt the desire to change it since the game is the first numbered sequel since IITemplate:'s release. He added that the basis for the resulting design is a mix between Sora's costumes for Kingdom Hearts II and Dream Drop Distance, one that is "a lot more sleek and sporty" in order to make him look more acrobatic.[24] Riku and King Mickey also received updated outfits.[60] When asked about Noctis Lucis Caelum' similarities with Yozora, Nomura stated that while he noted there are several similarities between the two characters, they hold no connections.[111] Roxas and Xion, popular characters from Kingdom Hearts II and other games in the series, were originally not planned to appear, but positive response to their characters led to their inclusion.[112]

Speaking on the designs of the worlds, Nomura said the updated graphical capabilities allowed the development team "to depict the world[s] of the original film[s] as close to [their] original form as possible" after previously creating worlds to be "a stylized Kingdom Hearts world".[113] Disney shared basic polygon information with the development team, who ultimately had to remake all of the characters, animations, and environments from scratch.[88]Template:Rp[114] Members of Pixar assisted with the creation of the worlds based on Toy Story and Monsters, Inc.,[69][54][115] and for the Pixar characters in the game, Pixar shared their actual character models with Square Enix and had the original character designers consult on the game "to make sure everything looked as true to the films as we could make it."[55] The design team would talk weekly with Disney, sharing their assets to receive feedback, with Disney sometimes asking "for minute alterations such as insisting a character show less teeth, having their eyelids move differently or their line of sight adjusted". The line of sight notes, which came from Pixar, "were instrumental in raising the general quality of the animation throughout" according to the development team.[88]Template:Rp[114]

Supporting characters can explore an environment on their own if Sora idles momentarily, sometimes triggering additional cutscene moments. For example, Rapunzel responds if an Aero spell is cast on a group of dandelions. Speaking specifically to interactions such as this with Rapunzel, Yasue said "finding and activating these moments builds trust with" her and can lead "to additional combat scenarios and treasure opportunities".[18]

Audio

Music

Template:Multiple image Template:Main The game's soundtrack was composed by long-time series composer, Yoko Shimomura,[91] and features additional contributions from Takeharu Ishimoto and Tsuyoshi Sekito.[116] Shimomura felt pressure over working in the title since it was Square's first numbered game after several years. She wanted fans to look forward to the game, believing its content would appeal to the audience.[117] The soundtrack includes a highly altered version of the track "Dearly Beloved" in order to fit the ending of the "Seeker of Darkness Arc".[118] The soundtrack was released on November 11, 2022,[119] the album of which contains 8 CDs. The soundtrack that plays during Xemnas, Ansem and Xehanort, "Forza Finale" ("last force" in Italian) was composed by Yasunori Nishiki, of whom Shimomura was a fan.Script error: No such module "Unsubst". Due to the game being released worldwide, the team decided to localise titles in multiple languages.[120]

As with the first two main Kingdom Hearts games, it has a theme song written and performed by Hikaru Utada, titled "Chikai" in Japanese and "Don't Think Twice" in English.[121] It serves as the game's ending theme.[122] An additional theme, titled "Face My Fears" by Skrillex, Poo Bear, and Utada, is used for the opening of the game.[123] Skrillex, a fan of the series, originally intended to remix "Don't Think Twice", before creating "Face My Fears", which also has a Japanese version. Both "Face My Fears" and "Don't Think Twice" were released on January 18, 2019.[124][122]

Utada requested that the producer Skrillex produce a remix of the song "Chikai" for Kingdom Hearts III, since it was known that he was a fan of the game. He proposed to instead make a completely new song. Utada agreed to collaborate with him and songwriter Poo Bear to write the song.[125]

Voice cast

Haley Joel Osment returned to voice the lead character Sora in the English cast.

Kingdom Hearts III only features English and Japanese voice acting and lip syncing, despite previous entries in the series having dubbing in other languages. Nomura noted that the development team wanted to prioritize a global simultaneous release for the game, and given the time and resources for recording the dialogue, this would not have been possible with additional language recordings.[126] Though the game has both English and Japanese voice acting, it does not have the ability to switch between them, as the development team found this feature difficult to properly support.[42] A version of the game with Chinese subtitles will also be released.[127] Kingdom Hearts III has full voice acting in optional dialogue moments outside of cut scenes, which is a first for the series.[128]

In the Japanese voice cast, Akio Otsuka, the voice actor for Xehanort's Heartless "Ansem", replaced his late father Chikao Ohtsuka, who played the villain Master Xehanort. Miyu Irino returned to voice Sora and Vanitas as he faced more issues during recordings of the game. After finishing the game, Irino wondered if he might properly portray Sora in sequels due to his age gap. Mamoru Miyano also returned to voice Riku and his replica persona with similar difficulties to his more drastic age gap. Miyano reflected that Riku had to act more positive, especially when interacting with his replica, since he understood his mindset. Risa Uchida provided the voice for Kairi and Xion again, noting that Kairi had a more mature perspective such as when she befriends Axel; in contrast, Uchida felt that Xion was more relatable.[129] Olaf received a new Japanese voice actor in an updated patch following the arrest of his original Japanese voice actor, Pierre Taki.[130]

Haley Joel Osment returned to voice Sora in the English version. Due to Sora's lack of growth across the franchise, Osment faced the challenge of properly giving him the tone of a teenager. In retrospect, Osment found the idea of ending Kingdom Hearts III as an emotional moment as, while the series would not end with this installment, the narrative would give proper closure to the story started by the antagonist Xehanort.[131] Tony Anselmo and Bill Farmer – who portrayed Donald Duck and Goofy in English[132][133] were overjoyed with their multiple redesigns when the characters traveled to other worlds.[134] Other actors include David Gallagher as Riku/Riku Replica, Bret Iwan as Mickey Mouse, and Alyson Stoner as Kairi and Xion.[135] Jason Dohring, Willa Holland, Jesse McCartney and Mark Hamill reprise their roles as Terra, Aqua, Ventus, and Master Eraqus from Kingdom Hearts: Birth by Sleep, respectively; McCartney also reprises his role as Roxas. Dylan Sprouse appears in the Re Mind downloadable content as the voice of new character Yozora, and was overjoyed with his character due to him liking Japanese role-playing heroes.[136] Rutger Hauer voices Master Xehanort, replacing Leonard Nimoy after his death in 2015; following Hauer's death in 2019, Christopher Lloyd portrayed the character in the Re Mind downloadable content.[137]

Release

Kingdom Hearts III was released for the PlayStation 4 and Xbox One on January 25, 2019, in Japan and other Asian countries,[138][127][42] and on January 29, 2019, elsewhere.[139] In July 2017, at D23, it was announced that the game would release in 2018.[54] Almost a year later, at an additional performance of the Kingdom Hearts Orchestra World Tour in Los Angeles, the game's North American release date was revealed to be January 29, 2019.[139] Nomura spoke to moving the game's release date outside of 2018, stating the development team had been told the original release date they had considered was not "good timing in the year" to release the game, especially considering "differences in holiday lengths and how stores behave in different regions". In addition, Square Enix requested the game be released as simultaneously as possible between Japan and the rest of the world, and not wanting to move up the release at the expense of development, resulted in the January 2019 date being chosen.[51] The game's epilogue was planned to be added to the game on January 26 for Japan and January 30 elsewhere, while the secret ending content was planned to be added worldwide on January 31, 2019.[140] This was done in order to help prevent them from leaking beforehand, since Nomura called them "the biggest spoilers" in the game.[141]

A deluxe edition of the game features an art book, steelbook case, and collectible pin. Another edition, exclusive to the Square Enix store, includes Bring Arts figures of Sora, Donald, and Goofy in their Toy Box outfits in addition to the deluxe edition contents.[142] A limited edition Kingdom Hearts III-themed PlayStation 4 Pro and DualShock 4 controller was released on January 29, 2019, exclusive to GameStop and EB Games in North America.[143]

Following the release of the game, Nomura confirmed the development of post-launch downloadable content, saying that the development team's current "top priority is on making DLC for KH3" with the intention of releasing a single content package of DLC in lieu of a separate "Final Mix" version like previous titles in the series.[144] A DLC episode entitled Re Mind was officially announced in June 2019, with a slated release on January 23, 2020, for the PlayStation 4 and February 25, 2020, for the Xbox One.[2][3]

The game was released with all downloadable content included for Windows on March 30, 2021, via the Epic Games Store.[145] It was later released on Steam after three years of exclusivity on June 13, 2024.[5]

A cloud-streamed version of the game for Nintendo Switch including the Re Mind DLC was announced in October 2021 to coincide with Sora's inclusion as a playable character in the Switch-exclusive crossover fighting game Super Smash Bros. Ultimate and the 20th anniversary of the Kingdom Hearts franchise, and was released on the Nintendo eShop alongside cloud versions of the 1.5+2.5 HD Remix and 2.8: Final Chapter Prologue collections on February 10, 2022.[146][147][148]

Reception

Critical response

Template:Video game reviews Kingdom Hearts III received an 83/100, indicating "generally favourable reviews", according to video game review aggregator Metacritic.[149][150] Game Informer called Kingdom Hearts III "the series at its strongest", a game that "provide[d] satisfying answers to the biggest question marks" of the series, praising the combat and gameplay, but panning the sidequests, Gummi Ship mode and general "repetitiveness" of the final worlds.[151] Writing for IGN, Jonathon Dornbush praised the technical advancements for the game and combat. GamesRadar was generally positive, but also panned the Gummi Ship game mode for its "blandness". VideoGamer panned it in general, finding it too simplistic and repetitive.[152]

Critical response to the narrative was mixed, with both RPGamer and GamesRadar finding the visuals of the Pirates of the Caribbean world awkward to watch due to Square's attempt to emulate realism.[153][154] Despite panning the narrative as "incomprehensible", VideoGamer.com found the Toy Story worlds and Pixar in general the most entertaining.[152] GameRevolution enjoyed the Disney worlds, complimenting both their narratives and visuals.[155] The more complex subplots was also generally praised, but DenOfGeek claimed it was "confusing".[156][157][151] The absence of Final Fantasy characters in the initial release of the game, apart from Moogles, were criticized by fans.[158][159][151] GameRevolution and EGM found that the Organization XIII as final stage villains made the narrative accessible to most gamers and praised the voice acting, especially Haley Joel Osment as Sora, and Richard Epcar and Paul St. Peter as Xehanort's alter egos.[157][154][160][153]

Sora's characterization was praised for retaining likable heroic traits,[161][158] though Polygon felt Sora's characterization was "off", lacking change.[162] RPGamer said Sora's hero's journey is mostly shown in the climax.[154] His fate in the ending was the subject of analysis due to his apparent death after saving Kairi to the point GameRevolution stated that Kingdom Hearts III did not give the audience the happy ending they expected despite ending Xehanort's arc.[163][164][165] The ending was generally praised for its bittersweet character endings, although GameSpot claimed that "heavy-handed storytelling... inevitably culminates in battles that are impressive set-pieces but feel cheap and spammy to play" with the story wrapping up "in an incredibly unfulfilling way."[166]

Sales

In its debut week, the game topped the EMEAA (Europe, Middle East, Africa, Asia) charts, in terms of both unit sales and gross revenue.[167] In Japan, the game debuted at the top of the Media Create charts with 610,077 retail sales, above Resident Evil 2.[168][169] It also debuted at the top of the UK charts, with Kingdom Hearts III more than doubling the launch week sales of Kingdom Hearts II.[170]

In North America, it was the top-selling game in January 2019,[171] and the third top-selling game in February 2019 (behind new releases Anthem and Jump Force).[172] Kingdom Hearts III is the overall top-selling game in North America during the first two months of 2019, exceeding the sales of Kingdom Hearts II by over 80% during the same time span.[173]

On February 4, 2019, Square Enix announced that more than 5 million copies were sold, becoming the fastest-selling title in the franchise,[174] less than two weeks after its release.[167]

On April 11, 2022, Kingdom Hearts III was revealed to have reached a total of 6.7 million units as of September 2021 surpassing Kingdom Hearts total of 6 million to become the current best selling title in the series.[175]

Accolades

Kingdom Hearts III was nominated by IGN for the Best Game of E3 2018, Best PlayStation 4 Game of E3 2018, Best Xbox One Game of E3 2018, and Best Action Game of E3 2018.[176] It also won the Momocon E3 Choice 2018 Game Award, and was nominated for Unreal's E3 awards.[177]

Year Award Category Result Ref(s).
2018 Game Critics Awards Best RPG Template:Won [178]
Gamescom Best Role-Playing Game Template:Nom [179]
Golden Joystick Awards Most Wanted Game Template:Nom [180]
Gamers' Choice Awards Most Anticipated Game Template:Nom [181]
2019 Japan Game Awards Award for Excellence Template:Won [182]
Golden Joystick Awards Best Visual Design Template:Nom [183]
Titanium Awards Best RPG Template:Nom [184]
Best Soundtrack (Yoko Shimomura) Template:Nom
The Game Awards 2019 Best Score/Music Template:Nom [185]
Best RPG Template:Nom
2020 New York Game Awards Statue of Liberty Award for Best World Template:Nom [186]
47th Annie Awards Best Character Animation - Video Game Template:Nom [187]
23rd Annual D.I.C.E. Awards Role-Playing Game of the Year Template:Nom [188]
NAVGTR Awards Game, Franchise Family Template:Nom [189][190]
Original Dramatic Score, Franchise Template:Won
Song Collection Template:Nom
Song, Original or Adapted ("Don't Think Twice") Template:Nom
SXSW Gaming Awards Excellence in Animation Template:Won [191][192]
Famitsu Dengeki Game Awards 2019 Best Music Template:Nom [193]

Re Mind

Template:Video game reviews The DLC received "mixed" responses based on the review site Metacritic.[194] IGN criticized the new boss characters were too difficult to defeat as there are few ways to level up.[195] GameSpot and GameInformer called it a director's cut, with the former praising the inclusion of Riku, Aqua and Kairi as playable characters, but criticizing how the main fighting area, the Keyblade Graveyard, had poor design in contrast to other worlds previously seen in the franchise.[196][197] JXV said that the high difficulty of the boss fights the DLC offers was Square's response to gamers' criticism in regards to the easy difficulty of the actual game as well as the return of quick time events from the previous game, Kingdom Hearts II.[198] Destructoid liked the inclusion of new playable characters and how the new bosses seem to be a response to the easy difficulty.[199] Comic Book Resources regarded Data Xehanort and Yozora as the most challenging bosses in the entire game.[200]

In regards to the narrative, GameInformer found it disappointing as, while the game allows the player to explore a new area and see more Final Fantasy characters, they are not properly followed. Still, they felt the new cutscenes helped to improve the game's final act, making the story more enjoyable.[197] Destructoid enjoyed the new cutscenes that expand on the game's final battle between Sora's group and Xehanort's forces, especially because Kairi is given more screentime and plays a more pivotal role in the outcome than in the original game. Unlike GameInformer, Destructoid praised the new boss characters as fighting them provided the reviewer more fun.[199] IGN felt that the narrative was hard to follow as the game ends on a more open nature than the original game.[195] GameSpot was more critical to the story, labeling it as "filler" and that it lacks the Disney and Pixar worlds that made the game enjoyable.[196]

Notes

Template:Notelist

References

Template:Reflist

External links

Template:Wikiquote

Template:Tetsuya Nomura Template:Kingdom Hearts series Template:Navboxes Template:Portal bar

  1. Cite error: Invalid <ref> tag; no text was provided for refs named March2019NPD
  2. 2.0 2.1 Cite error: Invalid <ref> tag; no text was provided for refs named ReMindRevealTrailer
  3. 3.0 3.1 Template:Cite web
  4. Template:Cite web
  5. 5.0 5.1 Template:Cite web
  6. Template:Cite web
  7. 7.0 7.1 7.2 Cite error: Invalid <ref> tag; no text was provided for refs named GeekJul2018
  8. 8.0 8.1 Cite error: Invalid <ref> tag; no text was provided for refs named GamezoneJune2013
  9. 9.0 9.1 Cite error: Invalid <ref> tag; no text was provided for refs named SquareEnixPresentsE32013
  10. Cite error: Invalid <ref> tag; no text was provided for refs named LATimesJul2013
  11. 11.0 11.1 11.2 Cite error: Invalid <ref> tag; no text was provided for refs named E32015GameSpot
  12. 12.0 12.1 Cite error: Invalid <ref> tag; no text was provided for refs named GummiShip
  13. 13.0 13.1 13.2 Cite error: Invalid <ref> tag; no text was provided for refs named EurogamerE32017
  14. Cite error: Invalid <ref> tag; no text was provided for refs named D232017IGNParties
  15. 15.0 15.1 Cite error: Invalid <ref> tag; no text was provided for refs named FinalBattleTrailerBreakdown
  16. 16.0 16.1 16.2 16.3 16.4 Template:Cite web
  17. Cite error: Invalid <ref> tag; no text was provided for refs named MagicTiers
  18. 18.0 18.1 18.2 18.3 Cite error: Invalid <ref> tag; no text was provided for refs named IGN3WorldPreview
  19. 19.0 19.1 Cite error: Invalid <ref> tag; no text was provided for refs named E32015GI
  20. Cite error: Invalid <ref> tag; no text was provided for refs named GameSpotMay2018Event
  21. 21.0 21.1 Cite error: Invalid <ref> tag; no text was provided for refs named IGNE320186Things
  22. 22.0 22.1 22.2 22.3 22.4 22.5 Cite error: Invalid <ref> tag; no text was provided for refs named PolygonMay2018Event
  23. 23.0 23.1 23.2 23.3 Cite error: Invalid <ref> tag; no text was provided for refs named USGamerReview
  24. 24.0 24.1 24.2 Cite error: Invalid <ref> tag; no text was provided for refs named SEPE32015
  25. Cite error: Invalid <ref> tag; no text was provided for refs named IGNMay2018Event
  26. Cite error: Invalid <ref> tag; no text was provided for refs named ReleaseDateNerdist
  27. 27.0 27.1 27.2 Cite error: Invalid <ref> tag; no text was provided for refs named IGN8Things
  28. 28.0 28.1 Cite error: Invalid <ref> tag; no text was provided for refs named NomuraKeybladeTransformations
  29. 29.0 29.1 29.2 29.3 Cite error: Invalid <ref> tag; no text was provided for refs named YasueNewsweek
  30. Cite error: Invalid <ref> tag; no text was provided for refs named SituationCommands
  31. Cite error: Invalid <ref> tag; no text was provided for refs named KotakuJun2013
  32. 32.0 32.1 Cite error: Invalid <ref> tag; no text was provided for refs named DriveForms
  33. 33.0 33.1 33.2 33.3 33.4 Cite error: Invalid <ref> tag; no text was provided for refs named DriveForms2
  34. 34.0 34.1 Cite error: Invalid <ref> tag; no text was provided for refs named D23TrailerAnalysisIGN
  35. 35.0 35.1 Cite error: Invalid <ref> tag; no text was provided for refs named DengekiOnlineJul2017
  36. Cite error: Invalid <ref> tag; no text was provided for refs named PSBlogMay2018Event
  37. Cite error: Invalid <ref> tag; no text was provided for refs named PiratesIGN
  38. 38.0 38.1 38.2 Cite error: Invalid <ref> tag; no text was provided for refs named PiratesVentureBeat
  39. 39.0 39.1 39.2 39.3 39.4 Cite error: Invalid <ref> tag; no text was provided for refs named D232018
  40. 40.0 40.1 Cite error: Invalid <ref> tag; no text was provided for refs named IGNGameplay
  41. 41.0 41.1 41.2 Cite error: Invalid <ref> tag; no text was provided for refs named NomuraGIE32018
  42. 42.0 42.1 42.2 42.3 42.4 42.5 42.6 Cite error: Invalid <ref> tag; no text was provided for refs named FamitsuJun2018
  43. 43.0 43.1 43.2 Cite error: Invalid <ref> tag; no text was provided for refs named ClassicKingdom
  44. 44.0 44.1 44.2 Cite error: Invalid <ref> tag; no text was provided for refs named WinnieThePoohGameSpot
  45. 45.0 45.1 45.2 Cite error: Invalid <ref> tag; no text was provided for refs named ConcludeXehanortSaga
  46. Cite error: Invalid <ref> tag; no text was provided for refs named GematsuJune2015
  47. 47.0 47.1 47.2 47.3 47.4 47.5 Cite error: Invalid <ref> tag; no text was provided for refs named Press Release
  48. Cite error: Invalid <ref> tag; no text was provided for refs named E32015Gameplay
  49. Cite error: Invalid <ref> tag; no text was provided for refs named RapunzelKHTwitter
  50. Cite error: Invalid <ref> tag; no text was provided for refs named FrozenWorld
  51. 51.0 51.1 51.2 51.3 Cite error: Invalid <ref> tag; no text was provided for refs named NomuraIGNE32018
  52. 52.0 52.1 Cite error: Invalid <ref> tag; no text was provided for refs named BigHero6
  53. 53.0 53.1 Cite error: Invalid <ref> tag; no text was provided for refs named ToyStoryPressRelease
  54. 54.0 54.1 54.2 54.3 Cite error: Invalid <ref> tag; no text was provided for refs named D232017
  55. 55.0 55.1 Cite error: Invalid <ref> tag; no text was provided for refs named EurogamerMay2018Event
  56. Cite error: Invalid <ref> tag; no text was provided for refs named SquareEnixWorlds
  57. Template:Cite web
  58. 58.0 58.1 58.2 Cite error: Invalid <ref> tag; no text was provided for refs named NomuraE32018Variety
  59. Cite error: Invalid <ref> tag; no text was provided for refs named GIConfirmedWorlds
  60. 60.0 60.1 Cite error: Invalid <ref> tag; no text was provided for refs named RealmOfDarkness
  61. Template:Cite web
  62. Cite error: Invalid <ref> tag; no text was provided for refs named KeybladeGraveyard
  63. Cite error: Invalid <ref> tag; no text was provided for refs named MysteriousTower
  64. Cite error: Invalid <ref> tag; no text was provided for refs named IenzoRadiantGarden
  65. 65.0 65.1 Cite error: Invalid <ref> tag; no text was provided for refs named Dec2018ScreenShots
  66. Cite error: Invalid <ref> tag; no text was provided for refs named BigHero6ExtendedTrailer
  67. Cite error: Invalid <ref> tag; no text was provided for refs named ClassicKingdomShorts
  68. Cite error: Invalid <ref> tag; no text was provided for refs named BigHero6Story
  69. 69.0 69.1 69.2 69.3 Cite error: Invalid <ref> tag; no text was provided for refs named NomuraGIJul2017
  70. Cite error: Invalid <ref> tag; no text was provided for refs named WinnieThePoohAnalysis
  71. Cite error: Invalid <ref> tag; no text was provided for refs named BigHero6RoxasOrganizationXIII
  72. Cite error: Invalid <ref> tag; no text was provided for refs named PiratesVerge
  73. 73.0 73.1 Cite error: Invalid <ref> tag; no text was provided for refs named D232018Polygon
  74. Cite error: Invalid <ref> tag; no text was provided for refs named MarshmallowPartyMember
  75. Cite error: Invalid <ref> tag; no text was provided for refs named BigHero6Trailer
  76. Template:Cite web
  77. Template:Cite web
  78. Template:Cite web
  79. Cite error: Invalid <ref> tag; no text was provided for refs named IGNOct2006
  80. Cite error: Invalid <ref> tag; no text was provided for refs named JoystiqFeb2010
  81. Cite error: Invalid <ref> tag; no text was provided for refs named JoystiqMar2010
  82. Cite error: Invalid <ref> tag; no text was provided for refs named IGNSep2010
  83. Cite error: Invalid <ref> tag; no text was provided for refs named DDDAnnounced
  84. Template:Cite web
  85. Cite error: Invalid <ref> tag; no text was provided for refs named Xbox One
  86. Cite error: Invalid <ref> tag; no text was provided for refs named GameInformer 244
  87. 88.0 88.1 88.2 88.3 88.4 88.5 88.6 Cite error: Invalid <ref> tag; no text was provided for refs named EdgeMagazineFeb2019
  88. Cite error: Invalid <ref> tag; no text was provided for refs named Dev Team
  89. Cite error: Invalid <ref> tag; no text was provided for refs named BusinessDivision3
  90. 91.0 91.1 Cite error: Invalid <ref> tag; no text was provided for refs named Famitsu
  91. Cite error: Invalid <ref> tag; no text was provided for refs named E3 early
  92. Cite error: Invalid <ref> tag; no text was provided for refs named Hashimoto
  93. Cite error: Invalid <ref> tag; no text was provided for refs named KotakuJun2014
  94. Cite error: Invalid <ref> tag; no text was provided for refs named GISep2014
  95. Cite error: Invalid <ref> tag; no text was provided for refs named KotakuUnreal
  96. Cite error: Invalid <ref> tag; no text was provided for refs named KotakuJan2015
  97. Cite error: Invalid <ref> tag; no text was provided for refs named NerdistE32017
  98. Cite error: Invalid <ref> tag; no text was provided for refs named SwitchVersionPossible
  99. Cite error: Invalid <ref> tag; no text was provided for refs named GameSpotJul2017
  100. Cite error: Invalid <ref> tag; no text was provided for refs named NomuraE32018IGN2
  101. Cite error: Invalid <ref> tag; no text was provided for refs named UnionXClassicKingdom
  102. Template:Cite news
  103. Template:Cite web
  104. Cite error: Invalid <ref> tag; no text was provided for refs named WinnieThePoohChinaCensor
  105. Cite error: Invalid <ref> tag; no text was provided for refs named DevelopmentComplete
  106. Cite error: Invalid <ref> tag; no text was provided for refs named NomuraGIPirates
  107. Cite error: Invalid <ref> tag; no text was provided for refs named DisneyAcquisitions
  108. Cite error: Invalid <ref> tag; no text was provided for refs named StarWars
  109. Cite error: Invalid <ref> tag; no text was provided for refs named KotakuAcquisitions
  110. Template:Cite web
  111. Template:Cite web
  112. Cite error: Invalid <ref> tag; no text was provided for refs named GISep2017Issue
  113. 114.0 114.1 Cite error: Invalid <ref> tag; no text was provided for refs named IGNDesignChallenges
  114. Template:Cite web
  115. Cite error: Invalid <ref> tag; no text was provided for refs named AdditionalComposers
  116. Template:Cite magazine
  117. Template:Cite web
  118. Template:Cite web
  119. Template:Cite magazine
  120. Cite error: Invalid <ref> tag; no text was provided for refs named HikaruThemeSong
  121. 122.0 122.1 Cite error: Invalid <ref> tag; no text was provided for refs named FaceMyFearsGameRant
  122. Cite error: Invalid <ref> tag; no text was provided for refs named FaceMyFears
  123. Cite error: Invalid <ref> tag; no text was provided for refs named FaceMyFearsKotaku
  124. Template:Cite web
  125. Cite error: Invalid <ref> tag; no text was provided for refs named HobbyConsolas
  126. 127.0 127.1 Cite error: Invalid <ref> tag; no text was provided for refs named HongKongRelease
  127. Cite error: Invalid <ref> tag; no text was provided for refs named GamesRadarMay2018Event
  128. Template:Cite book
  129. Template:Cite web
  130. Template:Cite web
  131. Template:Cite press release
  132. Template:Cite press release
  133. Template:Cite web
  134. Template:Cite web
  135. Template:Cite web
  136. Template:Cite web
  137. Cite error: Invalid <ref> tag; no text was provided for refs named JapanReleaseDate
  138. 139.0 139.1 Cite error: Invalid <ref> tag; no text was provided for refs named ReleaseDate
  139. Cite error: Invalid <ref> tag; no text was provided for refs named EpilogueReleaseDates
  140. Cite error: Invalid <ref> tag; no text was provided for refs named EpilogueRelease
  141. Cite error: Invalid <ref> tag; no text was provided for refs named DeluxeEditions
  142. Cite error: Invalid <ref> tag; no text was provided for refs named ThemedPS4Pro
  143. Cite error: Invalid <ref> tag; no text was provided for refs named UltimaniaNomura
  144. Template:Cite web
  145. Template:Cite web
  146. Template:Cite web
  147. Template:Cite web
  148. Cite error: Invalid <ref> tag; no text was provided for refs named MCPS4
  149. Cite error: Invalid <ref> tag; no text was provided for refs named MCXONE
  150. 151.0 151.1 151.2 Cite error: Invalid <ref> tag; no text was provided for refs named GIReview
  151. 152.0 152.1 Template:Cite web
  152. 153.0 153.1 Cite error: Invalid <ref> tag; no text was provided for refs named GamesRadarReview
  153. 154.0 154.1 154.2 Template:Cite web
  154. Cite error: Invalid <ref> tag; no text was provided for refs named gamerev
  155. Template:Cite web
  156. 157.0 157.1 Template:Cite web
  157. 158.0 158.1 Cite error: Invalid <ref> tag; no text was provided for refs named destructoidrev
  158. Template:Cite web
  159. Template:Cite web
  160. Template:Cite magazine
  161. Template:Cite web
  162. Template:Cite web
  163. Template:Cite web
  164. Template:Cite web
  165. Cite error: Invalid <ref> tag; no text was provided for refs named GameSpotReview
  166. 167.0 167.1 Template:Cite news
  167. Template:Cite news
  168. Template:Cite news
  169. Template:Cite news
  170. Template:Cite magazine
  171. Template:Cite news
  172. Template:Cite news
  173. Template:Cite web
  174. Template:Cite web
  175. Cite error: Invalid <ref> tag; no text was provided for refs named IGNE32018BestOf
  176. Cite error: Invalid <ref> tag; no text was provided for refs named MomoconUnrealE32018BestOf
  177. Cite error: Invalid <ref> tag; no text was provided for refs named E32018Winners
  178. Cite error: Invalid <ref> tag; no text was provided for refs named Gamescom2018Winners
  179. Cite error: Invalid <ref> tag; no text was provided for refs named GoldenJoysticks2018Noms
  180. Cite error: Invalid <ref> tag; no text was provided for refs named GamersChoiceNoms
  181. Cite error: Invalid <ref> tag; no text was provided for refs named JapanGameAwards2019
  182. Cite error: Invalid <ref> tag; no text was provided for refs named GoldenJoysticks2019Noms
  183. Cite error: Invalid <ref> tag; no text was provided for refs named FSGF2019
  184. Cite error: Invalid <ref> tag; no text was provided for refs named TGA2019Noms
  185. Cite error: Invalid <ref> tag; no text was provided for refs named NYGA2020Noms
  186. Cite error: Invalid <ref> tag; no text was provided for refs named AnnieAwards2020Noms
  187. Cite error: Invalid <ref> tag; no text was provided for refs named DICE2020Noms
  188. Cite error: Invalid <ref> tag; no text was provided for refs named NAVGTR2020Noms
  189. Cite error: Invalid <ref> tag; no text was provided for refs named NAVGTR2020Winners
  190. Cite error: Invalid <ref> tag; no text was provided for refs named SXSW2020Noms
  191. Cite error: Invalid <ref> tag; no text was provided for refs named SXSW2020Winners
  192. Cite error: Invalid <ref> tag; no text was provided for refs named FamitsuDengeki2020Winners
  193. Cite error: Invalid <ref> tag; no text was provided for refs named MCPS4re
  194. 195.0 195.1 Cite error: Invalid <ref> tag; no text was provided for refs named IGNReviewre
  195. 196.0 196.1 Cite error: Invalid <ref> tag; no text was provided for refs named GameSpotReviewre
  196. 197.0 197.1 Cite error: Invalid <ref> tag; no text was provided for refs named GIReviewre
  197. Cite error: Invalid <ref> tag; no text was provided for refs named jxre
  198. 199.0 199.1 Cite error: Invalid <ref> tag; no text was provided for refs named desre
  199. Template:Cite web