HonorCore

Most reputation plugins give you a number in chat and stop there. HonorCore turns that number into something the player can feel: a tier that grants permissions, unlocks commands and opens more doors by having a good behavior and reputation around the server. It can also punish them based on your settings.



By default: one point per player, and a 24h wait before you can honor someone else. Both rules are yours to change.

You will have full control of how players use the system. Make sure to take a quick look at all the config before using the plugin on your main server.

• Playtime — playtime required before honoring.
• Account age — prevents new multi-accounts from giving a lot of honor points.
• Minimum reputation or minimum tier.
• Rank / permission — rank or permission requirement before honoring.
• Shared playtime — you can only honor who you play with.
• Same IP blocked — prevents more alts from giving points.
• Distance and both online, if you want it to be a face to face thing.
• Requirements on the receiver too: account age and a reputation floor, so a farm of fresh accounts cannot collect honor.
• Daily limit on top of the cooldown.

Create as many tiers as you want, positive and negative. Each one can grant permissions, block commands, apply potion effects and run commands. It is really up to your creativity.

Examples:

unlocks and blocks are the text the menu shows, written by you. The plugin never generates it from permission nodes, because nobody wants to read essentials.sethome.multiple.3 in a tooltip.

• Staff — /honor take and /honor set, always written to the audit log with who did it, so you can track it.
• Reports — /report <player> <reason> goes to a queue. Staff approves or denies it from a menu. Nothing is applied automatically, because a group of players piling on reports should not be able to punish someone on their own.
• PvP kills — with arena exclusion, a self defence check and a per pair cooldown, so nobody can farm a friend's reputation into the ground.
• Combat logging.
• Punishments — see below.
• Griefing attempts — see below.
• Inactivity decay, optional, so the leaderboard shows who's more active than others.

Reputation for playtime, and able to set up rewards for a clean 30 day record.



Instead of hooking one punishment plugin, HonorCore watches the punishment commands. You decide what each one costs:

That works with LiteBans, AdvancedBan, CMI, EssentialsX, LibertyBans or whatever you use — and it keeps working the day you switch. It does not see punishments issued from a web panel or from another server in the network, since no command runs on this server in that case.

And the opposite direction, with your commands:



Griefing attempts are detected without any dependency: when a player tries to break, place or open something inside a claim that is not theirs, the protection plugin cancels the action — and that signal is identical whether the server runs WorldGuard, GriefPrevention, Lands, Towny, Residence or PlotSquared.

Off by default, with a long cooldown and a daily cap, because protection plugins also cancel harmless clicks.

• Four menus — profile, leaderboard, tier list and the report queue — with slots, materials, names, lore and actions defined in gui/*.yml. Customize all of them to your liking.
• Every message is in a language file. English and Spanish included; copy en_US.yml to make your own. Missing keys fall back to English, so a half finished translation still works.
• Colours: legacy &a, hex &#RRGGBB and <gradient:#ff0000:#0000ff>text</gradient>
• A sound per event — honor received, honor lost, reported, tier up, tier down, menus — each with its own volume, pitch and optional title or action bar.

Aliases: /rep, /reputation. Full tab completion everywhere, and everything that can work from the console does.



Players — on for everyone by default. Turn them off if you want.

Staff and administration:

honorcore.admin already includes honorcore.staff, which already includes honorcore.notify. One node is enough.

Bypasses — deliberately NOT handed to admins by default, so your staff sees the same rules as the players while they test:

honorcore.* grants absolutely everything, bypasses included.

A typical LuckPerms setup, so that only settled players hand out honor:



Use them as a chat prefix, a tab tag or a scoreboard line. There is also an optional built in nametag module using scoreboard teams, if you do not already run TAB.



Events: ReputationChangeEvent (cancellable, and the amount can be rewritten), TierChangeEvent, HonorGivenEvent (cancellable).

• 1.16 → 1.21+ on a single jar. Compiled against the 1.16.5 API and targeting Java 8, so it loads on the Java 8 of a 1.16 server and on the Java 21 of 1.21. No NMS, no version modules.
• SQLite or MySQL. Point several servers at the same MySQL and they share reputation.
• Full audit log. Every single change is recorded with actor, amount, reason and origin — staff decisions included.
• No hard dependencies. PlaceholderAPI is optional.

HonorCore is free.

You may:

• Run it on any server or network you own or administrate, public or private, with no player limit.
• Build on the API from your own plugins and share those freely.
• Decompile or modify it for your own private use on your own server.

You may not:

• Re-upload or redistribute it anywhere — other sites, forums, Discord servers, file hosts, leak sites, plugin packs, server templates or pre-made setups.
• Sell it or rent it.
• Claim authorship, or publish a renamed or modified version as your own work.
• Remove or alter the author credits.