Links
Tags
Creators
Details
1.2.0
Compatibility
Required content
Changes
This release includes a lot of new and improved features relating to changelog editing, and finally introduces support for Velocity!
IMPORTANT NOTE: Updating an existing installation to this version will require to to fully delete/re-create your language files, due to a lot of changes and restructuring. After re-creating, you can apply any changes you might've had again! You can get the default
en_USlanguage file from here.
New Features
- Added the ability to show changelog dialogs during the configuration phase (before the player joins the world)
- Finalized the design of the changelog creation/editing UI:
- Individual lines can now be edited and removed after being added
- The editor can now also be used to edit existing changelogs (see below)
- Closing the editor will now prompt the user to confirm they want to discard their changes
- Editor sessions can now be saved for later when closing the UI (unless the server restarts)
- The main changelog UI now has buttons to edit/delete each changelog for administrators
- Fixed Folia compatibility (it was technically compatible already, just not marked as such)
- Added full* support for the Velocity platform *(read more in the details below)
"Technical" / Detailed Changes
- Added a new configuration option
dialog_phase, which specifies whether dialogs should be shown during thePLAYorCONFIGURATIONphase- The default for new installations will be
CONFIGURATION - This setting won't appear in your file automatically for now, so you'll have to add it yourself.
- In case you want the full explanation of the options, you can take a look at the default config file!
- The default for new installations will be
- Added a new
server_changelogs.managepermission that will show edit/delete buttons for every changelog in the regular list UI - Implemented the Velocity platform fully, excluding a few tiny details:
- Players who join the server for the first time will also see changelogs (unlike on paper); since velocity doesn't store this information anywhere, a rework of that system or a separate implementation would be required
- Items for the changelog dialog header don't support custom components yet (again, velocity does not have any built-in parsing for those)
Full Changelog: https://github.com/codingcat2468/ServerChangelogs/compare/v1.1.0...v1.2.0
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:WUtYSCeR:X2WMCOds"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WUtYSCeR:X2WMCOds"
}

