Ogre Battle 64

Both lean on execution about the same (2 vs 2). Biggest difference: reads (0 vs 1) - All enemies follow scripted AI behaviour trees without player modelling

Both lean on execution about the same (2 vs 2). Biggest difference: reads (0 vs 1) - All tribal and Enclave enemies run fixed scripted combat routines

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Movement is trivial; no aim or precision required.

Both lean on execution about the same (2 vs 2). Biggest difference: variance (4 vs 5) - AD&D dice rolls throughout.

Both lean on execution about the same (2 vs 2). Biggest difference: reads (0 vs 1) - All AI opponents use fixed scripted behaviour trees

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Menu combat; zero dexterity

Both lean on execution about the same (2 vs 2). Biggest difference: variance (4 vs 5) - Randomized loot and dungeon layouts gate power

Both lean on execution about the same (2 vs 2). Biggest difference: reads (0 vs 1) - campaign AI is exploitable and mappable

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Point-and-click placement; zero reflex requirement

Both lean on execution about the same (2 vs 2). Biggest difference: optimization (9 vs 8) - Guard routing, cell ratios, and utility networks are deeply solvable

Both lean on execution about the same (2 vs 2). Biggest difference: variance (4 vs 3) - Drop rates and unknown encounters until mapped.

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - no mechanical layer