Rules

Eldiron rules are documented from five perspectives.

Editing Your Ruleset

Read Ruleset Nodes for the Creator workflow: changing values, adding or removing definitions, replacing icons, editing particle effects, and restoring the original ruleset.

Official Rules

Read Official Rules if you want the rulebook view: races, classes, attributes, combat, weapons, spells, progression, visuals, and the future crafting model.

This is the player-facing and creator-facing gameplay guide.

Rules In Eldiron

Read Rules In Eldiron if you want the implementation view: where the ruleset nodes live, how they are compiled, how Game / Rules edits definition branches and restores checkpoints, how item templates are created, and how to test rules from the terminal or Creator console.

Ruleset Contract

Read Ruleset Contract for the target public ruleset architecture: official, derived, and standalone rulesets; optional modules; canonical data ownership; composable effects; packages; assets; migrations; and documentation synchronization.

Ruleset Capability Audit

Read Ruleset Capability Audit for the implementation baseline. It distinguishes rules that are complete, functional, partial, catalogue-only, or missing across runtime, Creator, validation, tests, and documentation.

Short Version

New projects use the bundled eldiron.official ruleset by default.

Game / Rules opens a node editor with one selected definition branch at a time. Projects own their current nodes and preserve their original ruleset for restoration. This initial implementation uses full owned rulesets; inherited node deltas and upgrade workflows remain future work.

During ruleset development, test_projects/Hideout2D.eldiron follows the current representation. The starter copy remains frozen for the released version and is replaced from the tested project only as part of a release.