Skip to main content

Overriding Settings

Stonecraft's role is to configure sensible defaults. It's not restrictive in any way.

Stonecraft comes first!​

If you want to be able to overwrite anything that Stonecutter sets, you need to make sure that Stonecraft is applied first.

Below is a simple gradle file that shows you how you should think of the configuration block order. This shows you the order in which things are set within Stonecraft. Since the modSettings block comes first, anything that follows it can overwrite the settings it sets.

If you want to see an example, check the Stonecraft-template

High Level Overview​

build.gradle.kts
plugins {
    id("gg.meza.stonecraft")
}

modSettings {}

repositories {}
dependencies {}

// Architectury related settings
fabricApi {}
loom {}

// Task overrides
tasks.processResources {}

// Mod publishing
publishMods {}

Overriding Minecraft Version for snapshot builds​

When you are building for a snapshot version of Minecraft, you can prepare your mod for the eventual release. It's simpler to explain this with an example.

Let's say currently Minecraft 1.21.5 is out and you're preparing your mod for 1.21.6 and the current snapshot is 1.21.6-rc1.

1. Create the 1.21.6.properties file​

Create a file named 1.21.6.properties in the versions/dependencies folder with the following content:

minecraft_version=1.21.6-rc1  # <- This is the real snapshot version that the build will use
yarn_mappings=1.21.6-rc1+build.1
loader_version=0.16.14

# Fabric API
fabric_version=0.127.0+1.21.6

This is what you would copy from Fabric's website for the snapshot version.

2. Set your stonecutter version​

settings.gradle.kts
  ...
  mc("1.21.6", "fabric")  // 1.21.6 doesn't technically exist yet, but you can prepare for it
  ...

And that's it! Stonecraft will automatically use the 1.21.6.properties file for the snapshot build.