Tags
Creators
Details
3.0.0
Compatibility
Required content
Changes
MC 1.21.1 - 3.0.0
- No more "limits" or "delays", messages are sent when they are scheduled to.
- No limits/delays means no more data saved onto the player for tracking, just basic (separate) tags for the server and client, so there's no incompatibility with LabyMod or other mods that change player data significantly.
- There are four message schedules:
on_first_join (sent when a player joins a level for the first time
on_join_level (sends every time a player joins a level)
on_death (sent every time the player dies)
on_respawn (sent every time the player respawns)
- There are two message types:
chat (sends like a regular chat message)
overlay (displays centered on the client, above the action bar)
- Messages are constructed with key names: identifier, schedule, type, repeats, pack_intro, link, and text.
- This is how you send a chat message with a link, that never repeats, when the player joins a server for the first time. You can also display the player's name and the message's link in the message.
{
"identifier": "default_message",
"schedule": "on_first_join",
"type": "chat", "repeats": false,
"pack_intro": false, "link": "https://www.google.com",
"text": "Hi, %player%! Visit %link% for more info on this server!"
}
- Some key names are not required, like repeats, link, and pack_intro.
if link is not present, no link will be attached.
if repeats is not present, it will default to false.
if pack_intro is not present, it will default to false.
-
pack_intro is slightly different from repeats, it will check if the client has ever received the "identifier.firstJoin" tag from joining any level, and will never repeat first join messages if the message has pack_intro as true.
-
This version is valid for both NeoForge and Fabric.
-
Requires MonoLib.
Do you need a server to play with your friends?
For exceptional server hosting services, look no further than BisectHosting. Of course, you can install all the mods or modpacks you want, and their support team is always available to help you.
With the code "Lupin" you will get a 25% discount! Click here!
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:vtggzSb5:Tra0KX5Q"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vtggzSb5:Tra0KX5Q"
}



