FAQ — shapez 2 Factory Wiki
Short answers first, deeper guides linked from the homepage. If you want official sources, start with shapez2.com and the Steam store page.
Using this wiki effectively
Factory games are personal: your favorite layout style might differ from mine. Treat any guide as a set of experiments — try it for 30 minutes, keep what reduces confusion, discard what does not fit your brain.
What this site is (and isn’t)
This is a player-written companion meant to reduce friction: clearer mental models, fewer dead ends, and practical debugging habits. It is not a replacement for experimenting in-game, and it is not an official source of patch-perfect numbers.
If you only read one troubleshooting method
Use the “first backup upstream” walk: pause, find the first congested belt, then walk backward until you discover the first machine that cannot clear an output. Fix that single choke, unpause, and repeat. Most “mysterious” factory stops are a chain of small blockages, not one cursed building.
Mods, blueprints, and saves
Community tools can be amazing, but they add variables. If you are troubleshooting, test in a clean mental state: know what changed last (a new import, a new mod, a rebuilt hub), and undo one change at a time.
How to search this site (without a built-in search box)
Use your browser’s page search on the guide that matches your topic, or start from the homepage cards and follow the internal links. If you are trying to solve a stall, start at Buildings & Machines; if you are trying to read shapes, start at Shapes & Colors.
Community tier lists
If you want a lightweight way to rank modes, milestones, or achievements for discussion, use Tier List Maker.
If you think something here is wrong
Treat guides as living notes. The game can change, and player language evolves. The best sanity check is always: reproduce the behavior in-game, screenshot the target, and compare with the guide’s mental model — not with your memory of last month’s run.
Trademarks & credits (plain English)
shapez 2 and related trademarks belong to their respective owners. This site is an independent fan resource and should not be taken as an official statement from developers. If you are creating your own fan site, the usual norm is: credit the game clearly, do not imply endorsement, and link to official pages for purchases and announcements.
Accessibility & comfort
If long sessions hurt your hands or eyes, tweak settings early: breaks matter, and factory games reward consistency more than marathon bursts. A sustainable playstyle beats a heroic weekend that makes you avoid the game for a month.
Returning after months away
Your past self was smarter than you think — but also messier than you remember. Treat a stale save like onboarding: relearn the bus lines, rename districts in your head, and fix one bottleneck per session. It is okay to build a “temporary bypass” line while you plan a bigger rebuild.
Glossary mindset
Factory games throw a lot of nouns at you. You do not need to memorize all of them. You need a small working vocabulary: extract, transform, transport, buffer, merge/split, paint, deliver. Everything else is a specialization of those verbs.
A tiny vocabulary cheat sheet (non-exhaustive)
- Trunk line — a main belt/pipe path you try not to tangle.
- Module — a compact block that does one job with obvious I/O.
- Buffer — temporary storage that absorbs bursts so machines do not stall.
- Throughput — how much stuff moves per minute in steady state.
- Bottleneck — the slowest step that limits everything upstream.
When you are stuck, try to name which word above matches your problem. Naming the problem class is half the debugging battle. Stay curious.
If you are trying to teach a friend
Teach one concept at a time: first movement, then splitting, then a simple transform, then paint. Do not demo a mega factory on hour one unless they asked for chaos as entertainment. The best “tutorial” is often two saves side-by-side: yours as reference, theirs as hands-on.