CC: Tweaked: programmable computers and turtles for Minecraft, forked from ComputerCraft

The fork of ComputerCraft and what it changed

CC: Tweaked is a mod for Minecraft that adds programmable computers, turtles and more to the game. The project summary calls it a mod for Minecraft that adds programmable computers, turtles and more to the game, and a fork of the much-beloved ComputerCraft, continuing its legacy with improved performance and stability along with a wealth of new features.

The claim about performance and stability is the project's own, and the interesting part is that it is not the only differentiator. The fork's own community infrastructure reflects a project that has institutionalised its differences. There is a `CODE_OF_CONDUCT.md`, a `REUSE.toml` file, a `LICENSES/` directory, and a `crowdin.yml` file for translation, which together indicate a project with an organised contribution process and a formalised licensing and reuse scheme rather than a single maintainer's tree.

The version scheme makes the release cadence visible. The three most recent tags are v26.3-1.120.3 from 2026-09-28, v26.3-1.120.2 from 2026-09-17, and v26.2-1.120.2 from 2026-08-08. Each tag pairs a mod version with a Minecraft version, so the naming makes the coupling explicit: a CC: Tweaked release is scoped to one Minecraft release, and there is no long term version that spans game updates. The default branch is `mc-1.20.x`, and the last push was on 2026-10-19, so the tree is being worked on against a specific Minecraft line.

For a player, that coupling is invisible. For anyone publishing a mod that depends on CC: Tweaked, it is the single most important fact about the project.

One loader, two mod loaders, and a modrinth download

Installation is the easy part of this project. CC: Tweaked can be installed from Modrinth, and it runs on both Minecraft Forge and Fabric, so the same build serves both loader ecosystems rather than requiring separate per-loader artefacts from the user.

The repository is a multi-loader Gradle project, and the layout shows it. There is a `projects/` directory holding the project modules, `build-logic/` for custom Gradle plugin logic, a `gradle/` directory with the wrapper, `gradlew` and `gradlew.bat` launchers, and `settings.gradle.kts` and `build.gradle.kts` at the root. A `config/` directory and a `tools/` directory sit alongside them, along with a file named `illuaminate.sexp`, which uses a bespoke `.sexp` configuration format rather than JSON or YAML.

The naming of the API artefacts in the dependency snippet confirms the shape of it. There is a common API artefact for the vanilla case, described in the comment as being for multi-loader systems, and then separate `core-api`, `forge-api`, and `fabric-api` artefacts per loader, alongside the full forge and fabric runtime artefacts. A dependency that only wants the API and is not itself loader-specific can point at the common API alone, which is the sane default for a mod that runs on both.

The `package.json` at the root is worth a note because it is not what it looks like. It is named `tweaked.cc`, version 1.0.0, described as website additions for tweaked.cc, and it is an ES module package whose dependencies are the web terminal package `@squid-dev/cc-web-term` along with preact, tslib, setimmediate, and wasm-feature-detect. So the documentation site at tweaked.cc is a Preact application built with rollup, and it embeds a web-based terminal for the CC: Tweaked computers. The dev dependencies are the usual modern web toolchain, including typescript, rollup, and rehype with highlight support for rendering documentation code blocks.

The API is one package, and the rest is explicitly unstable

The most consequential design decision in the project is stated as a warning to integrators. You should be careful to only use classes within the `dan200.computercraft.api` package. Non-API classes are subject to change at any point. If you depend on functionality outside the API, or need to mixin to CC: Tweaked, the project asks you to file an issue so it knows.

This is a fork that has kept the package namespace of its predecessor, and it has made the API surface the compatibility contract. The reasoning is straightforward for a mod that is versioned against a game: the game updates on a schedule the mod does not control, so the mod's internal classes are going to move every time a new Minecraft version lands. The `dan200.computercraft.api` package is the part that stays put, and everything else is fair game for refactoring.

The documentation arrangements follow that contract. The API sources are bundled with the jar, so documentation should be viewable within your editor, and the generated documentation can be browsed online at the javadoc URL. The project also hosts documentation at tweaked.cc, which is the same site that the `package.json` in the root belongs to.

The `LICENSES/` directory, the `REUSE.toml` file, and the `SPDX-License-Identifier: MPL-2.0` header in the source comments point to a deliberate licensing position, with the per-file licence metadata handled through the REUSE specification so that every file in the tree declares its terms. That is a level of licence hygiene that many mod projects skip entirely, and it matters for anyone who wants to reuse the code.

Depending on CC: Tweaked from another mod

