Skip to content

Adding a rune

Use this recipe when the word fits the current one-Verb + one-Noun command system. For full field descriptions, placement rules, and verification, see Making runes.

1. Check the design row

Confirm the word, type, supported combinations, and state behavior in Current Rune Type.

2. Create the word data

Create a RuneDataAsset in Content/Rephrased/Gameplay/Runes/Nouns/ or Runes/Verbs/.

Set:

  • RuneWord
  • EnglishDefinition
  • WordType
  • RuneVisualMesh

For a Noun, set Default Status and add one Rules row per matrix cell; see Adding a noun.

For a Verb, set Duration when it has temporary effects and add its rows to each noun it affects; see Adding a verb.

3. Add a world form

Create BP_RuneWord_<Word> as an AWorldRune Blueprint under Content/Rephrased/Gameplay/Runes/WorldRunes/.

Assign:

  • RuneData
  • Origin
  • visual mesh and glow materials
  • interaction, command, and deactivation ranges

For a noun rune, size CommandRange to reach the intended puzzle actors.

4. Add a drawn form

Open DA_RuneDrawingGraph and add an FRunePattern:

  • Rune: the word data asset
  • StrokeIds: the exact unique stroke set

Save and test that the intended set matches, extra strokes do not match, and the parked first word leaves room to draw the second.

5. Set up the puzzle

The objects a noun commands are puzzle devices: Blueprint children of ARunePuzzleActor in Content/Rephrased/Gameplay/PuzzleDevices/. On the puzzle:

  • set Noun on RuneableObject to the matching noun data asset;
  • leave Status empty to start in the noun's Default Status, or pick one of its states;
  • add a State Looks row per state and the Performances the rules call for;
  • place CommandCollision where the command orb can reach it.

See Adding a puzzle device for the full recipe.

6. Verify in PIE

  • Candidate glow appears on the nearest rune.
  • F activates the world rune.
  • E opens the tablet.
  • The drawn pattern activates automatically.
  • Verb + Noun works in either order.
  • The orb reaches every intended matching receiver once.
  • A state with no rule for the verb rejects without changing state.
  • The transaction and visuals clear when the orb finishes.

Run Rephrased.Rune.PROT001 and Rephrased.Rune.CORE009 when shared rune C++ or drawing behavior changed. Content changes still need PIE evidence and request_review before submission.

Change history

  • 2026-09-29 — Gabriel Li — Puzzle setup step uses ARunePuzzleActor State Looks and Performances.
  • 2026-09-29 — Gabriel Li — Updated word fields and Runes folder paths for noun rules (CORE-009).
  • 2026-09-17 — Gabriel Li — Replaced the recipe with the shipping data asset, world rune, drawing pattern, and runeable-object workflow.
  • 2026-09-10 — Gabriel Li — Marked this as the legacy slot/calculator recipe and routed new rune work to the Second Playable guide.
  • 2026-09-05 — Gabriel Li — Updated to the shipped hybrid Content structure (PR #19): PreProShowcase sandbox under Content/Rephrased/Levels/Prepro/, Art/Gameplay/Levels layout, Imports isolation, Content/Developers/<Discipline>/<Name>/ scratch space.
  • 2026-05-23 — Gabriel Li — Rune Showcase path; PIE spelled out on first use.
  • 2026-05-08 — Gabriel Li — Added baseline change history section for weekly wiki maintenance.