Elden Ring: Systems Within Systems

I spent 120 hours in Elden Ring. As someone who thinks about system design professionally, I couldn't stop noticing the engineering underneath the art.

Emergent complexity

The genius of Elden Ring is that its rules are simple but their interactions are not. Every weapon, spell, ash of war, and enemy obeys consistent physics. But the combinatorial explosion of "what happens when these three systems overlap" creates situations the designers never explicitly authored.

This is exactly what good software architecture aspires to: simple primitives that compose into complex behavior without special-casing.

Difficulty as feedback

When you die in Elden Ring, you always know why. The game never feels unfair — it feels demanding. There's a software parallel: the best error messages don't just tell you something went wrong, they tell you what to do about it. Elden Ring's difficulty is an error message that says "try a different approach."

The open world problem

Most open worlds feel empty. Elden Ring's doesn't, because every landmark is visible from everywhere else. You can see the Erdtree from the starting area. You can see Stormveil Castle from Limgrave. Sight lines create structure in unstructured space.

In UI design, we call this "progressive disclosure." Show the user enough to orient themselves, then let them explore. Elden Ring does this at continental scale.