Most environment kits fall apart because no one wrote down what “on style” means. This lesson keeps you in 2D thinking for one session so Blender work in Lesson 2 starts from a shared compass—pillars, mood, camera targets, and a board you can literally glance at while modeling.

Lesson Objective

By the end of this lesson you will have:

1. A one-page art direction brief (plain text is fine) with three style pillars
2. A reference board (PureRef, Miro, or a single folder of images) capped at twelve key images
3. Three hero camera angles written down—the views your portfolio and vertical slice must survive

Step 1: Pick the fantasy in one sentence

Answer without naming shaders or polycounts:

“This environment should feel like [adjective] [place] built for [player camera height and pace] where [one memorable visual rule] is always true.”

Example: “A cozy cliffside trading post built for third-person over-the-shoulder where every roofline reads as a simple silhouette against the sky.”

That sentence becomes the north star when someone suggests photoreal gravel or ultra-dense clutter later.

Step 2: Write three style pillars

Pillars are decision filters, not adjectives spam. Each pillar must suggest what to remove as much as what to add.

Use this shape:

Mini challenge: Rewrite your table until each “reject” column names something you were tempted to do in past projects.

Step 3: Define forbidden looks

Forbidden looks stop scope creep. List three things your stylized kit will not chase in v1.

Examples:

• No photoreal scanned rock until the vertical slice ships
• No animated foliage in the first kit pass
• No interior rooms until the exterior reads in the three hero cameras

Post this list beside your reference board. When you want to add a fourth pillar mid-project, you negotiate with the list, not with your midnight energy.

Step 4: Build the reference board (max twelve images)

Quality beats quantity. Twelve strong images beat forty blurry Pinterest saves.

Include:

• Two master paintings or game shots that match mood (not necessarily genre)
• Two material close-ups that show how stylized surfaces handle edge wear and gradients
• Two modular kit examples (corners, trims, repeated walls done well)
• One orthographic or clear top-down if your game uses tactical readability
• One “bad example” labeled avoid so the team shares vocabulary

Exclude for now:

• ZBrush sculpt timelapses that do not match your poly budget
• Concept art with impossible camera angles unless you tag them aspirational only

Pro tip: Number each image on the board (R1–R12) and refer to IDs in Slack or notes (“Door trim should echo R7 edge treatment”). IDs beat “the blue one on the left.”

Step 5: Lock hero camera angles

Write three bullets:

1. Exploration camera — default gameplay height, FOV, and approximate distance to walls
2. Portfolio beauty shot — slower, slightly lower or wider framing for marketing stills
3. Stress camera — the meanest angle where silhouettes collapse (corner clutter, tight alleys)

You will light and optimize against these later. If a prop only looks good from the beauty shot, it is not shippable for the slice.

Step 6: One-page brief template

Paste into a doc and fill in:

Project codename:
Engine + render pipeline (Unity URP / Godot Forward+ / other):
One-sentence fantasy:
Pillar 1 / want / reject:
Pillar 2 / want / reject:
Pillar 3 / want / reject:
Forbidden looks (v1):
Reference board link or file path:
Hero cameras (3):
Primary scale anchor (door height / player capsule / grid cell):

Scale anchor preview: Lesson 2 assumes you already picked one real-world-ish height (often a door at ~2.1 m Blender units) so modular pieces snap predictably.

Troubleshooting

“Our references disagree with each other.”
Pick a tie-break pillar (usually silhouette or color). Demote conflicting images to “texture only” or remove them.

“Concept art is too painterly to model.”
Trace three orthogonal shapes from the concept (big masses only) and tag the rest as mood, not geometry targets.

“Stakeholders keep adding references.”
Gate the board—anything new requires removing an old slot until the slice ships.

FAQ

Do I need PureRef?
No. A dedicated folder plus a single PDF contact sheet works. Consistency of access matters more than the app.

How stylized is “stylized enough”?
If your normals and roughness could belong to any realistic game without changing albedo, you are still in default PBR land. Push shape language and gradient control first.

Should I pick Unity or Godot now?
Pick one primary integration target for scale tests; keep export naming engine-agnostic (ENV_Wall_A_2m beats WallStuff).

What if I am solo?
You are still two roles—art director yesterday and modeler tomorrow. The brief is how those two agree.

Recap and next lesson

You turned a vague “stylized environment” idea into pillars, forbidden looks, a capped reference board, and hero cameras. That is enough guardrails to open Blender without redesigning mid-blockout.

Next up — Lesson 2: Blockout workflow in Blender with scale sanity and composition-first layout so kit pieces snap to a grid you will reuse through the whole course.

Before you go: Bookmark this brief file path in your repo next to /art/brief.md or equivalent so audio and design can read it too. When you are ready for engine handoff vocabulary, skim Blender to Unity and Godot export pipeline—you will revisit it hard in Lessons 12 and 13.