Skip to content

A grid-first operating system for ComputerCraft: Tweaked

Get started

Install Lattice, then build your world as a grid.

This page is the “what to do first” guide. It assumes you already have ComputerCraft: Tweaked available (e.g. via AllTheMods 10).

1) Start with an Advanced Computer

Lattice targets ComputerCraft: Tweaked. You’ll get the best experience on an Advanced Computer (better display + color).

2) Run the installer

The installer bootstraps the system and pulls packages using the repo manifest. Keep the endpoint stable for copy/paste.

3) Expect structure

Lattice favors explicit layout, predictable paths, and composable parts. If you’re used to “one big script,” this will feel different — on purpose.

4) Add capabilities as packages

Install only what you need. Think drivers, services, utilities, and shared libraries — designed to compose cleanly.

What you’re installing

Lattice is intentionally not one giant program. It’s a foundation of smaller pieces that can be composed:

  • A minimal bootstrap flow
  • A shared library grid (reused across nodes)
  • A manifest-driven package repository
  • A base for automation, monitoring, and orchestration

If you want to explore what’s available, open the package browser.

Install command

Run on an Advanced Computer.

wget run https://lattice-os.cc/install

Notes

  • The /install route serves the installer script directly (for ComputerCraft).
  • If your world/network is flaky, retrying the installer is usually safe — it’s designed around a manifest-driven flow.
  • If something fails, capture the on-screen error and the last action (package/file) for quick diagnosis.

What to expect

Lattice leans into a “systems” mindset. That means a bit more structure up front, and a lot less chaos later.

Explicit over implicit

Configuration and behavior should be discoverable by reading files, not guessing hidden defaults.

Structure over sprawl

A lattice grows without becoming a tangled heap. Packages should have clear boundaries and predictable installs.

Failure should be loud

When something goes wrong, it should be clear what failed and where. Debuggability is a feature.

Modular Composable Predictable Debuggable

Next

After installing, your next step is usually to identify the packages you want and build upward deliberately.