Conan’s arrival in Mortal Kombat 1 is pure fan service done right. As a guest fighter ripped straight from classic sword-and-sorcery fantasy, he brings a slower, heavier neutral game built around massive normals, armor-backed specials, and brutal corner carry. He’s not about flashy cancels or high APM pressure; he’s about controlling space, forcing bad decisions, and ending rounds with authority.
That’s exactly why his second Fatality matters. This isn’t just another gore showcase for completionists. It’s a statement Fatality that reinforces Conan’s identity and, more importantly, tests whether players can execute cleanly under real match pressure instead of mashing after a flawless win.
Why Conan Fits Mortal Kombat 1’s Roster
Conan thrives in MK1’s slower, footsies-driven pace compared to previous entries. His oversized hitboxes and long-reaching buttons let him bully opponents who panic or overcommit, especially online where reaction windows are tighter. When you win with Conan, it usually feels decisive, and his Fatalities are designed to reflect that dominance.
The second Fatality leans heavily into his barbarian brutality, using deliberate timing and spacing rather than rapid inputs. It’s the kind of finisher that looks simple on paper but exposes sloppy execution instantly.
Conan’s Second Fatality Inputs and Distance
Conan’s second Fatality must be performed at mid-range. Too close and the input will fail; too far and you’ll get nothing but an awkward whiff while the opponent collapses.
The command input is consistent across platforms, with only the face buttons changing:
PlayStation: Down, Back, Down, Triangle
Xbox: Down, Back, Down, Y
Nintendo Switch: Down, Back, Down, X
Hold Block during the input if Release Check is turned off, which is the default for many competitive players. If Release Check is on, be extra clean with directional taps to avoid accidental specials.
Common Execution Mistakes Players Make
The biggest mistake is standing too close. Conan naturally wants to crowd his opponent after a win, especially off throws or corner enders, but this Fatality demands a clear step back. Take a micro-walk backward before inputting if you’re unsure.
Another frequent issue is rushing the sequence. The Down, Back, Down pattern needs distinct inputs, not a sloppy slide. On D-pad, think deliberate taps; on analog, reset to neutral between directions to avoid diagonal reads.
Tips to Land It Consistently in Real Matches
Train the distance first, not the buttons. In practice mode, knock the opponent down, back up until Conan’s sword tip barely wouldn’t reach, and burn that spacing into muscle memory. Once the range feels automatic, the input becomes trivial.
In online matches, buffer the Fatality immediately after “Finish Him” appears, but don’t panic. Conan’s second Fatality has a forgiving input window, so focus on spacing, then execute cleanly. When it lands, it’s one of the most satisfying finishers in MK1, and a clear signal that you didn’t just win the match, you dominated it.
Unlock Conditions and When Conan’s Second Fatality Becomes Available
Landing the input cleanly is only half the battle. Like the rest of MK1’s roster, Conan’s second Fatality is progression-gated, meaning it won’t work at all until you’ve met the unlock requirement tied to his character mastery.
Character Mastery Level Requirement
Conan’s second Fatality unlocks when he reaches Character Mastery Level 14. Until you hit that level, the game will ignore the input entirely, no matter how perfect your spacing or timing is.
This applies across every mode. Versus, Online, Towers, and Practice Mode all respect mastery locks, so you won’t be able to “sneak” the Fatality early just to lab it.
How to Unlock It Efficiently
The fastest way to reach Level 14 is grinding Towers with Conan as your main fighter. Longer towers with modifiers give more mastery XP, and Invasions mode is also extremely efficient if you’re clearing nodes consistently without retries.
Online matches work too, but they’re slower unless you’re winning cleanly and often. If you’re specifically chasing the Fatality, offline progression is simply more time-efficient and less RNG-dependent.
When It Appears in the Move List
Once unlocked, Conan’s second Fatality will immediately appear in the Fatalities section of his move list. This is your confirmation that the game will now accept the input in real matches.
If you don’t see it listed, it’s not unlocked yet, period. No amount of perfect execution will override that lock, which is why so many players think the Fatality is “bugged” when it’s really just unavailable.
Easy Fatality Tokens and Platform Parity
Easy Fatality tokens do not bypass the unlock requirement. You still need Conan at Mastery Level 14 before the game allows either the standard input or the simplified version to work.
There’s also no platform variance here. PlayStation, Xbox, and Nintendo Switch all follow the exact same unlock rules, so progression carries the same expectations no matter where you’re playing.
Once it’s unlocked, everything covered earlier about spacing, clean Down, Back, Down inputs, and deliberate execution applies fully. From that point on, failing the Fatality is no longer about progression, it’s purely about player discipline.
Exact Input Commands for Conan’s Second Fatality (Switch, Xbox, PlayStation)
Now that the Fatality is fully unlocked and visible in the move list, execution becomes the only gate left. Conan’s second Fatality is strict about both distance and directional clarity, which is why missed inputs usually come down to spacing drift or rushed commands.
Before worrying about speed, lock in the correct range. This Fatality requires Close Range, meaning you should be nearly chest-to-chest with the opponent when “Finish Him” appears.
Distance Requirement: Close Range Only
Close range in Mortal Kombat 1 is tighter than most players expect. You want Conan’s front foot almost overlapping the opponent’s hurtbox, not just within grab distance.
If you take even a micro-step back during the finish state, the game will read the input correctly but refuse to trigger the Fatality. This is the most common failure point, especially after knockback-heavy enders.
A good habit is to hold Forward for a split second as “Finish Him” appears, then release before starting the input. That tiny adjustment removes spacing uncertainty without affecting the command.
PlayStation Input (PS5 / PS4)
Input: Down, Back, Down, Square
Down and Back must be clean cardinal directions, not a down-back shortcut. Square is Conan’s front punch, and the game is very strict about reading it as a button press after the final Down.
Avoid sliding your thumb from Back to Down in one motion. Treat each direction as a deliberate tap, especially if you’re on a DualSense D-pad, which can easily blur diagonals.
Xbox Input (Series X|S / Xbox One)
Input: Down, Back, Down, X
The Xbox D-pad is slightly more forgiving, but the timing window is identical to PlayStation. X must be pressed immediately after the final Down with no delay, or the input buffer will expire.
If you’re using an analog stick, stop. This Fatality is far more consistent on D-pad due to how MK1 prioritizes directional precision over speed.
Nintendo Switch Input
Input: Down, Back, Down, Y
On Switch, handheld players should be especially careful with diagonals. The Joy-Con D-pad buttons can accidentally register down-back if pressed unevenly.
Docked play with a Pro Controller dramatically improves consistency. The input window is the same as other platforms, but Switch hardware punishes sloppy directional input more harshly.
Common Execution Mistakes That Kill the Fatality
The biggest mistake is rushing the input as soon as “Finish Him” appears. MK1 gives you plenty of time, so slow down and confirm your spacing before pressing anything.
Another frequent issue is holding Back for too long after the final Down. This can cause Conan to step backward, instantly breaking the close-range requirement even though the input itself was correct.
Button mashing is also fatal here. If Square, X, or Y is pressed early or multiple times, the game may read it as a normal attack input instead of a Fatality trigger.
Consistency Tips for Real Matches
End the round with a standing jab or short string that leaves Conan point-blank. Avoid knockdowns or launchers that create pushback unless you’ve practiced walking back in consistently.
In online play, latency can subtly affect input rhythm. Slow your directional taps slightly to ensure each input registers cleanly rather than trying to muscle-memory the sequence.
If you can land this Fatality ten times in a row in Practice without looking at the input list, you’re ready to execute it under pressure. At that point, success isn’t about reaction speed, it’s about discipline and spacing control.
Required Distance and Positioning: Close, Mid, or Full Screen Explained
Even perfect inputs will fail if your spacing is off by a pixel. Mortal Kombat 1 is brutally strict about Fatality distance checks, and Conan’s second Fatality is a textbook example of how positioning matters just as much as execution.
Before you even think about pressing Down or Back, you need to lock in the correct range and stop moving.
Close Range: What Conan’s Second Fatality Actually Requires
Conan’s second Fatality is a Close-range Fatality. That means point-blank, chest-to-chest distance, with no walking forward or backward during the input.
If Conan can land a standing jab without taking a step, you’re close enough. If you need to tap Forward to reach the opponent, you’re already too far out and the Fatality will not trigger.
A common misconception is that “close” allows a tiny step back. It doesn’t. Even a micro-walk backward during the input can shift Conan outside the hitbox check and kill the animation instantly.
Why Mid Range and Full Screen Will Always Fail
Mid range is roughly sweep distance, where low kicks or long-reaching normals connect. At this spacing, the game will ignore the Fatality input entirely and default to normal attacks or idle stance.
Full screen is self-explanatory, and no version of Conan’s second Fatality works from this distance. Unlike certain cinematic Fatalities in MK1, there is no screen-wide pull or auto-correction here.
If you’re seeing Conan twitch or throw out a random normal instead of triggering the Fatality, the game is telling you your spacing is wrong, not your inputs.
Visual Cues to Confirm You’re Close Enough
Look at Conan’s feet relative to the opponent’s. If their toes are nearly touching or slightly overlapping, you’re in the correct zone.
Another reliable cue is idle animation overlap. When characters are truly close, their idle stances subtly clip into each other instead of swaying independently.
Relying on the camera zoom is risky, especially on certain stages. Trust character spacing, not how “zoomed in” the scene feels.
Micro-Adjustments Without Breaking the Fatality Window
If you’re slightly too far, tap Forward once, then release the D-pad completely before starting the input. Holding Forward for even a fraction of a second too long can cause Conan to step again mid-input.
Never adjust backward. If you overshoot and walk past the opponent, rotate Conan with a tiny Forward tap instead of backing up, then re-center.
After “Finish Him” appears, take a breath, fix your spacing, then commit. MK1 gives you enough time to position perfectly, but zero forgiveness if you move during the sequence.
Step-by-Step Execution Breakdown for Consistent Success
Once spacing is locked in, execution becomes the final gatekeeper. Conan’s second Fatality in Mortal Kombat 1 is not input-heavy, but it is timing-sensitive and brutally honest about mistakes. Treat this like a combo ender, not a cinematic button mash.
Confirm the Distance Before Touching the Input
Start with both characters standing completely still at close range. No crouching, no micro-walks, no accidental stick drift. If Conan or the opponent is still sliding from a previous animation, wait half a beat until both idle stances fully settle.
This pause matters because MK1 checks Fatality conditions on a clean input state. If you begin buffering while Conan is still recovering, the game may read movement instead of the Fatality command.
Input Order and Platform-Specific Commands
With spacing confirmed, enter the input cleanly and without rushing. Conan’s second Fatality requires deliberate directional taps, not slides.
PlayStation: Down, Back, Forward, Circle
Xbox: Down, Back, Forward, B
Nintendo Switch: Down, Back, Forward, A
Use the D-pad whenever possible. Analog sticks introduce diagonals, and a single Down-Back misread can invalidate the entire sequence.
Rhythm Matters More Than Speed
Do not mash or rapid-fire the directions. Think of the input as four distinct beats, each pressed and released before the next. A smooth, even rhythm is far more reliable than trying to “dump” the command as fast as possible.
If you rush, the game may interpret Back to Forward as a dash attempt, especially on pad. That instantly breaks the close-range requirement and kills the Fatality.
Button Press Discipline at the End
The final face button press should be firm and singular. Double-tapping Circle, B, or A can cause Conan to throw a stray normal if spacing has drifted even slightly. One press, full stop.
Also avoid holding the button. MK1 occasionally prioritizes held inputs as follow-up actions, which can cause the Fatality to fail silently.
Common Execution Killers to Watch For
The most frequent mistake is accidental forward movement during the input. This usually comes from rolling the D-pad or over-tilting the stick. Each direction should be a clean tap, not a roll.
Another silent failure comes from inputting too early. If “Finish Him” hasn’t fully stabilized on screen, the game may still be clearing hitstun and ignore the command.
Training Mode Drills for Real Match Consistency
Set the CPU to stand and practice walking into close range, stopping completely, then executing the Fatality without adjusting again. Repeat until you can do it without thinking.
Next, simulate match conditions by finishing a combo, waiting a split second, then performing the input. This builds muscle memory for real rounds where adrenaline and timer pressure are in play.
Quick Reliability Tips from High-Level Play
Always reset your thumb to neutral between directions. Neutral inputs act as a buffer cleaner and prevent dash reads.
If the Fatality fails, don’t blame execution immediately. Check your spacing first, then slow the rhythm slightly on the next attempt. Conan’s second Fatality rewards patience, not panic.
Common Mistakes That Cause Conan’s Second Fatality to Fail
Even after locking in the correct input, Conan’s second Fatality is notorious for failing due to small, easily overlooked errors. Most of these mistakes happen under match pressure, not in Training Mode, which is why consistency drops online. If the Fatality isn’t triggering, one of the issues below is almost always the culprit.
Being One Step Too Far (or Too Close)
Conan’s second Fatality has a strict close-range requirement, not mid, not sweep, and not point-blank overlap. If Conan’s chest isn’t nearly touching the opponent, the input will fail silently.
Players often drift forward during the Back input, especially on analog stick. That micro-step shifts Conan out of the correct hitbox range and invalidates the Fatality even though the command looks clean.
Accidental Dash Inputs on D-Pad or Stick
Back-to-Forward motions are the most common execution killer across all platforms. On PlayStation and Xbox, rolling the D-pad instead of tapping clean directions can register a dash instead of discrete inputs.
On Switch, this happens even more due to the Joy-Con D-pad sensitivity. If the game reads a dash, Conan moves, spacing breaks, and the Fatality is dead on arrival.
Pressing the Final Button Too Early
The Fatality window does not fully open the instant “Finish Him” appears. There is a brief buffer where the opponent is still exiting hitstun, and any input during that moment is ignored.
This is especially common after combo enders. Waiting a half-beat before starting the input dramatically increases consistency across PlayStation, Xbox, and Switch.
Double-Tapping or Holding the Face Button
On PlayStation, double-tapping Circle can cause a stray normal. On Xbox, the same applies to B, and on Switch, A behaves identically. If spacing has shifted even slightly, that normal overrides the Fatality.
Holding the button is just as risky. MK1 can prioritize held inputs as follow-ups, which results in Conan doing nothing instead of triggering the cinematic.
Inputting Too Fast Instead of Too Clean
Speed is not rewarded here. Dumping the full input in one blur often causes the game to skip or merge directions, especially Back into Down.
Think of the Fatality input as four clean taps plus a single button press. Slowing down by a fraction of a second often fixes “random” failures immediately.
Platform-Specific Muscle Memory Errors
Players switching platforms frequently run into trouble here. PlayStation’s D-pad favors precision taps, Xbox pads tend to exaggerate diagonals, and Switch inputs are less forgiving with rapid direction changes.
If you play on multiple systems, consciously reset your muscle memory. Treat Conan’s second Fatality like a fresh input instead of assuming it will transfer cleanly across controllers.
Not Returning to Neutral Between Directions
Skipping neutral is a silent execution killer. Holding one direction while pressing the next increases the chance of the game reading a diagonal or dash.
Resetting to neutral between each input cleans the buffer and stabilizes the command. High-level players do this instinctively, especially in tournament settings.
Trying to Adjust Spacing Mid-Input
Once the input starts, spacing adjustments are over. Any micro-walk, crouch, or correction invalidates the close-range requirement instantly.
Always confirm distance first, stop completely, then execute. Conan’s second Fatality punishes hesitation harder than execution errors.
Quick Fixes and Pro Tips for Landing the Fatality in Real Matches
At this point, execution errors aren’t random anymore. They’re almost always coming from match pressure, online latency, or tiny mechanical habits that only show up outside of Practice Mode. These fixes are designed to stabilize Conan’s second Fatality when it actually counts.
Lock the Distance Before the Finish Him Screen
Conan’s second Fatality is close range, and “close” in MK1 is stricter than it looks. You want your character models nearly touching, not just inside throw range.
The safest setup is to walk forward slightly as the opponent is falling, then stop completely before Finish Him appears. If you’re still holding forward when the input starts, the game can read a dash and kill the Fatality instantly.
Use the Exact Platform Input Every Time
Consistency beats improvisation. Conan’s second Fatality input does not tolerate shortcuts or mirrored motions.
On PlayStation, the input is Back, Down, Back, Circle at close range.
On Xbox, it’s Back, Down, Back, B at close range.
On Switch, it’s Back, Down, Back, A at close range.
Say the directions in your head as you press them. This sounds simple, but it prevents accidental diagonals and keeps your rhythm clean under pressure.
Delay the Button Press by a Split Second
One of the most common real-match failures is pressing the face button too early. If Circle, B, or A is hit during the final Back input instead of after it, MK1 often reads a normal instead of a Fatality.
Finish the directional sequence first, return to neutral, then tap the button. That micro-delay dramatically increases success online and offline.
Respect Online Latency and Input Buffering
Online matches introduce delay that Practice Mode doesn’t prepare you for. If you rush the input, the buffer can eat a direction or merge Back into Down.
Slow the input down by about 10 percent when playing online. The Fatality window is generous, and clean inputs survive lag far better than fast ones.
Avoid Holding Block or Stance Switch
Many players unconsciously hold Block or Stance Switch during Finish Him, especially after defensive rounds. Both can interfere with directional clarity on certain controllers.
Release all shoulder buttons before starting the input. Think of Fatalities as a fresh state, not a continuation of neutral gameplay.
Train the Fatality From Both Sides
Side bias is real. Inputs that feel perfect on Player 1 side often fall apart on Player 2 side due to reversed muscle memory.
Practice Conan’s second Fatality equally from left and right. Tournament players do this religiously, and it’s one of the fastest ways to eliminate “it only works sometimes” frustration.
Use Match-End Flow Instead of Panic Inputs
The biggest execution killer isn’t mechanics, it’s adrenaline. Players see Finish Him and mash like the window is one frame long.
It isn’t. Take a breath, confirm spacing, then input with intent. Conan’s second Fatality rewards calm hands far more than fast ones.
Troubleshooting Input Errors, Online Delay, and Controller Settings
Even when you understand the input, real matches add layers of friction that Practice Mode never shows. If Conan’s second Fatality feels inconsistent, the problem usually isn’t the combo itself, but how the game is reading your controller, timing, or connection state.
This is where tightening the setup turns a “sometimes” Fatality into a guaranteed finish.
Double-Check the Exact Input and Distance
Conan’s second Fatality is a close-range input, and that part matters as much as the directions. You should be standing almost chest-to-chest when Finish Him appears.
The input is Back, Down, Back plus the face button. On PlayStation, that’s Circle. On Xbox, it’s B. On Switch, it’s A. If you’re even a half-step too far, MK1 will ignore the sequence no matter how clean it is.
Watch for Accidental Diagonals on D-Pad and Stick
The most common execution error comes from diagonal inputs the game never shows you. Down-Back instead of a clean Down will break the sequence instantly.
If you’re on analog stick, consider switching to D-pad for Fatalities only. If you’re already on D-pad, slow the motion and exaggerate each direction so the game clearly reads Back, then Down, then Back again.
Online Delay Changes the Rhythm, Not the Input
Lag doesn’t make the Fatality harder, it makes rushing worse. Online delay compresses your inputs, causing MK1 to buffer directions together if you move too fast.
Treat online Fatalities like a deliberate string, not a flick. Input Back, pause, Down, pause, Back, return to neutral, then press the button. That pacing survives rollback far better than speed.
Check Release Check and Input Shortcuts in Settings
Controller settings matter more than most players realize. If Release Check is enabled, letting go of a direction can count as an extra input, which can corrupt the sequence.
Turning Release Check off gives you cleaner reads for Fatalities. Also disable unnecessary input shortcuts if you’re getting random normals instead of finishers.
Clear Your Hands Before Finish Him
Holding Block, Stance Switch, or even Trigger buttons during Finish Him can interfere with how MK1 parses directions. This is especially noticeable on Xbox controllers with sensitive triggers.
As soon as the round ends, reset your grip. Thumbs on directions, nothing else pressed. Think of it as rebooting your controller state before the input.
Practice the Fatality in Match Conditions
Practice Mode is good for learning, but real consistency comes from simulating pressure. Turn on random block, end rounds manually, and force yourself to walk into close range before inputting.
The goal is muscle memory under stress. Once your hands know the spacing and rhythm, Conan’s second Fatality becomes automatic instead of a gamble.
Mastering Fatalities in Mortal Kombat 1 isn’t about speed or flair, it’s about control. Slow inputs, clean directions, and smart settings turn execution into muscle memory. When Finish Him appears, you won’t hope it works. You’ll know it does.