Tags
Creators
Details
2.4
Compatibility
Changes
๐ก๏ธ WeGuardian Changelog
Version 2.4 โ Full Messages & GUI Configuration Update
Release Type: Major Configuration & Customization Update Focus: Flexibility, Localization, and Server Branding
โจ New Features
๐ Fully Configurable messages.yml
-
Added a dedicated
messages.ymlfile to centralize all player-facing text -
Every message is now configurable, including:
- Chat messages
- Error messages
- Success messages
- Notifications
- Titles & subtitles
- Action bar messages
๐งฉ GUI Customization (100% Configurable)
-
All GUI elements are now configurable from
messages.yml, including:- GUI titles
- Item display names
- Item lores
- Buttons & descriptions
-
Affected GUIs:
- Punishment GUI
- Duration GUI
- History GUI
๐ ๏ธ New Messages Management System
-
Introduced a MessagesManager system to:
- Load and cache messages efficiently
- Support placeholders across all messages
- Ensure consistent formatting everywhere
-
Uses MiniMessage-compatible formatting for modern text styling
๐ Improvements
-
Removed hardcoded strings from:
- GUI classes
- Input handlers (Reason input, Custom duration input)
- Command feedback messages
-
Improved maintainability and readability of the codebase
-
Easier localization for non-English servers
-
Server owners can now fully brand WeGuardian without touching source code
๐งน Developer & Admin Benefits
- No recompiling required for message changes
- Clean separation between logic and presentation
- Future updates will automatically support new messages via
messages.yml
โ ๏ธ Notes for Updating
- On first startup,
messages.ymlwill be generated automatically - Servers upgrading from older versions should review and customize the new file
- Old message values previously in
config.ymlare now handled viamessages.yml
โ Recommended
Update to WeGuardian v2.4 to unlock full control over messages, GUIs, and server presentation.
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:QsS6k1xF:l0nnmcc3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QsS6k1xF:l0nnmcc3"
}

