King's Quest

Both lean on execution about the same (2 vs 2). Otherwise the profiles match closely.

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 3) - Timed attack and block prompts add light input demands

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Clicking menus has no physical ceiling

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Class trial rhythm sections add minor timing layer

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Item placement requires light spatial judgment but no precision

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Side-scrolling adventure controls require no dexterity

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Pointing and walking only

Both lean on execution about the same (2 vs 2). Biggest difference: optimization (5 vs 6) - Optimising battle chip builds and unlocking all story segments is the mechanical layer

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Point-and-click inputs only

Both lean on reads about the same (0 vs 0). Biggest difference: execution (2 vs 1) - Timed vote prompts create mild urgency but no skill ceiling

Both lean on execution about the same (2 vs 2). Biggest difference: reads (0 vs 1) - neighbor follows scripted routine, not adaptive

Both lean on execution about the same (2 vs 2). Biggest difference: optimization (5 vs 4) - Light environmental puzzles with gentle solutions