Tags
Creators
Details
2.5.0
Compatibility
Required content
Changes
Full English changelog available on GitHub. Full French changelog available on our Discord.
Summary
This update reorganizes Discord webhook handling, adds Safari webhook support, improves Mass Outbreak detection, and adds an option to prevent classic CSAR alert flood during outbreaks.
Fixed
- Fixed Mass Outbreak detection that could fail to trigger in-game alerts or webhooks
- Fixed Mass Outbreak detection by adding a fallback scanner for active outbreaks
- Fixed outbreak Pokémon triggering too many classic CSAR alerts
- Fixed the missing translation for the outbreak classic alert option
Added
- Added a separate
webhooks.jsonconfig file - Added a dedicated Safari webhook
- Added Safari webhook options in the server config UI
- Added dedicated webhook URLs for spawns, captures, outbreaks, and Safari
- Added fallback behavior to the default webhook when a dedicated URL is empty
- Added a configurable option to allow or block classic alerts for Pokémon coming from a Mass Outbreak
- Added a flood warning in the UI for the outbreak classic alert option
- Added a
LICENSEfile with All Rights Reserved
Improved
- Improved Discord webhook organization by separating it from the main server config
- Improved config readability and overall webhook management
- Improved migration support for older webhook values into
webhooks.json - Improved Mass Outbreak reliability so alerts no longer depend only on the initial compat hook
- Improved server control by allowing either recommended anti-flood behavior or a more permissive setup
Notes
- The mod license is now All Rights Reserved
- By default, normal Pokémon from a Mass Outbreak do not trigger classic CSAR alerts to avoid spam
- Important special alerts such as Shiny, Alpha, or Radiant can still be preserved depending on the mod logic
- It is recommended to regenerate the Discord webhook URL used during testing before release
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:meUPQ1KX:srX3ogpb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:meUPQ1KX:srX3ogpb"
}

