Open-source project
tobspr-games/shapez.io avatar
tobspr-games/shapez.io

shapez.io keeps building while development has already moved on

shapez is an open source base building game on Steam inspired by factorio!

7,007 stars1,314 forksJavaScriptGPL-3.0

At a glance

What is it?
The repository behind the shape cutting game shapez still compiles, still documents its mods and still runs a Docker image, but its own README says development moved to shapez 2. It is a working codebase with a maintenance notice attached, which is a different thing from a live project.
Who is it for?
Fork this repository if you need the shapez 1 code and can supply your own maintenance: it builds from source today, ships sample mods, and keeps its assets in an atlas pipeline. Do not expect new features, since the last tagged release was 1.5.1 on 2022-03-05 and the README redirects contributors elsewhere.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 69 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • tobspr-games/shapez.io7,007 ★ · +31
Star history
Repository2026-09-232026-11-15
tobspr-games/shapez.io7k7k

31 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The README hands development over to shapez 2

The top of the README announces that shapez 2 is available on Steam with multi-layer factories, better performance, trains and fluids. Further down, the contributing section states plainly that this repository is no longer actively maintained because the work moved to shapez 2, and points contributors at a separate Community Edition repository for ongoing work. The release list tells the same story from the other side: the newest tags are 1.5.1 from 2022-03-05, 1.4.3 from 2021-08-28 and 1.3.0 from 2021-05-14. The last push to master was 2026-09-07, so commits still land, but no release has followed them in more than four years.

Four prerequisites before gulp serves anything

A source build needs `ffmpeg` on the path, Node.js 16 with Yarn, and a Java runtime for the texture packer. Once those are in place, run `yarn` in the root folder; the entry point is then the gulp folder, and the documented sequence is:

bash
cd gulp
yarn
yarn gulp

The browser opens when that finishes. The same work runs in a container, since the Dockerfile starts from node:16 and exposes two ports:

dockerfile
FROM node:16

EXPOSE 3001 3005

Node 16 is not an accident of the docs: the Dockerfile pins the same runtime, and the repository also carries .travis.yml for continuous integration and .gitpod.yml for a cloud workspace.

gulp produces a debug build, and config.js is the switch

What the build gives you is not what a player gets. Running gulp produces a debug build with several debugging flags enabled, and turning them off means editing `src/js/core/config.js`. That is the whole configuration surface: the top level of the repository holds no environment file and no settings document, and no command line flag for the build is described. For anyone forking this, that single file controls the debugging flags, so it is the first thing to read before changing anything under `src/js`.

An ES5 engine shared with YORG.io, with forEach kept out of hot loops

The engine is custom, and by the project's own account it shares almost the entire core with the YORG.io 3 engine. The reasoning about code style is unusually concrete. The project is based on ES5; some ES2015 features are used, but most are avoided because they are too slow once polyfilled. `Array.prototype.forEach` is confined to non critical loops because a plain for loop is faster. The same paragraph separates the engine core, described as relatively clean, from the game code layered on top, described as hacky. That is a usable map for a newcomer: the engine is the part to trust, the application layer is where the damage is.

GitHub records GPL-3.0 while package.json says MIT

The license question has two answers inside the repository. GitHub records GPL-3.0 for the project, and a LICENSE file sits at the top level beside CONTRIBUTING.md and a CONTRIBUTORS list. The root manifest disagrees:

json
"name": "shapez.io",
"license": "MIT",
"private": true,

That combination, a private package pinned at version 1.0.0 with an MIT field, looks like an internal manifest for the web build rather than a distribution decision. Anyone vendoring or relicensing this code has to settle the conflict against the LICENSE file itself, not against the package metadata.

Itch pushes run through butler, the Steam upload runs through a batch file

The release scripts show the shape of the distribution. The Itch.io uploads are butler invocations that read the version from the `version` file in the repository root:

bash
yarn publishOnItchWindows

The Steam path is a Windows batch file:

bash
yarn publishOnSteam

which underneath runs `cd gulp/steampipe && ./upload.bat`. The tree also carries electron_gog/ and electron_wegame/ next to electron/, so each storefront has its own shell, and `yarn publish` chains the Itch uploads, the Steam upload and a web deploy through `cd gulp && yarn main.deploy.prod`. None of this is written up as steps you should follow. It is the record of how the maintainers shipped, and its middle is Windows shaped.

Type declarations are extracted from plain JavaScript

The tooling is thin and entirely script driven. Linting is `eslint src/js`, formatting is `prettier --write` over `src/**/*.*` and `gulp/**/*.*`, and the check named `tslint` is really `cd src/js && tsc`. The interesting entry is `buildTypes`:

bash
yarn buildTypes

Underneath it runs `tsc src/js/application.js --declaration --allowJs --emitDeclarationOnly --skipLibCheck --out types.js`, so the declaration file is extracted from JavaScript sources instead of being maintained by hand, which is the usual answer for an ES5 codebase that refuses a rewrite. Config files follow the same spare style: .eslintrc.yml, .prettierrc.yaml, .editorconfig and .yamllint. The scripts block holds no test entry, so the compiler and the linter are the whole definition of a passing build.

Mods have a site and a folder, translations have neither

Mods are the part of this project with an ecosystem still attached. The catalogue lives at shapez.mod.io, and the documentation for writing them is in the repository under `mod_examples/`, which ships sample mods to read next to the game source. Translations get less attention: the pointer goes to `translations/README.md`, and the same paragraph says new translations are not being reviewed. The machinery still exists, since `sync-translations.js` sits at the root and is wired to `yarn syncTranslations`, so the gap is in review rather than in tooling. Asset work is automated in the same spirit: changes are rebuilt into the atlas automatically, a contribution credited to dengr1065, and most of the artwork lives in a separate repository.

Editorial conclusion

Fork this repository if you need the shapez 1 code and can supply your own maintenance: it builds from source today, ships sample mods, and keeps its assets in an atlas pipeline. Do not expect new features, since the last tagged release was 1.5.1 on 2022-03-05 and the README redirects contributors elsewhere. Check the LICENSE file against the MIT field in package.json before you redistribute any of it, and expect to run Node 16 with ffmpeg and Java present.

Frequently asked questions

What is shapez io?

shapez is an open source base building game inspired by Factorio, and its stated goal is to produce shapes by cutting, rotating, merging and painting parts of shapes. This repository holds the game source, with a Steam release, an online demo at shapez.io and an official Discord linked from the README.

Is shapez 2 still in development?

The README says shapez 2 is out on Steam with multi-layer factories, better performance, trains and fluids, and that development of this repository moved to shapez 2. For ongoing work on the original game it points contributors at the Community Edition repository.

How do I add mods to shapez io?

The mod catalogue is at shapez.mod.io, and `mod_examples/` in the repository carries sample mods plus the documentation for creating them.

shapez io vs factorio

The project describes itself as a base building game inspired by Factorio, and its own goal statement is about producing shapes by cutting, rotating, merging and painting parts. Beyond that description the repository makes no feature by feature comparison, and it points readers to shapez 2 for the current version.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. tobspr-games/shapez.io on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tobspr-games-shapez-io.svg)](https://hysenlabs.com/projects/tobspr-games-shapez-io)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tobspr-games-shapez-io.svg)](https://hysenlabs.com/projects/tobspr-games-shapez-io)

Was this useful?