All versions
1.3.8
Release
Cobblemon Quick Battle 1.3.8-NeoForge4 months ago 3,386
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Fixes
- Fixed quick battles trusting client-only checks for multiplayer flow, so the server now validates target range, player battle state, target capture or busy state, and invalid first-move cases before the quick battle starts.
- Replaced blocking quick battle timing with server-tick scheduling, preventing the server thread from sleeping during send-out follow-up and wild Pokemon defeat cleanup.
Adjustments
- Adjusted quick battle move choice to automatically use the strongest usable damaging move against the current target instead of always forcing move slot 1.
- Added a first pass of quick battle hit feedback that anchors hitsplats, effectiveness text, and floating XP or EV rewards over the target Pokemon instead of using full-screen flashes.
- Allowed clearing the quick battle keyboard and controller bindings with right-click in the config screen, showing
-while the action is unbound. - Restyled quick battle config tooltips with a custom red-bordered popup treatment to better match the stronger Cobblemon config screen presentation.
- Polished the custom config tooltips so wrapped text is centered inside the popup and the tooltip layer renders above the config rows cleanly.
- Tightened the custom config tooltip sizing and transparency so single-line popups sit lighter and closer to the text they describe.
- Anchored quick battle config tooltips above the mouse with full-screen overlap instead of confining them to the panel, and moved keybind unbinding to the list-level right-click path so both keyboard and controller bindings clear reliably.
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:55fHndP6:QhZ87Fx9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:55fHndP6:QhZ87Fx9"
}


