Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 years ago
Updated last week
All versions
5.0.0-beta.1
Beta
5.0.0-beta.1 - Paper7 months ago 574
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
Platforms
Folia
Paper
Changes
This update removes a lot of legacy code, making the code-base a great bit more simple and a lot more performant.
Requirements
- The Paper part now requires at least Paper 1.20.1 and no longer supports Spigot
- The universal jar has been removed. Each platform now has its own jar (that is as small as possible)
- Maintenance now requires at least Java 21
Changed
- Added mode-based maintenance messages for
ping-message,player-count-message, andplayer-list-hover-message- You can have different MOTDs depending on the pre-configured mode, e.g. a generic
defaultor one forupcoming-release. - Updated proxy/global toggle syntax:
/maintenance on [mode]- For proxy servers:
/maintenance on global [mode],/maintenance on <server> [mode]
- For proxy servers:
- Other updated commands:
/maintenance motd [timer] [mode],/maintenance setmotd [timer] [mode] ...,/maintenance removemotd [timer] [mode] ...
- You can have different MOTDs depending on the pre-configured mode, e.g. a generic
- Added
%REASON%variable to messages, using theactive-reasonconfig option. This allows for dynamic MOTD and other messages via a quick command without modifying the messages themselves- Can be changed via the
/maintenance setreason <reason>command
- Can be changed via the
- Velocity/Bungee: Replaced
mysqlsection withredis. This is a more suitable database for such reading and sharing of data and no longer means some server pings can take multiple seconds, if you have multiple proxies linked
Fixed
- Velocity/Bungee: Fixed the
/maintenance schedulecommand for single servers having swapped time arguments.
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:VCAqN1ln:1BdVGCru"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VCAqN1ln:1BdVGCru"
}

