Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 5 months ago
Updated 3 weeks ago
All versions
1.4.0
Release
Auto Broadcaster 1.4.03 weeks ago 359
Uploaded by
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
Platforms
Folia
Paper
Purpur
Changes
What's Changed since v1.3.0
New Features
- Per-world broadcast targeting — Use
target_worldsconfig option to broadcast messages only to players in specific worlds (works for both interval and scheduled messages) - Per-permission broadcast targeting — Use
required_permissionconfig option to restrict message visibility to players with specific permissions - Interval validation — Minimum 10-second interval enforced automatically to prevent performance issues
- Improved message format detection — Regex-based MiniMessage tag detection instead of fragile heuristic
- Better tab completion — Suggests indices for
remove intervaland time keys forremove time
Performance Optimizations
- Pre-computed messages — Prefix + content components are built once at config load, not on every broadcast tick
- Zero-allocation world filtering — Replaced stream-based filtering with simple for-loop
- Cached time parsing — Scheduled message times parsed once and cached
Bug Fixes
- Scheduled message duplicates — Added per-day "already fired" tracking to prevent duplicate broadcasts after reload
- Scheduled message misses — Uses a 2-minute window instead of exact time matching to handle server lag gracefully
Configuration Changes
New config options in config.yml:
interval_messages.target_worlds— List of worlds (empty = all worlds)interval_messages.required_permission— Permission node (empty = everyone)scheduled_messages.target_worlds— Per-time world targetingscheduled_messages.required_permissions— Per-time permission targeting
Download
The paper-auto-broadcaster-1.4.0-all.jar is the plugin JAR to use on your server.
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:s0lEVsmg:2cXXgXcm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s0lEVsmg:2cXXgXcm"
}