If you want to build on CC: Tweaked from a mod of your own, the project tells you that it is hosted on its own maven repository, so it is relatively simple to depend on. The repository is declared in Gradle with a content filter, so only the `cc.tweaked` group is fetched from it and everything else resolves from elsewhere:

repositories {
  maven {
    url "https://maven.squiddev.cc"
    content {
      includeGroup("cc.tweaked")
    }
  }
}

The dependency block itself then differs by loader, and the comments in the source label the three cases. The vanilla line is the one for multi-loader systems and points at the common API artefact. The Forge Gradle block declares the core API and the forge API as compile-only dependencies and the full forge artefact as a runtime-only dependency, while the Fabric Loom block does the same with the fabric API and the full fabric artefact using the scope names `modCompileOnly` and `modRuntimeOnly` that Loom uses for mod dependencies.

Two details are worth pausing on. The version coordinates in the artefact names are templated on the Minecraft version and on the CC: Tweaked version, which is the project telling you that those are two separate axes you have to keep aligned, and the Forge artefacts go through `fg.deobf`, the Forge Gradle deobfuscation helper, because Forge's production environment remaps Minecraft classes.

The project also recommends adding a soft or hard dependency in your `mods.toml` file with the appropriate version bounds, so that API functionality you depend on is guaranteed to be present at runtime. That is a small step that prevents the worst class of failure, which is a mod that loads against an API method that no longer exists.

A fork that also has to keep the original's community with it

Forking a mod means inheriting its users as well as its code, and the community section shows how that is handled. The project points you to the GitHub discussions page if you need help getting started with CC: Tweaked, want to show off your latest project, or just want to chat about ComputerCraft. There is also a fairly populated but quiet IRC channel on EsperNet, reachable as `#computercraft` through a desktop client or online through KiwiIRC.

Using the word ComputerCraft in the chat invitation rather than CC: Tweaked is a deliberate touch. The fork inherits the name in people's mouths, and the community is organised around that inherited name rather than around the fork's own branding.

Contributions are open in the broad sense. Any contribution is welcome, whether that is using the mod, reporting bugs, or contributing code, and the project points developers to the developing section of CONTRIBUTING.md for how to get started. The repository also has a `.pre-commit-config.yaml` and a `typos.toml`, the latter being a spell checker configuration for the source tree, which is a detail worth noting because a project that runs a typo checker over its own source is a project that expects text to be reviewed as well as code.

For a player, the practical picture is a mod distributed on Modrinth, documented at tweaked.cc, with a discussion forum and an IRC channel for the people who write the Lua programs that run on its computers.

What the fork does not solve for you

There are limits here that are worth stating plainly, and they come from the game rather than from the code.

First, the Minecraft coupling is unavoidable. Every release is bound to a specific Minecraft version, and the default branch is named after one, `mc-1.20.x`. A server operator who wants a setup that survives game updates has to plan for upgrading CC: Tweaked alongside the game, and the release naming makes that a per-update chore rather than an occasional one. This is the structural cost of the mod category, not a defect in this fork.

Second, the API is deliberately narrow. If your mod needs to reach into how a computer actually executes a program, or how a turtle registers its peripherals, that is exactly the surface the project reserves the right to change. The path forward is the one the project names, filing an issue so the use case can be discussed, which is the right process but a slower one than a stable internal API would be.

Third, the licence information is not as clean as the file listing suggests. The licence field in the repository listing is given as unknown, while the source headers carry `SPDX-License-Identifier: MPL-2.0` and the tree includes a `LICENSES/` directory and a `REUSE.toml` file. Those are consistent with each other, and the MPL-2.0 terms in the header are the most specific statement in the repository, but anyone shipping a derived mod should read the licence files in the tree rather than trust the metadata field, and should treat the per-file REUSE data as the authoritative mapping of terms to files.

Fourth, the improvements over the original are asserted rather than measured in anything the project publishes. There are no benchmark numbers or comparison figures in the documentation, so the fair statement is that the project claims better performance and stability and that you would have to judge that yourself.

Editorial conclusion

CC: Tweaked suits a Minecraft mod developer who wants to add programmable hardware and Lua scripting to a world with better performance and stability than ComputerCraft, and it suits a player who wants to write Lua programs against computers in the game. It is the wrong choice for a server operator who wants a stable long term deployment, because releases are tied to Minecraft versions and the default branch follows the newest line. Verify three things before depending on it: that your Minecraft version has a matching CC: Tweaked release, that you only use classes in the dan200.computercraft.api package because everything else is subject to change, and that the MPL-2.0 licensing recorded in the source headers matches how you intend to redistribute your mod.

Frequently asked questions

Official sources

1. cc-tweaked/CC-Tweaked on GitHub
2. Issues
3. Project website
4. README
5. Releases