LOR a world where the chemistry is the language, and the language builds everything

Imagine Minecraft or Roblox, but with one radical difference: every new material, machine, creature, and item is invented inside the game — not by writing external code or installing mods, but by combining things that already exist in the world. The joy of LOR is building, and beneath building sits creation: the making of genuinely new things.

To make creation lawful rather than arbitrary, the world is built from a fixed alphabet: 64 elements, borrowed in structure from the 64 hexagrams of the I Ching. Everything above them — a shirt, a tower, a dragon, a player — is a composition of a handful of these elements, laid out in space. There is no giant gap between the atoms of this world and its objects, the way there is between quarks and chairs in ours. An object is always just one step away from its vocabulary. That single commitment is the spine of everything below.

Section 01

The two layers, and the great inversion

Early on, we built LOR physics-first. Elements had behaviours derived from their structure; heat and charge flowed through fields; matter aged and transmuted on its own. It was a beautiful, self-consistent machine. We even built working simulations of it.

Then came the inversion, and it's the most important move in the whole project. We realised the game doesn't live in its physics — it lives in the things players make and how they interact. So we flipped the teleology. Instead of elements deriving their meaning from the axes, the meanings are hand-authored, and the elements become something closer to words in a programming language. Some are nouns (substances). Some are verbs (actions). Some are grammar (if, when, repeat). An item is a small program written in these words, and its layout on the ground is the source code.

This is not a retreat from the I Ching — it's a closer reading of it, as the next section explains. And it's the reason the design now has two firm layers and one still-molten one:

The guiding principle across all three: no side-channels. If an idea needs a hidden parameter, a metadata tag, or a special case bolted on outside the 64, it's suspect. The whole thesis is that everything reduces to elements a player can find and combine. A creature's colour, its allegiance, its shape — all of it should be testimony of what it's made from, not a setting on a form. This is the sharpest blade we own, and we use it to test every new idea.

Section 02

What we take from the I Ching — and what we don't

The I Ching gives us three things we keep, and several we've set aside. Being honest about which is which matters, because it's easy to over-romanticise the source.

What we keep

The 64 as a fixed, structured alphabet. Six binary lines give exactly 64 hexagrams. Eight trigrams (three lines each) combine in pairs to form them. That combinatorial skeleton is real and load-bearing: a player who learns the eight trigrams can half-guess an unfamiliar element, which is the perfect amount of guessability — enough to reason, not enough to remove discovery.

Meaning authored on top of structure — which is how the I Ching itself works. The classical text does not derive each hexagram's meaning mechanically from its trigrams. The trigrams inform (Thunder-below-Mountain suggests movement checked by stillness), but the received text then hand-assigns each hexagram a rich, specific judgment. That is exactly our model: structure suggests, human curates. When we went looking for which hexagram should mean "the loop," the tradition kept handing us gifts — 24 Return is literally the turning-point; 42 Increase is multiplication; 50 The Cauldron is the vessel of transformation.

Changing lines as transformation. In a real I Ching casting, a hexagram comes with moving lines that transform it into a second hexagram. This is not decoration we added — it's the oracle's own core notation, and it became our transmutation mechanism (Section 05).

What we've set aside

We are not doing divination, fortune-telling, or the philosophical/moral content of the hexagrams. We're not bound to King Wen's ordering (it's display-only). And critically, we've shelved the idea that the four axes (the opposing trigram pairs, which we'd called things like Heat and Charge) do any mechanical work. They began as the engine of a derived physics. Once meanings became hand-authored, the axes stopped computing anything — they survive now only as flavour, as the visual logic of the glyphs, and as a general design instinct: everything comes in trade-off pairs, there are no god-mode stats. That instinct is precious and stays. The machinery is dormant.

honest gap  There's a vacancy shaped like the axes, though. Our grammar quietly assumes quantities exist — a tower SENSEs a value, an IF compares against a threshold. What are the units of this world? What does a tower actually measure? That's the door through which the four axes might one day return: not as physics, but as the measurable quantities the verbs operate on.

Section 03

What we take from other games

LOR is not being invented in a vacuum. Several existing games have already solved pieces of this puzzle, and each teaches one clean lesson.

strong fit  The convergence across all six is striking: they were all designed by extracting primitives from desired artifacts, not by designing primitives in the abstract. Nobody designed the Humanoid first and looked for a use. That's our method too (Section 04).

Section 04

The first elements

Rather than define all 64 in the abstract, we worked backwards from the things we want to build: player, clothing, creature, tower, spawn point, energy crystal. We wrote each as a plain-language recipe as if the elements already existed, then harvested the vocabulary that recurred. The rule: an element earns a slot only if it appears in at least two target items — otherwise it isn't a primitive, it's a one-off recipe.

That harvest yields about 22 elements in four groups. The other 42 slots stay deliberately dark — that's discovery space.

partial  These assignments are suggestions. Some are near-certain (LIFE 27, the Cauldron trio, REPEAT 24). Two — MOVE 35 and IF 60 — are the softest calls, listed with alternates. The mapping is the last thing to harden, not the first.

Section 05

The casting table

Here's the idea that ties the alphabet to the world: the ground is the casting table, and the layout is the source code. You don't open a menu to build. You lay elements and items on the ground in a pattern, and the pattern is the recipe. Substances form the body; operators trail off it in a reading-line like a rune-sentence. Cast it, and the geometry collapses into the finished item — the ground was the source file, the flash is the compile. The ground type underneath matters too, so some things can only be made in certain places.

A tower, written in elements, each line owned by one element:

Remove the IF and it shoots everything; remove STORE/DRAW and it becomes a god-item — which is why the grammar makes cost structural, not a stat someone forgot to balance.

The transmutation recipe — a special order

Most recipes make items. One recipe makes elements from other elements, and it's rare and low-level by design. Place the Cauldron at the head; extend a row of six SAME/CHANGE markers from it; place the element to be transmuted at the end. Each marker says whether that line holds or turns. The result is the masked flip — any element can, in principle, become any other. This is the shelved changing-lines physics reborn as a deliberate, invoked, priced operation instead of an ambient one.

Section 06

What's on the shelf (not the bin)

Several richly-developed ideas were set aside during the inversion. None were thrown away — each solved a real problem and may return. Naming them keeps us honest about what we're not currently committed to.

The tools built during the physics era — a kernel simulation, a 64-element periodic table, and an interactive "Graph of Changes" — are all preserved in the repo. The periodic table and the Graph, in particular, are poised to come back: the table as the element-authoring canvas, the Graph as the atlas of what the transmutation recipe can reach.

Section 07

What we should call complete

A note on the criterion, because it's unusual and it's the user's own: completeness is measured by how much else an idea permits. The more concepts an idea leaves room for, the more complete it is. The more it contradicts other things we want, the less complete — no matter how polished it looks. By that test, these have earned the name. They are the load-bearing walls; build on them with confidence.

Everything else — the specific hexagram assignments, the fields' return, the units of measurement, whether SENSE and IF stay split (current lean: yes), the exact transmutation costs — is partial or open, and should be held loosely.

Section 08

Where the disparate ideas could meet

No right answers here — these are propositions, ways the scattered threads might fuse into something whole. Each takes ideas that currently sit apart and proposes a join.

These four don't have to all be true. But notice they reinforce rather than contradict — which, by our own completeness test, is the sign they're pointing somewhere real. The through-line: author, then let it live; make nothing you can't read; measure everything in a few shared units; and call it all discovery.