7 Mistakes That Kill Your Run in The Last Judgement (And How I Fixed Them)
I've died 127 times in The Last Judgement. I know because I started counting after my 50th game-over screen drove me to figure out what I was doing wrong. Here's the thing nobody expects: I built this game. I wrote every spawn timer, tuned every difficulty curve, placed every pixel of that radial ring. And I still made the same seven mistakes over and over again — dying to systems I personally designed. Fixing them took my average score from 2,800 to 6,400 in one week.
This isn't theory. These are the actual errors that ended my runs, tracked across 20 consecutive games. I'll show you which mistake killed me most often, how I fixed each one, and the exact score improvement I saw afterward. If the developer can't avoid these traps, you definitely need to hear about them.
Mistake #1: Hesitating on the First Drag
My biggest killer: hesitation. I'd see a soul spawn, recognize it was good or evil, then pause for half a second before dragging. That delay killed 32% of my runs.
I coded the timer ring to start shrinking the instant a soul appears. I know this because I wrote that logic. But playing? I tested this by recording my screen anyway, because even as the developer I needed to confirm what my hands were experiencing versus what my code specified. The radial countdown begins at spawn, not when you start dragging. Every millisecond I spent "thinking" was time I couldn't afford.
How I fixed it: I forced myself to drag the moment I identified the soul type. Not after. During. My hand moved while my brain finished processing. This felt wrong at first — like I was guessing — but the game rewards decisiveness over certainty. I designed it that way, and I still had to learn it through my own body.
Result: My average survival time jumped from 1:47 to 3:22. This single fix doubled my longevity.
Mistake #2: Dragging in Curved Paths Instead of Straight Lines
I watched my replays and noticed I was dragging souls in slight arcs — curving from center to heaven or hell. Curved paths take longer than straight vertical drags. I lost 0.3-0.5 seconds per soul doing this.
Watch your own cursor path. If it's not a perfectly vertical line, you're wasting time. The game only cares about final position (top half = heaven, bottom half = hell), so diagonal or curved drags add zero benefit. I know this intimately — I implemented the hit detection zones. There's no bonus for style, no hidden score for smooth arcs. The code just checks: did you cross the midpoint threshold? Which direction?
The fix: I practiced dragging straight up and straight down in 30-second drill sessions between games. I'd spawn a soul, drag it vertically, note if my path curved, repeat. After 10 drills, my muscle memory corrected itself. The click of releasing a cleanly sorted soul became satisfying — a sharp, clean snap instead of the sluggish whoosh of an arced drag.
Result: Shaved 8-12 seconds off my level completion times. At level 8+, that's the difference between clearing the screen and dying mid-sort.
Mistake #3: Ignoring the Timer Ring Visual
The radial timer ring is the most important UI element in the game. I designed it. I tweaked its color gradient, its shrink rate, its thickness at every level. And I ignored it for 40+ games. I'd focus on the soul icon, drag it, then check the timer. By then, I'd already wasted precious frames.
My own Game Over screen said "Reason: The timer runs out." I designed the timer. I still forgot about it. That's how strong the center-screen tunnel vision is. You build the warning system, you tune it for visibility, and then your own eyes glue themselves to the soul sprite sitting right in the middle of the screen. The ring could be screaming red in your periphery and you wouldn't notice.
The ring shrinks at different speeds depending on your level. Early levels give you 3-4 seconds per soul. By level 9, you get 1.8 seconds max. I didn't adjust my pace because I wasn't watching the ring — even though I was the one who calibrated those exact shrink rates.
Here's what changed my approach: I started using peripheral vision to monitor the ring while my central vision identified the soul type. When the ring hit 50% (halfway around the circle), I'd speed up my decision regardless of ambiguity.
I googled "why do I choke under time pressure" and found research on the speed-accuracy tradeoff that confirmed what I was seeing: faster decisions don't always mean more errors, especially when delay has a higher cost than mistakes. I built The Last Judgement to punish delay more than it punishes misclassification — and I still needed a Wikipedia article to convince myself my own design philosophy was correct.
Result: My late-game (level 10+) survival rate increased 40%. I started making the timer deadline instead of running out of time mid-drag.
Mistake #4: Panic-Sorting When Multiple Souls Spawn
Multi-spawns start around level 6. Two or three souls appear simultaneously, each ringed by its own shrinking halo. I'd panic, drag the first one I saw, then scramble for the others. This killed 18% of my runs.
The mistake: random order. I was sorting left-to-right or whatever soul my cursor happened to be near. But each soul has its own independent timer ring — I programmed it that way specifically to force triage decisions. Sorting by screen position instead of urgency meant I'd clear the "easy" soul with 2 seconds left while the "hard" soul with 0.8 seconds timed out beside it.
The solution: Triage by timer ring fullness, not spawn position. I scan all visible souls, identify which has the emptiest ring, sort that one first, then move to the next-most-urgent. You have to train your eyes to read the rings like gauges on a dashboard.
Here's my priority system:
Ring < 30% full — Drop everything, sort this immediately
Ring 30-60% full — Sort after critical souls
Ring > 60% full — Safe to delay while handling urgent ones
Result: Multi-spawn survival rate went from 34% to 71%. I stopped dying to "too many souls at once" and started dying to actual difficulty spikes.
Mistake #5: Not Centering My Cursor Between Drags
I'd drag a soul to heaven, release it, then have to move my cursor all the way back to center-screen for the next spawn. At level 12+, souls spawn every 1.2 seconds. Moving from top-of-screen to center wastes 0.4 seconds per soul — and I can feel the heat of that lost time by level 14, when the lava glow at the bottom of the screen seems to pulse faster.
The optimization: After releasing a soul, I immediately return my cursor to the vertical center of the screen (the horizon line between clouds and lava). This position minimizes travel distance to any new spawn. I designed spawns to always appear at center precisely so that a disciplined player could park their cursor there. It took me weeks of dying to follow my own design intent.
I learned this principle from watching speedrunners play sorting games. They call it "cursor parking" — always return to optimal position between actions. You'd think the developer would know this instinctively. I didn't.
Result: Saved 0.3-0.5 seconds per soul. Over a 50-soul run, that's 15-25 seconds of extra time. Enough to survive 8-12 additional spawns.
Mistake #6: Overthinking Ambiguous Icons
Some icons are deliberately ambiguous. I drew them that way — hooded figures that could look like demons at small sizes, skulls crowned with halos that blur the line between sacred and damned. I'd stare at these for 1-2 seconds trying to "be sure" before dragging. The artist in me appreciated the detail. The player in me was dying because of it.
When I saw my score frozen at zero, I slowed down to check if I was doing something wrong. That hesitation is exactly what kills runs at higher levels. I spent precious seconds second-guessing the scoring system I built, wondering if my drag wasn't registering, wondering if something was broken — when really I just hadn't sorted a soul correctly yet. The confusion bled into my next few drags. I moved cautiously, like my hands were wrapped in wool. That caution cost me everything.
But here's what I discovered through tracking: The Last Judgement has a 92% accuracy threshold for progression. You can misclassify 8 souls out of 100 and still advance levels. Spending 2 seconds to achieve 100% certainty on one soul means you time-out on the next two. I set that threshold at 92% during development — generous enough that speed should always beat perfectionism. And yet I still fell into the perfectionism trap.
I looked up why ambiguous icons paralyzed me so badly and found research on cognitive load theory: decision paralysis gets exponentially worse when we demand perfect information before acting. I built The Last Judgement to exploit this instinct — it wants you to overthink. Knowing that as the creator didn't protect me as the player.
My rule now: If I can't classify an icon in 0.8 seconds, I make my best guess and move on. I'd rather misclassify 1/10 ambiguous souls than time-out on 3/10 clear souls. I'm still not sure this is the optimal strategy — maybe there's a visual tell I'm missing on the ambiguous ones, some detail in my own artwork I've forgotten — but the numbers don't lie.
Result: Accuracy dropped from 97% to 94%, but my score increased 38% because I stopped timing out.
Mistake #7: Playing When Tired
I tracked my scores by time-of-day. My 8 PM - 10 PM sessions averaged 5,200 points. My 11 PM - 1 AM sessions averaged 2,900 points. Same player, same game, 44% score drop.
The difference: reaction time. When I'm tired, my icon recognition slows by 200-400ms and my dragging accuracy drops. I make more curved drags, hesitate more, misjudge timer urgency. The soul icons I designed look muddier through exhausted eyes — the warm glow of a halo bleeds into the cold flicker of demonic fire when your pupils won't focus.
The fix: I stopped playing after 10:30 PM. If I want to improve, I play when my brain is sharp. If I want to relax, I play something else.
This sounds obvious, but I wasted 15+ hours grinding scores while exhausted, convinced "one more run" would be the breakthrough. It never was. You'd think building the game would give me some edge at 1 AM. It doesn't. Fatigue doesn't care about your credentials.
Result: My peak score jumped from 6,800 to 9,400 within three days of only playing during high-energy windows.
Which Mistake Killed Me Most?
I tracked every death across 20 games. Here's the breakdown:
Hesitation (32%) — Delayed first drag, timer expired
Timer ignorance (23%) — Didn't notice ring was almost empty
Multi-spawn panic (18%) — Sorted wrong soul first
Curved drags (14%) — Wasted time on inefficient paths
Ambiguity paralysis (8%) — Overthought unclear icons
Cursor position (3%) — Poor cursor parking between drags
Fatigue (2%) — Played when tired (low sample due to time restrictions)
Fixing hesitation had 5x more impact than fixing cursor position. Start with the biggest killer, not the easiest fix. And if you're wondering whether the developer has some hidden advantage in this game — I don't. I die to the same mistakes you do. The code doesn't play favorites.
Before and After: The Numbers
Here's my progress after fixing each mistake in order of impact:
Before: Average score 2,800, average level 6, survival time 1:47
After fixing hesitation: Average score 4,200 (+50%), level 8, survival time 3:22
After fixing timer awareness: Average score 5,100 (+21%), level 9, survival time 4:41
After fixing multi-spawn triage: Average score 6,400 (+25%), level 11, survival time 6:18
After fixing all seven: Average score 7,900 (+23%), level 13, survival time 8:52
Total improvement: 182% score increase over baseline.
FAQ: Common Questions About These Mistakes
Q: How long did it take you to break these habits?
About 8-10 hours of focused play spread over one week. Hesitation took 3 hours to fix because it's pure muscle memory retraining. Cursor parking took 20 minutes because it's just a conscious habit. The timeline depends on which mistake you're fixing — motor skills take longer than strategic adjustments. And yes, I had to retrain muscle memory on my own game. Building it didn't give me a shortcut.
Q: Do these fixes work at higher levels (15+)?
Yes, but the margins shrink. At level 15, even perfect execution barely beats the timer. I tuned those level 15+ timers to be punishing — and they are. These fixes got me from dying at level 6 to dying at level 13. To push beyond 15, you need near-perfect icon recognition (sub-0.5s identification) and optimized drag paths I haven't mastered yet.
Q: What if I'm already doing most of these correctly?
Track your deaths for 10 games. Write down the exact reason each run ended (timer expired, wrong sort, etc.). Your personal mistake distribution will differ from mine. Fix your top 2 killers first — that's where you'll see the biggest improvement. Don't waste time optimizing cursor parking if multi-spawn panic is killing 40% of your runs.
Q: Is there a practice mode for drilling specific mistakes?
No — and honestly, I probably should have built one. But you can create drills yourself. For hesitation: Play 5 rounds where you deliberately drag souls 50% faster than comfortable, even if you misclassify. For timer awareness: Play 5 rounds where you only watch the ring, barely looking at the soul icon. These focused drills isolate the skill you're fixing.
Q: Why does the game punish hesitation so heavily?
Because I designed it to. Hesitation compounds. If you hesitate 0.5s on soul #1, you have 0.5s less for soul #2, which makes you hesitate more on soul #2, which gives you even less time for soul #3. The timer doesn't pause between souls — it's continuous pressure. I built that cascade intentionally, but living inside it as a player still rattles me. One hesitation cascades into run-ending panic by soul #5.
Your Next Steps
Pick your biggest killer from this list. Play 5 games focusing only on fixing that one mistake. Ignore the others for now. Track your scores.
Once that fix becomes automatic, move to your second-biggest killer. Repeat.
This is how I went from 2,800 to 9,420 in 20 games. You don't need to be perfect. You just need to stop making the same mistake 32% of the time.
Start with hesitation. It's the silent run-killer. Fix it today and watch your scores double by tomorrow.
For more on building fundamentals, check out The Last Judgement: Complete Beginner's Guide. If you want additional optimization techniques, see 10 Tips to Get Higher Scores in The Last Judgement.
About the Author
Game Developer & Founder, Stay Foolish Capital
Kento is a game developer and ex-startup founder with a successful tech exit and deep experience across multiple technology domains. A former top-ranked competitive player in Japan, he applies deep analysis of game physics and algorithms to uncover winning strategies and develop compelling gaming experiences.