Tags
Creators
Details
0.2.0+1.20
Compatibility
Required content
Changes
A 1.20 port of the 0.2.0 release.
The 0.2.0 release adds message presets, laying down the groundwork for message pools and eventually scheduling.
Message Presets
Message presets are useful when you want to save broadcasts that you might use quite a bit in the future. Eg: "The server will be restarting in 5 minutes."
To create a message preset, you can use the following command:
/broadcast preset create <id> <type> [contents]
Example usage:
/broadcast preset create simplebroadcast:test minecraft:vanilla "Hello world!"/broadcast preset create simplebroadcast:empty simplebroadcast:default
To broadcast a preset message simply call the following command:
/broadcast preset <id>- Broadcast a preset to the entire server.
You can modify and read preset configurations using the following commands:
/broadcast preset <id> location- Get the display location of the message preset./broadcast preset <id> location [actionbar/chat/title]- Set the location of the preset./broadcast preset <id> contents- Get the raw contents of the message preset. This will not format the contents./broadcast preset <id> contents <value>- Set the raw contents of the message preset./broadcast preset <id> type- Get the message type of the preset./broadcast preset <id> type <type>- Set the message type of the preset./broadcast preset <id> delete- Delete the message preset.
Full Changelog: https://github.com/mineblock11/SimpleBroadcast/compare/0.2.0+1.19.x...0.2.0+1.20 Full Documentation: https://docs.mineblock11.dev/
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| SimpleBroadcast-0.2.0+1.20-sources.jar | Unknown | 217.72 KiB |
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:ijqqUY8R:mxCIjsCs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ijqqUY8R:mxCIjsCs"
}

