Links
Tags
Creators
Details
2.0.0+neoforge-1.20.6
Compatibility
Changes
2.0.0 - rewritten, and now runs almost everywhere
One jar now covers every Bukkit-family server from Minecraft 1.8.8 to 26.2 - Spigot, Paper, Purpur and Folia. Velocity, BungeeCord, Fabric and NeoForge builds are included too.
The jar went from 771 KB to about 30 KB, because the bundled HTTP library was replaced with the HTTP client built into Java. There are now no third-party dependencies at all, so nothing can clash with other plugins.
Every published build was tested by booting a real server and checking that the message actually arrived at a webhook.
Fixed
- Worked only on 1.20 to 1.20.6. It now runs on 1.8.8 through 26.2 from one file.
- Used only the old chat event, which Paper has deprecated for removal. Paper's modern chat event is now used automatically wherever it exists.
- Sent one HTTP request per chat message, which Discord rate-limits almost immediately on a busy server. Messages are now batched, and a rate limit pauses and retries instead of losing messages.
- Players could ping
@everyoneor any role just by typing it in chat. No message can trigger a mention any more. - Players could reshape the Discord log using markdown. Chat text is now escaped.
- Messages cancelled by other plugins (muted players, word filters) were still relayed. They no longer are.
- The plugin described itself as "the best currency plugin out there".
New
- Player name and skin shown as the Discord message author
/discordchatloggerwithreload,testandstatus- Optional join/leave and death relaying
- Optional
server-namelabel, for sharing one channel between servers - Velocity, BungeeCord, Fabric and NeoForge support
Source and issue tracker: https://github.com/SawyerTheNerd/Discord-Chat-Logger
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:iILQhAq4:DtGzAtHh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iILQhAq4:DtGzAtHh"
}

