Tags
Creators
Details
1.7.5
Compatibility
Changes
This update focuses entirely on polish, clarity and day-to-day administration. It makes commands easier to discover, player redemption history easier to inspect, the code editor less chaotic and Discord notifications look like a premium integration.
Added
- Added a completely redesigned
/codeshelp menu.- Paginated for future commands.
- Shows only commands the sender can use.
- Includes a short description for every command.
- Commands are clickable in-game and include hover descriptions.
- Console output remains clean and readable.
- Added
/codes help [page]. - Added paginated personal statistics with
/codes stats [page]. - Added
/codes stats <player> [page]for administrators.- Supports online players.
- Supports offline players known to the server cache.
- Uses UUID data internally, so name changes do not break stored history.
- Works from the server console when a player is specified.
- Added the new
mpromocodes.admin.stats.otherspermission. - Added permission-aware tab completion for help, stats, menu, reload, health and webhook commands.
- Added Discord Components V2 messages with:
- Clean accent-free containers.
- Large emoji header sections with logo thumbnails.
- Separate player, promo-code, result and server-context sections.
- Clean separators.
- Emoji-labelled values and compact code styling.
- Discord-native absolute and relative timestamps.
- Success, failure and test designs.
- Added the official MPromoCodes Modrinth image as the default webhook avatar and thumbnail.
- Added webhook campaign information.
- Added configurable compact UUID display.
- Added configurable webhook field visibility.
- Added an automatic legacy-embed fallback if Discord rejects a Components V2 request.
- Added all new messages to both English and Slovak localization files.
- Added automatic version-aware
config.ymlmigration with collision-safe backups.
New Webhook Settings
These values are included in the fresh configuration generated during an upgrade and can be adjusted under discord-webhook:
discord-webhook:
message-style: "COMPONENTS_V2" # COMPONENTS_V2 or LEGACY_EMBED
fallback-to-legacy: true
avatar-url: "https://cdn.modrinth.com/data/5XgdhBMc/90edf839b06799d8801b81a1942416b3b68eeeca_96.webp"
branding:
show-logo: true
logo-url: "https://cdn.modrinth.com/data/5XgdhBMc/90edf839b06799d8801b81a1942416b3b68eeeca_96.webp"
footer: "MPromoCodes"
test-color: "#5865F2"
display:
show-uuid: true
compact-uuid: true
show-server: true
show-campaign: true
show-remaining: true
show-time: true
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:5XgdhBMc:7OTnQASj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5XgdhBMc:7OTnQASj"
}

