Tags
Creators
Details
5.0.0-alpha.1+fabric-1.21.11
Compatibility
Required content
Changes
With the release of Minecraft 1.21.11, the game's latest update broke TCDCommons API and Better Statistics Screen (both v4.X) beyond repair, to the point where one may as well rewrite a lot of the codebase if v4.X were ported to 1.21.11. I have therefore decided to part ways with v4.X and focus solely on my upcoming v5.X versions that are full rewrites of my mods.
For the past few months, I have been working on full rewrites of my mods, that I planned to release as v5.X. The goal with those rewrites is to develop a more robust codebase that improves stability of my mods, as well as to fix what past game updates broke.
Given 1.21.11 completely 'totaled' my v4.X mods, I have decided to release the progress I have made so far with v5.X, although still in its early alpha stage. This wasn't the initial plan, so expect missing and incomplete features.
v5.X is still in development, and I plan to reimplement missing features soon. It will take a while however.
Changelog
- Overhauled GUI framework
Missing features
- Client/Server networking
- HTTP networking
LEGAL NOTICE
The license for v5.X versions is All rights reserved for now, however it also grants modpack developers the right to feature v5.X versions in modpacks that are hosted on CurseForge and Modrinth. Please read the full license file for more info.
The primary reason for this is that I did not plan to release v5.X this early, and ARR was meant to be in place until I found a license I felt comfortable with. The idea was to assign a proper license once the full v5.0 release was out. Given I had no choice but to release v5.X early, ARR will remain for now.
Regarding modpacks; Feel free to feature my mods in modpacks on CurseForge and Modrinth. Despite the license, I intentionally worded it to permit modpack usage.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Eldc1g37:YMGq7X5F"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Eldc1g37:YMGq7X5F"
}

