Dragonfire
Timing-based dodging of projectiles across two repeating screens of escalating speed.
the cheat-test profile
The four axes - the argument
Each axis is rated on its own - how far one cheat would trivialize the game here. They don't trade off; low on all four means the game is an experience, not a contest.
Execution
cheat: Aimbot - perfect inputs
7/10Jumping fireballs on the bridge demands precise, escalating timing
Reads
cheat: Out-predict an adaptive opponent
0/10Dragons fire on script, not in response to your habits
Variance
cheat: See what's hidden / map the RNG
2/10Fireball timing varies slightly but is quickly internalised
Optimization
cheat: A perfect solver / coach
4/10Treasure routes and safe paths are learnable fixed patterns
How to read this
Each axis is named by the cheat that would break the game along it. Execution is the hands. Reads is out-thinking an adaptive opponent. Variance is hidden information & RNG. Optimization is the solvable systems layer. A game's region is the top one or two axes.
These four aren't one rating split four ways - they're independent 0-10 questions. A 9 on one axis takes nothing from the others, and a game low on all four isn't missing data: it's telling you there's no skill here to cheat.
The basis is how the majority actually plays this game - not a niche mode or a personal run. For a game with very different modes (a story campaign versus ranked multiplayer), that's the version most people mean.
Compare with
Similar games
see all →Ranked by shared genre first, then by how closely the cheat-test profile matches - a cross-genre tag means a pick matched on skill profile alone.
Game details
- Released
- 1982
- Developer
- Imagic
- Platforms
- vic-20, colecovision, Atari2600, C64, ZXS, TRS-80 Color Computer, intellivision, Apple][
- Modes
- Single player
- IGDB users
- 62/100