Three ways to get involved

With the IntelliJ IDEA plugin

Install Sacred Mod Development from the JetBrains Marketplace, or search for it under Settings → Plugins.

Then choose File → New → Project → Sacred Mod. The wizard asks for a name, a description, and a template: a bare entrypoint or one with a working listener. You also pick the mod’s language (Java, Kotlin, or Groovy) and the build script’s DSL (Kotlin or Groovy).

The two choices are independent, so a Groovy mod can sit behind a Kotlin build script. The wizard can also run git init and set up an SRML repository, so a launcher can install the mod from day one.

A green Run Sacred configuration appears as soon as the plugin sees dev.ancaria.coderpack in your build script. It builds the mod and installs it into the Sacred Gold folder set in Settings. If the loader release isn’t cached yet, it downloads it and checks its SHA-256. Then it starts the game with your mod loaded.

With the command line

coderpack new creates the same project from a terminal. --language picks Java, Kotlin, or Groovy, and --dsl picks the build script syntax. The two don’t have to match.

Only Java adds no runtime. A Java mod stays around 1.8 KB, a Kotlin jar carries its standard library at about 1.8 MB, and Groovy’s runtime brings it to about 7.8 MB.

A Kotlin project also gets dev.ancaria.coderpack:api-kotlin, the same API in Kotlin style. The event becomes a type argument instead of a class literal, and one on covers both watching and deciding. To change what the game is about to store, a listener calls mutate, which compiles only for events that can be decided.

The module adds nothing the Java API can’t do—every declaration forwards to it—so a Kotlin mod can drop it and call the Java API directly. The Kotlin tab on the front page uses it.

1$ coderpack new gold-rush --language kotlin
2# writes build.gradle.kts, settings.gradle.kts, registry.toml,
3# and src/main/kotlin/mods/goldrush/GoldRush.kt
4
5$ cd gold-rush
6$ ./gradlew assembleSacredMod

Both build scripts produce the same descriptor:

1plugins {
2    id("dev.ancaria.coderpack") version "0.200.0"
3}
4
5version = "1.0.0"
6
7sacred {
8    id = "gold-rush"
9    displayName = "Gold Rush"
10    description = "Tops up every gold pickup by half again"
11    entrypoint = "dev.ancaria.mod.goldrush.GoldRushMod"
12    author("MairwunNx (Pavel Erokhin)")
13    website = "https://ancaria.dev"
14    repository = "https://github.com/me/gold-rush"
15    apiVersion = "0.200.0"
16    installTo = layout.dir(providers.gradleProperty("sacredDir").map { file("$it/mods") })
17}

Covered events

These are all the events a mod can subscribe to in API 3. A mutable event arrives before the game commits the write, so a listener can return the event’s Mutation to veto it or change what gets stored. The rest report what already happened.

An event that no class covers yet arrives as Unknown, with its wire name and raw fields, so a tracer subscribed to Event still sees it. The full contract is in coderpack’s EVENTS.md.

For anything that isn’t an event, getContext().getGame() acts on the game directly. getWorld().getEntityRegistry().getPlayer() returns the hero, and getConsole().print("...") writes a line to the in-game console.

Working on the platform

The loader has three parts: a Frida agent that hooks instructions inside the 32-bit game, a Rust host that carries frames between the game and the JVM, and the JVM that dispatches events to mods. Nothing patches the game on disk. How an event crosses that boundary and back is on the How it works page.

Every hook and address needs evidence before it ships. Research on pureHD.exe relies on three tools: Cheat Engine to watch memory live and find candidate writers, a PE analysis kit (pefile and Capstone) for offline disassembly and string catalogues, and Ghidra for deeper static analysis and call graphs.

A confirmed result moves from research into mappings as a VA, an RVA, and a confidence level. Shipping code never hard-codes an address.

Why pureHD.exe 2.0.2.118 and not the stock Sacred.exe? The community pureHD mod fixes a long list of the original’s bugs, keeps Sacred’s balance and feel, and adds only what’s genuinely useful. That makes it the one build worth pinning every address to.

If your folder has another build, the launcher tells you. It can fetch pureHD from ancaria.dev/files/sacred.purehd.zip and place pureHD.exe and pHD.dll next to the game, leaving the original executable alone.