Keep the world. Improve its surfaces.

What the list means

After terrain compilation, WorldWeaver identifies compatible ground, cliff, shoreline, route and greybox surfaces where applicable. This deterministic list does not run another AI generation or consume credits. It is a recommendation, not a list of missing assets that you must buy.

Water, foliage, spawn markers and your own project meshes are not generic PBR upgrade targets. A material changes a surface; it does not turn a village greybox into a finished building.

From needs to one combined pack

1. Weave and inspect your world. Check terrain, routes and sites before buying surfaces. Material Needs appears in the generated result, not in the empty prompt screen.
2. Select one to four useful surfaces. Review the suggested material briefs and edit them if necessary. You do not have to fill all four slots.
3. Request and review the quote. The server shows the exact credit amount for the selection and engine. Nothing starts until you confirm. Starter can inspect the list and quote, but generating the material set requires a paid plan and the integration to be enabled.
4. Review the completed run. A partial result means some materials failed; only successful materials are included, and failed bindings are not presented as applied. Check the run’s status before downloading.
5. Download World + Materials Pack. It contains your world, successful material maps and recipes, Landscape sources and the combined Python installer. You do not need to download a World Pack first or fetch a second standalone script.

Where the materials apply

The combined installer builds the world and assigns materials using WorldWeaver ownership and surface tags. Generated terrain layers use compiler masks; matching route surfaces and owned greybox pieces receive their finishes. Your project-authored meshes are not replaced.

Automatic layered terrain materials are designed for the generated StaticMesh terrain. A manually imported native Landscape needs its own layer/world-coordinate graph for the supplied masks. That route is not an automatic multi-layer material setup.

Credits and plan access

The world generation and optional material run are separate operations. Paid plans use the same credit charge for the same operation; their monthly credit allowances differ. The quote is the amount to review, not a guessed fixed pack price.

Your own API keys and AI subscriptions are supported in Cosindra Desktop only. Web products do not support them: they use Cosindra-managed AI and Cosindra credits, including on the BYOK plan.

Starter’s one free asset download is shared across products. It does not unlock paid material generation. Baseline world materials remain available without buying a material run.

Save your world, download your material files

A saved world does not preserve generated material files forever. MaterialForge maps have a 24-hour recovery window; download the combined ZIP while those files are available. A successfully downloaded complete ZIP is self-contained and does not expire.

Runs are tied to the world revision they were created for. Do not mix an old installer with a newly refined world or a different run’s material folder. Publishing a world does not automatically publish its private generated material files.