2.0
Compatibility
Changes
TartanMsg | Simple Cross-Server MessagingTartanMsg is a straightforward, high-performance messaging plugin designed for server owners who want a fast, reliable, and clean /msg system. It features a hybrid JAR architecture, meaning the exact same file works seamlessly on your Velocity proxy and your standalone Paper/Spigot servers.๐ Why Choose TartanMsg?Hybrid Support: A single .jar file for both Velocity and Bukkit/Paper.Network-Wide Chat: When deployed on Velocity, players can message each other across all sub-servers effortlessly.Wide Compatibility: Works seamlessly across modern and legacy Minecraft versions (Spigot/Paper from 1.8 to 1.21+, Velocity from 3.3.0 to 4.x).Privacy Controls: Built-in toggle system allowing players to enable or disable private messages on demand (/msgenable & /msgdisable).Fully Customizable Multi-Language System: Easily configure your default language in config.yml and modify every text and prefix inside the /languages/ folder (en.yml, it.yml).No External Dependencies: All necessary libraries (Adventure API, SnakeYAML) are safely shaded inside the compiled JAR.๐ ๏ธ Commands & PermissionsCommandDescriptionAliasesPermission/msg <player> <message>Send a private message to anyone./tell, /w, /messagetartanmsg.use/msgenableEnable your private messages./msgentartanmsg.use/msgdisableDisable your private messages./msgdistartanmsg.use๐ Installation GuideDownload TartanMsg-2.0.jar.Drop the JAR file into the plugins/ folder of your Velocity proxy or your Paper/Spigot server.Restart or reload your server to generate default files.Customize your configurations and text formatting inside plugins/TartanMsg/.๐ป Technical SpecsOptimized for high performance and minimal resource usage.Powered by Kyori Adventure API for pristine, bug-free text formatting across all platforms.
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:gEVwHwm0:SGNF7kKC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gEVwHwm0:SGNF7kKC"
}

