Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 months ago
All versions
1.2.2+1.21.1
Release
Cobblemon Broadcaster 1.2.2+1.21.110 months ago 119
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Changes
Additions
- Added PokeSnack Support.
- Added support for Pokemon Labels.
- Broadcasts now have a toggle to decide whether to announce to the server or to the player it spawned on. PokeSnacks are always global. (default: Global)
- Added the following placeholders: {x}, {y}, {z}, {gender}, {biome}, {dimension}.
Fixes
- Fixed an issue where defeating an NPC with a pokemon matching a Faint spec would announce it in chat.
- Fixed an issue where adding new keys wouldn't update with the reload command.
Removals
- Removed the "Enabled" key from
config.yml. If you don't want something, simply delete the entire entry from yourconfig.yml
config.yml
# DON'T TOUCH Config-Version OR THINGS WILL BREAK
Config-Version: 1.2.0
# Name of Spec
shiny:
# Set whether the message is sent to all players, or just on the player it spawned on. (true/false)
Global-Alert: true
# Message that gets sent to all players when the Pokemon with the spec spawns in.
SpawnMessage: "<yellow>A shiny <gold>{pokemon} <yellow>spawned on <gold>{player} at x = {x}!"
# Message that gets sent to all players when the Pokemon with the spec spawns in from a PokeSnack
SpawnMessage-Snack: "<yellow>A shiny <gold>{pokemon} <yellow>was lured in by a PokeSnack at {x}, {y}, {z}!"
# Message that gets sent to all players when the Pokemon with the spec faints.
FaintMessage: "<red>A shiny <dark_red>{pokemon}<red> has fainted."
# Message that gets sent to all players when the Pokemon with the spec is captured.
CaptureMessage: "<yellow>A shiny <gold>{pokemon} <yellow>has been captured by <gold>{player}!"
legendary:
Global-Alert: true
SpawnMessage: "<green>A Legendary <dark_green>{pokemon} <green>has spawned near <dark_green>{player}!"
FaintMessage: "<red>A Legendary <dark_red>{pokemon}<red> has fainted."
CaptureMessage: "<green>A Legendary <dark_green>{pokemon} <green>has been captured by <dark_green>{player}!"
mythical:
Global-Alert: true
SpawnMessage: "<light_purple>A Mythical <dark_purple>{pokemon} <light_purple>has spawned near <dark_purple>{player}!"
FaintMessage: "<red>A Mythical <dark_red>{pokemon}<red> has fainted."
CaptureMessage: "<light_purple>A Mythical <dark_purple>{pokemon} <light_purple>has been captured by <dark_purple>{player}!"
ultrabeast:
Global-Alert: true
SpawnMessage: "<aqua>An Ultra Beast <dark_aqua>{pokemon} <aqua>has spawned near <dark_aqua>{player}!"
FaintMessage: "<red>A Ultra Beast <dark_red>{pokemon}<red> has fainted."
CaptureMessage: "<aqua>A Ultra Beast <dark_aqua>{pokemon} <aqua>has been captured by <dark_aqua>{player}!"
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:E96uokEJ:aJYdlbzP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E96uokEJ:aJYdlbzP"
}

