Tags
Creators
Details
Licensed MIT
Published 5 years ago
Updated 3 years ago
All versions
2.0
Release
1.7.10-2.04 years ago 208
Compatibility
Minecraft: Java Edition
1.7.10
Platform
Forge
Supported environments
Client-side
Server-side
Changes
New features
- Added the
packfolder system, to automatically build thepack.mcinstancefile if it's missing. - Added a template layout in this folder by default.
- Added the hash-based cache system, to not have to re-download the same file everytime there's a pack update (can be disabled).
- Added the optional resources system. Supports grouping, menus, multiple options to check at once and much more (Check out the wiki) [Currently only for the
clientside] - Added an update checker with multiple modes, including automatic installation.
- Added a zero-byte files deleting system for the
modsfolder. It will delete any empty file in there.
Feature changes and fixes
- Changed the overrides/carryover to only merge and not replace folders (they can can still overwrite files though). This is to make the code more coherent and fix a lot of issues.
- Changed the config file's organisation to be better and more readable (you will have to re-create your configs).
- Updated and fixed the Curseforge integration (now with config settings)
- Updated to Modrinth API v2.
- Updated how the mod grabs data from those two platforms
- The mod's version is now present in the logs.
- Fixed the logo not getting displayed in the mod info page for Windows systems.
- Fixed the mod crashing on servers.
- Rewrote the wiki to be much better and easier to understand
- Removed the StopModReposts error when the blacklist couldn't be downloaded, and made the integration optional.
- Replaced the amount of web redirections config with a connection timeout setting instead.
Technical changes
- Rewrote the entire web system to use Apache's
HttpClient. It should be more stable, sometimes faster and provides a way cleaner code. - Refactored a good portion of the code base to be more organized, with smaller functions and an overall cleaner code (i hope).
- Reworked some GUI code to be easier to use
- Separated the main code into multiple phases, allowing to only do a certain portion at some specific point. Used by the update GUI.
- Bumped the version number to 2.0
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:cUtsYbG5:6LfaZsbS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cUtsYbG5:6LfaZsbS"
}

