Gaming

Nintendo just dropped a new Fire Emblem mobile game, and it’s bad

Bafflingly, it's Fire Emblem if it had virtually zero strategy crossed with Among Us if it only had two possible Imposters

Fire Emblem Shadows

In classic Nintendo fashion, the company made a new game announcement out of nowhere on a Wednesday evening.

This one, though, was different than usual, as it marks the Japanese gaming giants first mobile release since 2021’s Pikmin Bloom. Enter Fire Emblem Shadows, a free-to-play title that was, rather appropriately, shadow dropped last night. The company describes it as “real-time strategy meets social deduction,” which sounds pretty neat on paper.

The problem, however, is that the game kind of sucks. After a classic flashy Fire Emblem cinematic that initially seems promising, you immediately are thrown into battle with little chibi characters. That isn’t inherently bad, but it’s what you do with them that proves so underwhelming.

Basically, Shadows‘ combat has you “managing” a party of three in a tiny grid. I use quotation marks because they move and attack automatically, so all you’re doing is occasionally selecting one of a few special abilities (such as a healing spell or an area of effect flame) that operate on cooldowns. This is the extent of the aforementioned “real-time strategy.”

But the “social deduction” element is especially undercooked. As you head into each battle, two of your units are designated “Disciples of Light,” with the third being the “Disciple of Shadow,” who’s essentially the “Imposter” from Among Us. At the end of each battle, you have to guess who’s the Disciple of Shadow, and whether you choose correctly will affect the next skirmish.

Fire Emblem Shadows

However, the three-unit party means you automatically have a 50/50 shot of getting it right, given that you know you’re not the imposter. That also means that if one of the NPCs is KO’d between rounds, you’ll immediately know who did it. It would be like if the only murder suspects in Knives Out were Daniel Craig, our hero, and douchey Chris Evans, instead of, you know, an entire cast of characters. The party members’ AI also makes it pretty obvious who the imposter is.

Frankly, it’s such a baffling system. It’s possible the three-unit party was a creative choice to keep battles bite-sized for mobile, but if that’s the case, then it just fundamentally breaks the game. And because the actual “combat” side of things is so automated, there’s really little incentive to play, even with the unlockable rewards and multiplayer mode.

Meanwhile, other Fire Emblem staples are missing entirely. For instance, the series’ signature Support conversations, which generally offer great characterization and develop synergistic stats in battle, boil down here to a character just saying their name.

This means that Shadows actually having voiced versions of popular Fire Emblem characters (like my personal favourite, Three Houses‘ Dimitri) ultimately feels wasted here. I suppose furries might get something out of seeing these characters have animal transformations, but even then, they’d be better off just sharing the new artwork online.

Of course, a mobile game isn’t going to be as deep as the console Fire Emblem titles, but the massively successful Fire Emblem Heroes still shows you how to do it well enough. Whatever (likely valid) criticisms you have of that gacha game, it at least has layers of strategy, a surprisingly deep metagame, and a better overall handling of classic FE characters.

As a massive Fire Emblem fan, I’m definitely not going to put any more time into Shadows. If you’re interested, you can download it for free on Android and iOS. But honestly, we’re better off waiting for Fortune’s Weave, the recently-unveiled (and highly promising) next mainline entry, on Switch 2 next year.

Image credit: Nintendo

MobileSyrup may earn a commission from purchases made via our links, which helps fund the journalism we provide free on our website. These links do not influence our editorial content. Support us here.

Related Articles

Fatal error: Uncaught Aws\S3\Exception\PermanentRedirectException: Encountered a permanent redirect while requesting https://ms-staging-baselayer-static-assets.s3.ca-central-1.amazonaws.com/?list-type=2&delimiter=%2F&prefix=uploads%2Fwpcf7_uploads%2F. Are you sure you are using the correct region for this bucket? in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php:49 Stack trace: #0 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(209): Aws\S3\PermanentRedirectMiddleware->Aws\S3\{closure}(Object(Aws\Result)) #1 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(158): GuzzleHttp\Promise\Promise::callHandler(1, Object(Aws\Result), NULL) #2 /var/www/html/vendor/guzzlehttp/promises/src/TaskQueue.php(52): GuzzleHttp\Promise\Promise::GuzzleHttp\Promise\{closure}() #3 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(163): GuzzleHttp\Promise\TaskQueue->run() #4 /var/www/html/vendor/guzzlehttp/guzzle/src/Handler/CurlMultiHandler.php(189): GuzzleHttp\Handler\CurlMultiHandler->tick() #5 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(251): GuzzleHttp\Handler\CurlMultiHandler->execute(true) #6 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(227): GuzzleHttp\Promise\Promise->invokeWaitFn() #7 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #8 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #9 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(272): GuzzleHttp\Promise\Promise->waitIfPending() #10 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(229): GuzzleHttp\Promise\Promise->invokeWaitList() #11 /var/www/html/vendor/guzzlehttp/promises/src/Promise.php(69): GuzzleHttp\Promise\Promise->waitIfPending() #12 /var/www/html/vendor/aws/aws-sdk-php/src/AwsClientTrait.php(58): GuzzleHttp\Promise\Promise->wait() #13 /var/www/html/vendor/aws/aws-sdk-php/src/ResultPaginator.php(151): Aws\AwsClient->execute(Object(Aws\Command)) #14 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(52): Aws\ResultPaginator->valid() #15 /var/www/html/vendor/aws/aws-sdk-php/src/functions.php(69): Aws\map(Object(Aws\ResultPaginator), Object(Closure)) #16 [internal function]: Aws\flatmap(Object(Aws\ResultPaginator), Object(Closure)) #17 /var/www/html/wp-content/plugins/s3-uploads/inc/class-stream-wrapper.php(695): Generator->valid() #18 [internal function]: S3_Uploads\Stream_Wrapper->dir_readdir() #19 /var/www/html/wp-content/plugins/contact-form-7/includes/file.php(362): readdir(Resource id #734) #20 /var/www/html/wp-includes/class-wp-hook.php(322): wpcf7_cleanup_upload_files() #21 /var/www/html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #22 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #23 /var/www/html/wp-includes/load.php(1280): do_action('shutdown') #24 [internal function]: shutdown_action_hook() #25 {main} thrown in /var/www/html/vendor/aws/aws-sdk-php/src/S3/PermanentRedirectMiddleware.php on line 49