Minecraft mods, but easier
  • Kotlin 79.2%
  • Java 20.8%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2026-08-16 00:31:29 +02:00
gradle/wrapper Initial Commit 2026-04-20 18:19:24 +02:00
gradle-plugin test framework 2026-08-10 22:52:06 +02:00
src/main testing: add sneak 2026-08-16 00:31:29 +02:00
.gitignore Initial Commit 2026-04-20 18:19:24 +02:00
build.gradle.kts gradle plugin, shadowing & client support 2026-07-26 22:13:26 +02:00
LICENSE.txt Initial Commit 2026-04-20 18:19:24 +02:00
README.md gradle plugin, shadowing & client support 2026-07-26 22:13:26 +02:00
settings.gradle.kts Initial Commit 2026-04-20 18:19:24 +02:00

Crimson

My personal library for Fabric mods.

I directly include Crimson in all my mods. It is not a separate mod. This is my personal preference because it gives me more flexibility, causes fewer conflicts and allows me to backport features automatically.

To make inclusion easier, there is a gradle plugin in this repository that handles shadowing. Dependencies are shadowed instead of using fabric's include feature because if multiple mods include different versions of the same dependency, only one is available, which causes conflicts and incompatibilities

You can add this as a git submodule if you want to, but I recommend just copy-pasting whatever you need into your own project. There are no guarantees for a stable API.

My goal is to make crimson handle all interactions with the game. That way I can make my mod codebases only consist of the mod's actual logic. I want to abstract Minecraft in a way that maximizes the readability of my mod's codebases.


This started as a port of a previous project of mine: Crimson for PaperMC, which had the goal to add Skript-like development patterns to Paper (like a simple wait n ticks, making it easier to create visual effects)

However, I rarely use Paper servers anymore, so the original project was replaced by this.