Back to mods
Common Toolkit project artwork

CurseForge · Minecraft mod

Common Toolkit

A NeoForge library mod providing shared developer utilities: declarative config, networking helpers, dynamic JSON-driven registries with client sync, weighted gear/brewing-mix systems, and creative tab filling.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which Common Toolkit release should I use?

Updated 2 days ago
Latest stable file Common Toolkit (1.1.0)
Game version 26.2
Loader NeoForge

Common Toolkit (1.1.0) targets 26.2 with NeoForge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.

Where it goes

Is Common Toolkit required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release NeoForge
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does Common Toolkit (1.1.0) need?

Common Toolkit (1.1.0). Change the file and its required mods may change too.

No extra mods listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional mods.

Before you install it

Add Common Toolkit without breaking your instance.

Built for Common Toolkit (1.1.0). Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use Common Toolkit (1.1.0). It targets 26.2 with NeoForge; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    This file does not list any required mods. Do not add a library just because a different file uses it.

  3. 03

    Put it on the correct side

    The project page does not say whether this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside Common Toolkit (1.1.0). It opens that exact file at the source.

About this project

What does Common Toolkit add?

🧩 Common Toolkit

A NeoForge library mod providing shared developer utilities: declarative config, networking helpers, dynamic JSON-driven registries with client sync, weighted gear/brewing-mix systems, and creative tab filling.

NeoForge Minecraft 26.2 and 1.21.1 Library LGPL-2.1-or-later


✨ Overview

Common Toolkit is not a gameplay mod by itself — it is a library that other mods depend on. It bundles a set of infrastructure pieces that are tedious to rebuild from scratch for every mod: config declaration, network payload plumbing, JSON/datapack-driven registries that stay in sync between server and client, dynamic tags for those registries, and a couple of ready-made registries (gear sets, brewing mixes) built on top of that infrastructure.

If you were told to install this mod, it's because another mod on the pack depends on it — it adds no content on its own.
Codex Stalking Dragons

🎯 Features

⚙️ Configuration

Declarative common/client/server config definitions with an in-game config screen, without the boilerplate of hand-rolling a ModConfigSpec for every value.

🔄 Dynamic Registries

JSON-driven registries that reload with datapacks and automatically sync their contents from server to client over the network — both weighted (for random-selection use cases) and unweighted variants.

🏷️ Dynamic Tags

A tag system for the dynamic registries above: #namespace:tag references in datapack JSON, resolved after content load and synced to the client, mirroring how vanilla tags work for built-in registries.

📡 Networking Helper

A thin layer over NeoForge's payload API that removes the repetitive registration/handling boilerplate for custom network packets.

🎯 Gear Sets & Brewing Mixes

Two ready-made dynamic registries built on the framework above: weighted, JSON-configurable equipment sets and custom brewing recipes, meant to be consumed by other mods' game logic.

📦 Creative Tab Filling

Declarative registry to inject items into existing creative tabs (vanilla or modded) without writing an event handler per mod.

🌈 Color & Codec Utilities

Gradient color helpers and common Codec/StreamCodec building blocks shared across the utilities above.

🧱 Mod Structure

Internally the library is organised into self-contained subsystems. Other mods pick only the pieces they need — nothing here runs unless a dependent mod calls into it.

Area What it provides
config Declarative configuration system (common/client/server) with an in-game screen. Derived from Minecraft Forge's legacy config system (LGPL-2.1, see NOTICE.md).
dynreg Core dynamic-registry framework: datapack reload, server→client sync, weighted and unweighted variants, per-registry serializers.
dynreg/tag Dynamic tags for those registries: tag keys, holder sets, datapack tag loading and client sync.
network / payloads Payload registration/handling helpers over the NeoForge networking API.
systems/gear Weighted, JSON-configurable equipment-set registry built on dynreg.
systems/mixes JSON-configurable custom brewing-mix registry built on dynreg.
tabs Declarative creative-tab injection registry.
codec / json / color Shared Codec/StreamCodec building blocks, JSON helpers and gradient-colour utilities.
menu / screen Container-menu and screen helpers (data slots, filtered slots, tickable text).
block_entity / datagen / commands Ticking block-entity helpers, data-generation helpers, and debug commands (/common_toolkit).

📄 Requirements

Minecraft / NeoForge / Java see Available Versions below
Side Client and Server (required on both)

📦 Available Versions

Minecraft NeoForge Java Latest build Status
26.2 26.2.0.57+ 25 1.1.0 Stable
1.21.1 21.1.259+ 21 0.0.0-beta.4 Beta — re-fork port from upstream Placebo 1.21.1

Both versions share this CurseForge project. Pick the file that matches your Minecraft version — the API surface is the same across both, only the underlying platform differs.

🎮 How to Use

  1. Install as a dependency of another mod that requires it, on both client and server.
  2. No configuration is needed to simply run it — it only exposes APIs and registries for other mods to build on.

🙏 Credits & License

Common Toolkit is a rewritten, independently branded port of Placebo by Shadows_of_Fire (MIT License), under a new mod id, package and API. The 26.2 build targets the current NeoForge line; the 1.21.1 build is a re-fork from the upstream Placebo 1.21.1 sources. The original Patreon-gated cosmetic system was not ported.

License: this mod is distributed under the GNU LGPL v2.1 or later, because its configuration system (com.skd.commontoolkit.config) is derived from Minecraft Forge's LGPL-2.1 legacy config code. The remaining, Placebo-derived portions are additionally available under the MIT License. Full third-party attribution, the MIT text and the LGPL-2.1 notice are in the repository's NOTICE.md; the complete LGPL-2.1 text ships as COPYING.LESSER in the jar and repo, and the mod's own source is published as a -sources.jar alongside every release.

Developed by Stalking Dragons.

Codex Stalking Dragons
https://codex.skdragons.com/
Codex Stalking Dragons — Minecraft Modding

Project description from CurseForge.

Pick your setup

Common Toolkit by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

2 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

Common Toolkit versions and loaders

9 of 9 releases match

Looking for an older file? The official CurseForge project page is in Resources.