2.0.0+forge-26.2
Compatibility
Changes
Forge mod for Minecraft 26.2. Server-side only, no client install needed.
Now on every platform: one Bukkit plugin jar for Spigot, Paper, Purpur, Folia & forks from 1.8.8 to 26.3, plus mods for Fabric/Quilt, NeoForge and Forge (1.20 to 26.3). Same features, same config and language files everywhere. The mods are server-side only, so players join with a vanilla client.
New
- In-game menu (
/pvp): toggle your PvP, see your combat status. Admins also get cooldown ±5s, a custom cooldown dialog (click the clock, 1.21.6+), feedback mode, language switch, reload and a paged player list to toggle anyone's PvP. - More commands:
/pvp status [player],/pvp players,/pvp set <player|*> <on|off|toggle>,/pvp display <actionbar|chat>,/pvp language <code>,/pvp version, clickable/pvp help. Aliases/pvpcontroland/pvptoggle. Tab completion everywhere. - Languages: English and German included; add your own
lang/messages_xx.yml. Every text editable, with&colors and&#RRGGBBhex colors (1.16+). - Blocks more damage sources: projectiles (arrows, tridents, snowballs, fireworks, fishing hooks), player-lit TNT, harmful splash and lingering potions (Bukkit).
- Combat notice when you enter combat, sounds for toggles and menu clicks.
- New config options:
language,default-pvp-enabled,notify-combat-tag,sounds,open-menu-without-arguments,disabled-worlds. - Permission
pvpcontrol.bypass.cooldown. On Fabric, LuckPerms / fabric-permissions-api is used automatically; otherwise operators are admins.
Changed
- Missing permissions now show a message instead of failing silently.
- Rewritten, shorter messages with a consistent style.
- Player PvP states are stored in
players.yml; states from 1.0.x are imported automatically on join. - New options are added to an existing
config.ymlwithout touching your comments.
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:D44U32Px:TshsF9oN"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:D44U32Px:TshsF9oN"
}

