Tags
Creators
Details
2.1.1
Compatibility
Required content
Changes
-
Added keybind and gui element to open journal.
-
The hotbar message is now more clear on what is restricted.
-
Extended API functionality to set restrictions. This has laid the foundation of my goal to move away from config restrictions, to datapack and external mod functionality. Starting in 2.1.2 Farmers Delight config restrictions will be removed and a separate mod to enable those restrictions will be required.
-
There are pros and cons to having separate mod restrictions and I've taken all into consideration.
-
- Community driven restrictions are possible
-
- The config in Player Journal will become less cluttered.
-
- Not everyone will have those in built mods installed so being able to choose is a positive.
-
- The biggest negative is the player will need more mods installed to enable the full restriction list.
-
- Custom config restrictions will still be possible and easily added.
Optional dependencies
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:3Rm0Nh4k:SP664hHC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3Rm0Nh4k:SP664hHC"
}



