Tags
Creators
Details
0.2.0
Compatibility
Changes
Lightning 0.2.0, rebuilt from scratch.
Lightning has been rewritten from the ground up. New code, new configs, and a much bigger idea: instead of only adding commands, Lightning now makes every message on your server look the way you want, even the ones from plugins you can't change.
This is a beta. Please report anything odd at support.denizenmc.com.
Fresh out of the oven
- Charge any plugin's text. Write MiniMessage in any plugin's config and Lightning brings it to life right before players see it. No prefixes, no hooks.
- Everywhere players read. Chat, action bars, titles, boss bars, tab list, scoreboards, menus, items, holograms, dialogs, the server list, and kick and ban screens.
- Sparks. Your own reusable tags: colors, prefixes, formulas, scales, rotating lines, random picks, and lines in each player's language.
- Bolts. Move a message to the action bar or a title, play a sound, or hide it, all from inside the text.
- Player faces with
<face>, plus<center>,<clock>and small caps. - Rewires. Restyle messages baked into plugins or Minecraft itself, including the ban screen.
- Pulse keeps animated lines moving on scoreboards and tab lists that never refresh on their own.
- Guard keeps whatever players type as plain text, so nobody can sneak tags into your messages.
Custom commands, remade
- Real Brigadier commands with tab completion and red error hints as you type.
- Typed arguments, subcommands, cooldowns, usage limits and per-command messages.
- Actions read top to bottom: messages, console and player commands, broadcasts, waits, checks and chance.
- Player input is always safe. It can't become a tag, a placeholder or a selector like
@a.
Kitchen tools
/lightning inspectshows where any message came from./lightning checkfinds broken tags across every plugin's config./lightning convertturns old&codes into MiniMessage, with a backup./lightning parseand/lightning debugfor testing and troubleshooting.
Under the hood
- Text without tags is skipped after one quick look, and anything that reads the same for everyone is only prepared once.
- Folia support throughout.
- Cleaner configs with simple keys and plain explanations.
Before you update
- Lightning now needs Paper or Folia 1.21+ and Java 21. Spigot and older versions are no longer supported.
- Old configs don't carry over. Commands use a new layout, so start from the new
commands/examples.yml. - Action hooks on other plugins' commands are gone for now. Most of what they did is easier with rewires and bolts.
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:BzegqUOE:vSg6pFLP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BzegqUOE:vSg6pFLP"
}

