OPEN TO BUILDERS, ARTISTS & EXPLORERS

Make the world
more alive.

Terrain Lab grows through small, reviewable contributions. Bring a species to life, shape a new world, improve the projector workflow, or make the guide clearer.

There is room for every kind of maker.

Open an issue for a world, creature, motion, terrain reaction, performance fix, accessibility improvement, bug, documentation change, or physical rig finding. A screenshot or short recording helps others understand visual issues. For a larger feature, discuss the approach in an issue before building it so contributors can coordinate.

Useful entry points: animal extension guide, sandbox integration contract, and field guide.

From idea to pull request.

  1. Search existing issues; open a new one if the idea or bug has not been discussed.
  2. Fork the repository, create a focused branch from current main, and make one coherent change. Keep generated screenshots and local model downloads out of your commit unless they are part of the contribution.
  3. Run the checks below. Test visual work in the browser, including the integrated sandbox. For projector or Kinect changes, describe the rig and calibration used.
  4. Open a pull request against main. GitLab calls the same review step a merge request. Link the issue, explain behavior before and after, and include screenshots or a short recording for visual changes.

A draft pull request is welcome for early feedback. Mark it ready when the change and checks are complete.

Try it on your machine.

git clone https://github.com/YOUR-USERNAME/terrain-lab.git
cd terrain-lab
npm ci --prefix standalone-animal-demo
npm test --prefix standalone-animal-demo
node scripts/build-site.mjs
python3 -m http.server 5180 --directory _site

Open http://localhost:5180/, /sandbox/, and /wildlife/. The sample landscape and projector preview work without a Kinect. If Chrome is installed, npm run test:site --prefix standalone-animal-demo checks site links and browser interactions. A live sensor or projector change also needs a physical rig check; document what you could verify.

How a change lands.

The pull request template asks for the behavior, test evidence, visuals, and asset credits. Automated checks build the site and run simulation tests. A maintainer reviews scope, integration with the sandbox and projector, readability, performance, and provenance, then may request changes. After approval, a maintainer merges into main; GitHub Pages publishes from that branch through the deployment workflow. Contributors can follow the pull request and deployment status on GitHub.

Prefer small branches. If another pull request changes the same area, update your branch from main and resolve conflicts before merge.

Keep every asset traceable.

Only submit models, sprites, textures, sounds, or reference-derived work that you have the right to share. Record creator, source URL, license, required credit, and modifications alongside each new asset. Avoid bundling downloaded libraries or unlicensed movie/game artwork. For wildlife, follow the asset and animation layout and update attribution.

The repository also has a contributor checklist and issue forms for proposing work.

Easy to use, clear to credit.

Original Terrain Lab code and documentation use the MIT License. You can use and adapt them while keeping the copyright and license notice. Models and bundled libraries can have different terms; check the license scope and asset credits before reusing them. Code contributions are accepted under MIT, while each contributed asset keeps its documented license.