Manage and generate game studio materials with ReBlink Matter

Studio material libraries are difficult to search when their meaning is buried in filenames, folders, and individual memory. A name such as plaster_07_final says little about the surface, its style, or where it belongs in a project.

Generation tools address a different part of the problem. Most of them produce new maps. They do not manage the library the studio already has, and they leave the shader work to the artist.

ReBlink Matter brings these tasks together. It helps studios discover, generate, and refine engine-native materials, textures, and shaders while grounding the work in the studio library. Teams can use natural language to find existing materials, create derivatives, or generate new materials with the shader logic needed to make a surface move, react, and change.

Manage the studio material library

Matter indexes the studio library as material records that can be inspected, retrieved, refined, and used as the basis for new work. This reduces dependence on filenames as the main source of context.

A file called plaster_07_final may be useful, but its name does not fully describe its appearance, behavior, project style, or production role. Matter makes library contents discoverable by their material meaning rather than requiring artists to know the exact file or folder name.

Studios can establish a trusted collection of existing materials, textures, and shaders. Matter uses that collection as production context when searching, generating, and refining materials.

Artists can also drag in a material, shader, or texture to inspect it, annotate it, or create a derivative. This brings existing work into the same process as generated work instead of separating the library from material creation.

Search materials by meaning

Matter supports natural-language search across indexed material records. An artist can describe the surface they need instead of guessing how someone named or stored it.

Search can account for the project’s realism, lighting, stylization, and palette. These settings give Matter project context when it retrieves existing work or helps create a related material.

The result can be used directly when it already fits the need. It can also become a starting point for refinement or a derivative. Search is therefore connected to production work rather than limited to finding a file.

Retrieve existing work

Retrieval brings a suitable material, texture, or shader back into use. Matter can identify relevant assets from the studio library and return them as editable, engine-native materials.

This makes existing work easier to reuse across a project. It also helps teams work from trusted material records rather than recreating a surface because its source was difficult to find.

Retrieval is distinct from generation. If the library already contains an appropriate material, Matter can surface it. If the material is close but not complete, the artist can refine it or derive a new version.

Derive materials from trusted sources

A derivative begins with an existing material, shader, or texture and changes it for a new production need. Matter keeps that work connected to its source in the studio library.

An artist can start with a known material and adjust its textures, parameters, or shader behavior. The derivative can follow the project’s established realism, lighting, stylization, and palette while changing the parts required for a particular scene or effect.

This connection helps prevent the new version from becoming an orphan with no clear relationship to the trusted collection. The source and the new production material remain part of the same material workflow.

Generate new materials and shaders

Generation is a first-class capability in Matter. It is not limited to situations where search returns no starting point.

Material Chat is the in-engine surface for prompting a new material or editing an existing one. An artist can describe a result such as:

Flowing magma, with cool patches of rock flowing over it.

Matter can use that request to generate the textures and functional shader behavior together. The material can then be refined through further language or parameter changes.

The same process can create new textures, surfaces, and shaders for effects such as cracked lava, an energy grid, atmosphere, or plasma. Because Matter is project-aware, generation can follow the studio’s selected style, lighting, stylization, and palette.

Shader generation is an uncommon material capability

Textures describe a surface. Shaders define how it behaves.

A set of texture maps can describe color, surface direction, roughness, and metallic response. It does not by itself define flowing magma, an animated energy grid, a dissolve, a force field, fire, plasma, or another changing surface. Those effects require shader code, render logic, parameters, and a connection to the material used by the engine.

Map generation is common. Shader generation as a production material, checked in the target engine and connected to the studio library, is not. Traditional shader graphs and material editors still require a person to author the behavior. Some experimental plugins and text-based systems can build material graphs, but they do not also serve as a studio material library for search and management.

Matter generates textures, shader code, render logic, and a wired material instance together. The result is one usable, engine-native artifact rather than a folder of loose images. It can produce procedural, animated, and adjustable behavior for surfaces such as cracked lava, magma, energy grids, atmospheres, plasma, dissolves, force fields, and fire.

Generated shader code is validated against the target engine. Matter starts in Unity and uses a portable representation intended for the other engines a studio uses. This supports engine-aware output without treating a material as a fixed set of maps.

Artists can refine generated behavior through language or parameters and edit the shader logic in place. When an idea changes, they can revise the material instead of rebuilding the shader and its connections from the beginning.

Check and refine materials in the engine

Matter checks generated shader code against the target engine. Artists can inspect the material in its production environment, refine its appearance or behavior, and edit its logic without separating the generated maps from the shader that uses them.

The material remains editable after generation. Parameters can be tuned, language instructions can revise the result, and shader logic can be changed in place. The wired material instance stays connected to its textures, code, and render logic throughout this process.

Keep material work connected to production

Matter combines indexing, retrieval, derivation, generation, checking, and refinement around the studio material library. Existing materials can be found and reused. New work can begin from a trusted source or from a prompt. Generated materials include the shader behavior required by the engine, not only the texture maps.

This keeps search, library management, material creation, and in-engine refinement connected to the same production process.