Skip to content

Engineering wiki

Rephrased is a 3D isometric linguistic puzzle adventure where arranging ancient runes reshapes the environment. GDD is the design source of truth; this tab expands the Technical Design Document (TDD) for engineering.

New today? First day (engineering) — setup, compile, Rune Showcase PIE, weekly workflow. Do not start on systems pages until that is done.

Onboarding

Unreal basics — skip if you already know UE:

Rephrased project — open only if the current task needs it:

Designers and artists (scripted build): Building Rephrased

Setup & assistants

Environment installs and coding-agent workflows are on the Setup tab:

Wiki operations

  • Wiki maintenance — page metadata, change history rules, and weekly audit workflow.
  • Self-review workflow — say you are done in your coding agent (Cursor, Claude Code, Codex, Antigravity, or another MCP-capable IDE); optional Git hook reminder.

Systems

One page per TDD subsystem. Each lists files, what they do, public API, known constraints.

  • Rune system core — validator, executor, priority manager, event bus, redefinition manager, registry, strategies
  • Rune actors and placementARune, ARuneSlot and subclasses, ARuneCalculator, AExpandingRingActor, ARuneableObject
  • Effect componentsURuneEffectComponent base, the verb roster, history, attach/revert
  • Camera system — zone-driven gameplay framing and the cinematic showcase camera
  • Memory palaceAMemoryPalace, AMemoryOrb, UPlayerRuneKnowledge
  • Player and interactionARephraseCharacter, URuneCarryComponent, IInteractableInterface
  • Puzzle narrative devicesAClockDevice, AStarObservatory, the runeable-device pattern
  • Content pipeline — data assets, the Blueprint authoring layer
  • AudioAAudioManager today; FMOD path
  • VFX — Niagara usage, the multi-anchor fire pattern
  • UI / Menus — definition widget, HUD hook, menu roadmap
  • Save / Load — partial today (UPlayerRuneKnowledge save game); full level/state save not implemented

Reference

Step-by-step recipes for the things engineers extend most often.

Authoring (designer-facing)

  • Rune authoring — what designers configure on data assets, slots, calculators, runeable objects
  • Camera authoring — placing zones, blend modes, tracking, cinematic stack

Plan

Mirrors of the TDD's plan/risk/schedule sections. Engineers update these in place rather than touching the TDD between gates.

Devlogs

Conventions

Pages under wiki/ use front matter where noted: owner, status, last-reviewed. The lead development log uses the same three fields. Source citations use file paths only — no line numbers, they drift.


Back to Start here.

Change history

  • 2026-08-14 — Gabriel Li — Onboarding is First day (engineering) only; role tracks removed. Self-review blurb lists all team coding-agent harnesses.
  • 2026-08-13 — Gabriel Li — Self-review blurb points at MCP review gate, not named skills.
  • 2026-05-23 — Gabriel Li — GDD source-of-truth intro; onboarding first with PIE spelled out; role routes, First day, and Git workflow; glossary and Setup wording; lead DEVLOG front matter in conventions; onboarding nav split (Unreal basics + Rephrased project); removed Memory/GC page.
  • 2026-05-10 — Gabriel Li — Engineer onboarding and Self-review workflow linked; quick build guide linked from Setup (later moved to onboarding tracks).
  • 2026-05-09 — Gabriel Li — Engineering home lists Setup tab entry points (wiki/AI/Home.md, installers, assistants).
  • 2026-05-08 — Gabriel Li — Added baseline change history section for weekly wiki maintenance.