Building comparison
head to head
Going MedievalvsL.A. Noire
Going Medieval asks more than L.A. Noire, and the gap is optimization.
Going Medieval
Optimization · Systems & Chaos
Constructing and defending a medieval fortress colony through randomised events and deep production chains.
L.A. Noire
Optimization · Systems & Chaos
1940s detective procedural built around crime scenes and reading scripted interrogation tells.
Going Medieval leans Optimization (Systems & Chaos); L.A. Noire leans Optimization (Systems & Chaos).
Going MedievalL.A. Noire
Axis by axis
Execution1 vs 2
L.A. Noire leans a little harder on execution, though the gap is small.
Going Medieval
Pause-enabled management has no twitch component
L.A. Noire
Light shooting and driving, very forgiving
Reads0 vs 0
Same score on reads - which means the number cannot separate them. The difference is in what each one asks of you.
Going Medieval
Raider AI follows scripted attack patterns and frequencies
L.A. Noire
Suspects follow fixed scripts, never adapt
Variance6 vs 4
Going Medieval leans clearly harder on variance.
Going Medieval
Settler traits, weather, and plague events carry meaningful randomness
L.A. Noire
Interrogation tells and clues hidden until discovered
Optimization8 vs 5
Going Medieval leans clearly harder on optimization.
Going Medieval
Fortress design, food supply chains, and research order are richly solvable
L.A. Noire
Evidence chains and question choices have fixed correct answers
A matching score does not mean a matching test. Two games can both sit at 10 on execution and demand completely different things of you - which is why the reasoning above matters more than the number beside it.