Tags
Creators
Details
1.0.0
Compatibility
Changes
FuryKarma is a modern and lightweight Minecraft Paper plugin (supporting 26.1.2+ and Java 25) designed to manage player karma. Players can give positive or negative ratings to others with a reason, view detailed profiles, check a leaderboard of the best-rated players, and customize all messages.
It supports both cracked (offline-mode) and normal (online-mode) servers, integrating natively with nLogin to ensure players must authenticate before they can manage karma. It stores all information securely and performantly using an embedded SQLite database.
Features
- Karma Voting: Let players rate others using
/karma <positive | negative> <player> <reason>. - Comprehensive Profile Info: Players can query profiles (with
/karma info) to view net karma, average positive rating, and a history of recent received ratings (relative timestamps included, e.g.,2h ago). - Leaderboard (Top 10): Displays the top 10 players sorted by their positive average rating, including positive/negative counts.
- Embedded SQLite Storage: Efficient database queries for counts and leaderboard without bloat.
- nLogin Compatibility: Safely restricts command usage for unauthenticated players.
- Customizable Cooldowns: Set a cooldown period (defaulting to 24 hours) between votes to prevent spam. Can be bypassed with
furykarma.bypass.cooldown. - Advanced Message Formatting: Supports classic legacy ampersand codes (e.g.,
&e) and modern Adventure MiniMessage tags (e.g.,<green>Text</green>). - Modern Brigadier System: Dynamic command registration via Paper's Brigadier API, featuring smart tab-completion.
Requirements
- Server: PaperMC, Purpur, or any other fork compatible with version 26.1.2 or higher.
- Java: Version 25 (Eclipse Temurin recommended).
- Authentication (Optional): nLogin (fully supported for cracked networks).
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:XognlYxR:T01kmKsd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XognlYxR:T01kmKsd"
}

