Case study / RHM: The Foundation

Direct the world.
Prove the build.

RHM required one production language across a third-person game, characters, artifacts, comics, music, and review tools. This breakdown shows how creative intent became gameplay contracts and inspectable evidence.

Role: Creative direction and systems architecture
Disciplines: Game systems, technical art, connected media
Public state: Steam listing live / release date TBA

1official gameplay trailer

5public Steam gameplay captures

3published connected comic issues

12characters compared at one technical gate

The assignment

Make a large world buildable without flattening its identity.

The production problem was not a shortage of ideas. It was preserving authored intent while making every system, asset, and release pass through a visible owner and an evidence gate.

01 / Frame

Lock the player contract

Movement, identification, routing, and extraction create the readable spine beneath the visual world.

02 / Separate

Give systems ownership

Canon, gameplay, components, zone assembly, technical art, and release proof remain distinct responsibilities.

03 / Verify

Show development truth

Gameplay footage, engine captures, topology comparisons, deformation tests, and public releases support the claims.

Playable evidence

The trailer is the system test.

The public footage puts navigation, player state, hostile readability, world effects, and objective communication in the same moving frame.

Official gameplay trailer

Move. Identify. Route. Extract.

The player contract becomes legible through compass direction, mission language, silhouettes, state color, traversal geometry, effects, and encounter timing.

Inspect the Steam page

Gameplay reading

Three frames, three production questions.

Each capture is labeled by the system it proves instead of being treated as decoration.

RHM traversal gameplay — TraversalCan the player read the route while moving?
Objective geometry, destination marking, and motion align in one action.

RHM player state gameplay — State languageCan the player distinguish self, threat, and uncertainty?
Color and silhouette preserve hierarchy under heavy effects.

RHM extraction gameplay — Mission flowCan the objective survive the enemy field?
HUD, compass, hostile density, and extraction language share the screen.

Technical art decision

Generation quality mattered more than an expensive remesh.

The pipeline compared source tiers, rigged results, topology, deformation, and engine handoff instead of assuming a familiar optimization step was helping.

Observed / measured / corrected

Do not manufacture detail after the source.

The remesh increased geometry without restoring missing form. The decision moved quality control upstream to generation and downstream to materials, outlines, rigging, and engine validation.

Hero sources were compared at a shared review gate.
Topology and weight behavior were inspected, not assumed.
Failed approaches remained documented as production evidence.

Public outcomes

What exists now.

No invented engagement numbers and no unreleased canon. These are the public or directly inspectable outputs available today.

GameSteam presence

A public listing, official gameplay trailer, and five gameplay captures.

NarrativePublished comics

Three connected RHM issues available through GlobalComix.

Technical artReusable review gates

Character, artifact, rig, deformation, and generation-tier comparisons.

ProductionTraceable systems