Tags
Creators
Details
2.0.0.9
Compatibility
Required content
Changes
2.0.0.9 Compatibility improvements for Forge
- Add compatibility for Forge 1.16.6
2.0.0.8 Compatibility improvements for NeoForge
- Add compatibility for NeoForge 1.20.5
2.0.0.7 Http Client adjustments
- Dynamically construct http client header
2.0.0.6 Auth Error Fix
- Fix an error when storing data with 2.0.0.5
2.0.0.5 No more Access Token
- CloudSettings no longer uses your Minecraft Access Token to authenticate. The whole server login process is used instead
2.0.0.4 Earlier injection point
- initialize cloud settings on the first option load up before minecraft gets fully initialized.
2.0.0.3 Gui Scale Fix
- fix a small bug where the loaded gui scale won't get applied to the minecraft window
- add shutdown hook to sync pending changes when minecraft gets closed
2.0.0.2 Sync Fix
- fix handler won't get initialized when no data exists
2.0.0.1 Compatibility improvements
- Remove Title Screen Listener to initialize cloud settings
- Use mixin into Minecraft to initialize cloud settings
2.0.0.0 Another Rewrite?
It's been 6 Months since the last rewrite which brought us a suspicious looking login screen and a login cert file and i instantly regretted making those.
That's why I removed them completely and switched to a new authorization concept which uses the Microsoft Access Token to identify a user using the MinecraftServices.com API. This is basically the same way as Minecraft uses it to verify you're not a cracked minecraft player when joining a Server.
So here are the good news
- Improved load up speed due to async option requesting
- No log in required anymore
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:nnu4dJj4:gmojFcs2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nnu4dJj4:gmojFcs2"
}

