Most of what Propsmith does follows from one decision: a model is a small program, not a mesh. You describe a prop in a sentence, an AI writes code that builds it from simple shapes, and the code runs to make the 3D model you see and download. This post explains how that works, what it’s good for in a game, and what it rules out.
What a model actually is
Each model is the body of a function that receives three.js (release r170) and returns the finished object. It starts with an empty group, sets up a few shared materials, adds the parts one by one and returns the group. Only three.js core is available: no imports, no network, no timers and no textures, not even generated ones.
The building blocks are few:
- Primitives: boxes, spheres, cylinders, cones, tori and capsules.
- Lathes: a 2D profile spun around an axis, for anything turned, such as vases, bottles, lamps and barrels.
- Extrusions: a 2D outline pushed into a solid, with a bevel when the edges should look soft.
- Tubes along curves, for handles, pipes and cables, or geometry computed point by point.
Materials are standard physically based materials with three settings that matter: colour, roughness and metalness, plus a glow for lights and screens. The traffic cone in our library is a good example of the scale of it: about 70 lines of code. Its base is a rounded square, extruded with a small bevel. The cone is a lathed profile spun 32 times around its axis, with a darker inside and two reflective bands that stand a hair proud of the plastic. The result is 2,028 triangles in six parts.
How the code is run and checked
On the site, the code streams in as the AI writes it, and a live viewer rebuilds the model after each complete statement, so you watch the parts appear. The finished code then runs in a sandboxed viewer page that can’t reach the rest of the app. The viewer measures the model’s size in metres and counts its triangles. If the code crashes, it shows the error and you can ask for a fix in a sentence. If a build fails outright, the credits go back.
The props in the public prop library go through more. A checker runs each one against the same three.js release and:
- rejects imports, network calls, DOM access, timers, textures and random numbers;
- fails a model with no meshes, broken vertex positions, or parts sunk below the ground;
- warns about models that float, sit off-centre, have unnamed or duplicate parts, use vertex colours (which the Roblox export drops) or go over 60,000 triangles.
Then it renders four views (front three-quarter, back three-quarter, front and side) with the size and triangle count printed on them, plus the thumbnail, using the same viewer the site uses. The builder looks at the renders, fixes what’s wrong and renders again, usually for two to four rounds. How we picked the props covers that process in more detail.
What code gives a game prop
Separate parts that can move
Every part has a name (leg_front_left, drawer_top_handle), and every part that could move sits in a group whose origin is its pivot. The treasure chest’s lid hangs from a lid_pivot on the back hinge line. The forklift’s mast tilts, its fork carriage slides up, and each wheel turns on its own pivot. Characters such as the zombie have pivots at the neck, shoulders, elbows, hips and knees.
That’s what makes animation from a sentence work. For “the lid lifts up and tips aside”, the AI writes a short function that turns lid_pivot over time. The viewer samples it 30 times a second into keyframes, so playback and every export show exactly the same motion. For Roblox, which only imports animation that drives the bones of a skinned mesh, the export gives each moving part a bone and bakes the motion onto the bones.
Modest triangle counts
Shapes use modest segment counts (16 to 32 around a cylinder), and a part is only as detailed as it needs to be. The library builds to a budget: 5,000 triangles for handheld items, 15,000 for furniture and everyday props, 40,000 for vehicles, buildings and characters. The median library model is about 9,300 triangles, and about a third are under 5,000.
Exact sizes
Models are built in metres, Y up, standing on the ground at the origin. “A square wooden crate about 80 cm on each side” gives a crate 0.8 m on each side, and every model page shows the size measured from the mesh. Import into Roblox Studio with Scale Unit set to Meter, or into Godot as is, and props sit at the right scale next to each other.
Edits that change one part
When you ask for a change (“make the lid gold”), the AI replies with small search-and-replace edits to the existing code rather than a new model. The lid’s material changes and everything else stays as it was, including the part names and pivots, so an animation you already built keeps working.
Rebuilds that come out the same
The code is stored with each version, and every export is made by running it. In the library, the checker rejects random numbers, so scattered detail, such as the uneven stones around the campfire, uses a random generator with a fixed seed and comes out identical every time. When a one-shot animation ends in a new state, that end pose can become a model of its own by running the animation to its last frame, without another AI call.
What it costs
- No image textures. Wood grain, rust, dirt and printed labels can’t be painted on; they have to be shape or colour. There are no PBR texture maps. That suits stylised games and doesn’t suit photorealism.
- No organic sculpts or realistic characters. Characters are assembled from parts, which is good for rigging and bad for faces and muscle. Fur and foliage need tricks: our builders learned that manes read as hair when made of tapered tubes, and that cones look like spikes.
- Natural shapes get heavy. The oak tree is 36,172 triangles, because a canopy made of clustered shapes takes a lot of them.
- No image-to-3D. You describe what you want in words; you can’t upload a picture.
- Code can be wrong. Sometimes it throws an error, or a handle lands a few centimetres off. The fix is another sentence, but it is a step a mesh generator doesn’t have.
Why we chose it anyway
Game props have jobs to do. A chest needs a lid that opens; a door needs a hinge in the right place; a pickup has to stay light because there will be fifty of them; a crate has to match the size of the player. A model written as code has those properties from the first build, because the hinge, the size and the part names are in the code. For the props a game needs most, we think that’s worth more than a photo-real surface. To see what that looks like across 60 real prompts, read Text-to-3D prompt examples.