What is inside the .blend, and why it ships

An export is a flattening. FBX and GLB carry the mesh as it stands the moment you press the button: modifiers applied, history gone, hierarchy collapsed, materials translated down to the lowest common denominator. That is exactly what an engine wants, and it is useless for picking the work back up.

The .blend is the workshop itself. It holds the object, and it holds how the object was made — and it is the second part that lets you take it apart.

Modifiers are left live

Nothing is applied. The mirror, the subdivision, the solidify on the drapery are still in the stack with their settings. Drop a subdivision level for a mobile target, break the symmetry on one side of the face, thicken a fold — without starting from frozen geometry.

On a flattened file, the same edit means rebuilding what was destroyed. That is usually slower than sculpting it again.

Collections are named, and they separate what should be separate

This is not decorative tidiness. On Bramée, the antlers live in their own collection, parented to the skull but independent of the mesh: detach them, lengthen them, break one, and the rest of the bust does not move. That separation does not survive an export — in the FBX, the antlers are geometry among geometry.

It is the difference between buying a character and buying a character you can change. The price is the same.

UVs are unwrapped by hand, and you can see the seams

The unwrap is done by hand, with seams placed where the eye does not go: under the jaw, in the nape, behind a fold. Opening the .blend shows you where they are — which matters the day you want to repaint an area, rebake a map, or change the resolution of one island.

An automatic unwrap gives you islands that are correct and unreadable. You find out when you go to touch up a texture, which is to say too late.

One material, and a node tree you can read

Pieces ship with a single material and one set of 2K PBR textures packed as ORM. The node tree is a handful of named nodes — not a thicket of anonymous mix nodes inherited from a tutorial. You can follow what feeds what, and replace it.

ORM packing, and how it translates between engines, has its own note. This one stays on the file.

What the .blend does not contain

Worth stating plainly: there is no animation rig. Flash pieces are static busts, the spec sheet says so, and a skeleton dropped onto a bodiless bust out of politeness would serve nobody. There is no separate high-density sculpt either — the maps are baked, the working version stays at the studio.

A commission is the right frame for a rigged character, or for receiving the high-density sculpt. It is not what €80 covers, and pretending otherwise would do a disservice.

Why the file ships at all

Because withholding it would serve one purpose: forcing you to come back. That is a way to sell. It is not this one. A studio that can open, modify and rebake a piece it paid €80 for is a studio that knows what it is buying the next time.

The non-exclusive licence sets out what you may do with the file once it is open — and the one limit that counts: it is what you build your product with, not the product.