Frequently asked questions
Short answers. Where something is not decided yet, we say so.
Buying
Is the kit for sale?
Yes. The Stylized Town kit costs $39, paid once. See pricing.
Is there a subscription?
No. The kit has one price ($39), paid once. Nothing renews and nothing is charged again.
Which updates does a purchase include?
Updates: 0.4.0 and every later version below 1.0.0. A released version never changes: an update is a new version with its own quality report.
What is the refund policy?
The refund policy explains when and how. You can send a request from the support page; a refund closes the downloads of that purchase.
Do I need an account?
Not for the free sampler. Buying the kit and downloading it later need an account: you sign in with a link sent to your e-mail address, without a password.
Licence
Can I use the assets in a commercial project?
Yes. Use and modify the assets in your own games, sites and apps, ship them inside compiled or deployed products and client work; no redistribution of the asset files themselves. Read the licence.
Can I modify the assets?
With the SDK you change what each asset declares (colours, swappable parts, optional parts, uniform scale) per instance, in the browser. 8 of the 30 assets declare such options, 25 in total: see what you can change, asset by asset.
Can I redistribute or resell the files?
No. You may not share, publish or resell the asset files on their own, modified or not.
Were the assets generated by AI?
The quality reports of 30 of the 30 assets record that no AI model contributed to the asset, and 30 record no third-party inputs: the assets are built by scripts from parameterized recipes. Each report lists the checks.
Technical
Which Three.js versions are supported?
The kit is tested with three 0.186.1 and SDK 0.5.1. With another three version the CLI still installs the kit and warns that the version is untested. The GLB files need no decoders.
Do I need Blender?
No. Installing the kit, customizing what the assets declare, assembling scenes and verifying them all run on Node.js and a browser. The kit does not include Blender source files, and geometry changes such as extra storeys or another roof pitch are not part of it.
Do I need the MCP server?
No. An agent connected to our MCP server discovers the kit through read-only tools. An agent without it reads the installed kit files and uses the CLI. Both paths were exercised in recorded trials: see MCP setup.
Which browsers and devices are supported?
The quality renders and the demos run in Chromium with WebGL 2, on desktop. Other browsers have not been tested, and nothing has been measured on phones or tablets, so we make no claim about them. Without WebGL the demos show a render and an explanation.
How do I get the SDK?
The SDK packages come as tarballs, not through the public npm registry. The quickstart shows where they go in your project.