Skip to main content

Updating Nitea

1. Change the version​

If you keep it in gradle.properties (like the mod configurator does), it's one line:

gradle.properties
nitea_version=0.3.1

Otherwise change the version at the end of the Nitea dependency in build.gradle. The loader and Minecraft version in the artifact name stay the same.

2. Rebuild and test​

If Gradle doesn't pick up the new version, run ./gradlew build --refresh-dependencies.

3. Release your mod​

Players get the new Nitea when they update your mod.

What players run​

Nitea is bundled inside mod jars, so a player runs whichever copy their mods contain. When several mods ship different versions, the loader (NeoForge, Forge or Fabric) loads the newest. That means:

  • Your mod may run on a newer Nitea than you built against, because another mod in the pack ships it. That's supported: Nitea never removes or changes public methods.
  • Your mod never runs on an older Nitea than you built against.

You don't need to update Nitea for your mod to keep working. Update to get fixes and new features.

warning

Only use the documented API (cc.nitea.*). Classes in cc.nitea.internal can change in any version, and a mod that uses them can break when a newer Nitea is loaded.

Releases and changes are listed on GitHub.

From 0.2 to 0.3​

Nitea 0.3 ships one artifact per loader and Minecraft version instead of a single NeoForge one. It's also published in Nitea's own Maven repository instead of JitPack: replace maven { url 'https://jitpack.io' } with maven { url 'https://libraries.nitea.cc' }, and the coordinates com.github.pyrogenous:NSDK:0.2.0 with cc.nitea:nitea-<loader>-<minecraft>:0.3.0, for example nitea-neoforge-26.2. The API is the same.