1.1.0
Compatibility
Required content
Changes
Version 1.1.0
A quality-of-life and bug-fix update focused on the pasture block limit system and better control over denial messages.
Fixed
-
Ghost blocks / item desync
When a player hit their pasture block limit, the client would still briefly place a “ghost” pasture and consume the item until they switched slots or relogged. Placement is now properly cancelled and the inventory is force-synced instantly. No more ghosts. -
Top-half break not counting
Breaking only the top half of a pasture block no longer left the block count stuck. The tracker now correctly detects both the top and bottom half of the double block.
Added / Improved
-
Configurable message location
New optiondeny_message_locationwith four choices:chat– normal chat (default)actionbar– action bar onlyboth– chat and action barnone– suppress all denial messages
-
Full formatting support
All denial messages fully support Minecraft’s formatting codes (§c,§l,§o, colours, bold, italic, etc.). -
Expanded YACL config screen
The in-game config menu now exposes:- Default Pokémon limit
- Default pasture blocks limit
- Prevent creative bypass
- Notify on deny
- Message location
- All five denial messages (editable with formatting)
Complex lists (ranks, blacklists, species limits, etc.) remain JSON-only for precise server control.
Technical notes
- Still fully server-side. Clients only need the mod if they want the YACL screen.
- Compatible with Cobblemon 1.7.3+. Cobblemon 1.8 should work.
- Existing configs are automatically upgraded. New keys get sensible defaults.
Thanks for the reports and testing. Enjoy cleaner pastures!
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:v3RSFRlW:6eCWGi45"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v3RSFRlW:6eCWGi45"
}

