1.1.0
Compatibility
Changes
# 📦 CobbleTracker Update Changelog
## 🚀 Overview
CobbleTracker v1.1.0 delivers major stability enhancements, lifecycle tracking fixes, and powerful modular features to upgrade your Cobblemon server experience.
---
## 🛠️ Critical Bug Fixes & Stability
- **Filtered Player Pokémon False Alerts**: Fixed an issue where releasing party Pokémon triggered global spawn announcements. Chunk unloads and Pokéball recalls are now ignored.
- **Form & Regional Aspect Matching**: Categories now inspect dynamic form labels and regional forms rather than only base species tags.
- **Combined Multi-Label Announcements**: Pokémon matching multiple categories (e.g., Shiny Legendary) merge cleanly into a single unified MiniMessage broadcast.
- **Runtime Classloader Fixes**:
- **Fabric**: Fixed dev environment crashes by applying MixinExtras `@WrapOperation` on registry hooks.
- **NeoForge**: Resolved `LivingEntity` dimension conflicts via Access Transformers and Access Wideners.
---
## 🌟 New Features & Enhancements
### 🎯 10 Built-In Spawn Categories
Standard pre-configured categories now include:
- `Legendary`, `Mythic`, `Ancient`, `Ultra-Beast`, `Shiny`
- `Starter`, `Alolan`, `Hisuian`, `Galarian`, `Paldean`
Each supports custom MiniMessage styling, audio cues, particle trails, and glow highlights.
### 🛡️ Anti-Snipe Spawn Protection
- Introduces a protected encounter claim window for rare wild spawns.
- Spawn locators receive temporary capture priority for a configurable duration, preventing teleport sniping on multiplayer servers.
### 🌐 Discord Webhook Integration
- Rich embed alerts with official artwork, IV percentages, shiny badges, and coordinates.
- Fully asynchronous network dispatch to avoid server tick lag.
### 📜 Hall of Fame & Historic Tracking
- Persistent ledger tracking captured rare encounters, milestones, and discoveries.
- Stored safely via asynchronous writes to prevent I/O hitches.
### ⚙️ Modular Engine
- Every feature contains an independent toggle in `cobbletracker.json`.
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:7H6HU7Y7:QhKNZ2G0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7H6HU7Y7:QhKNZ2G0"
}

