UE5 / Style Direction / Roadmap

Style Roadmap for UE5 Materials

A shared map for the material library's visual lanes: stylized, anime, cel shader, semi-realistic, and realistic. The goal is to keep one production structure while letting each style make different lighting, texture, and control decisions.

Library compass

Use before writing a new page

Pick the style lane first, then decide whether the work belongs as a recipe, core pack, production note, or asset-specific style page. That keeps the library from becoming a pile of unrelated shader notes.

01

Style Lanes

Positioning: this library is stylized-first, not stylized-only. Stylized thinking means readable shapes, authored controls, and deliberate tradeoffs. Realistic pages still belong here when they follow the same production discipline.

02

Decision Matrix

Question Does the page teach a reusable signal? Make it a Core Pack. Examples: UV motion, mask shaping, edge response, runtime control.
Question Does the page define a look? Make it a Style Direction page. Examples: anime/cel base, semi-realistic skin, realistic PBR rules.
Question Does the page build an effect? Make it a Recipe. Examples: portal, water, shield, terrain blend, wet surface.
Question Does the page solve a production problem? Make it a Production Note. Examples: face shadow maps, outline stability, sorting issues, perf limits.

03

Authoring Rules

1. Name the style lane in the first screen

Readers should know whether a page is stylized, anime, cel, semi-realistic, or realistic before reading graph details.

Why: the same node graph can be correct for one style and wrong for another.

2. Separate visual target from graph implementation

Start with what the material should read as, then explain the signal path. Do not let node order become the story.

Why: artists and engineers both need to understand the decision, not just the construction.

3. Keep controls tied to decisions

Expose controls like width, softness, intensity, speed, roughness bias, tint, and mask contrast. Avoid exposing internal math just because it exists.

Why: a Material Instance should feel like a small art tool, not a debug panel.

4. Leave image placeholders until the content is stable

Use a placeholder slot when the visual direction is known but the final image is not generated yet.

Why: image generation is easier once the page already says what the visual must prove.

04

Next Pages