Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated last month
All versions
19.3.5
Release
v19.3.5 - (Neo-)Forge - 1.19.3-1.20.1last year 1.72M
Compatibility
Minecraft: Java Edition
1.20–1.20.1
1.19.3–1.19.4
Platforms
Forge
NeoForge
Supported environments
Client-side
Server-side
Client and server
Changes
19.3.5
- Split config for builtin data- and resourcepacks, sorry for the inconvenience
- Your Config Formatting will no longer be overwritten all the time
- Packs added trough folder entries in the config, can now also be overwritten to have a lower priority, by specifying a specific file
19.3.4
- I found a Mixin bug jaj /s
- Should now run properly on forge and fabric again, big sorry!
19.3.3
- Actually fix default config not working
- Will now properly update legacy configs to new format
19.3.2
- Fixed default config not working
19.3.1
Backport of 21.0.5
- Added new Config options
- log_pack_ids -> if set to true, the IDs of all available packs will be logged
- resourcepacks.enable_builtin -> A list of pack IDs to be enabled, this can be used to enable builtin resourcepacks from mods
- Load order from config is now respected, changed previous behavior, datapacks and resourcepacks will be listed in the same order, as in the config. (First in the config = highest priority ingame) The config will be converted automatically if you were on 21.0.1 before.
- Force enabled Resourcepacks, will no longer show twice in the resourcepack list.
- Changed Default config for compat with upcoming CF changes
- Updating will automatically add "<instance folder>/datapacks/" to the config. CF will load datapacks from that folder.
- Renamed config to
global_packs.tomlit'll be renamed automagically. - Folders in config will be created automatically (now more reliable)
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:NRLPy2mk:Kgn0YIHG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NRLPy2mk:Kgn0YIHG"
}

