Links
Tags
Creators
Details
XConomy-Bukkit-2.26.7
Compatibility
Changes
XConomy V2.26.7 Update Log
You Must Delete message.yml to use this version!
You Must Delete message.yml to use this version!
You Must Delete message.yml to use this version!
Added
Added modern interactive pagination to help, balance leaderboard, and transaction tracking views.
Added /xconomy track flow <transaction_id> for detailed transaction inspection. Added transaction detail output with amount, resulting balance, participants, transaction type, time, trace ID, parent transaction, command source, comment, and money-flow summary.
Added transaction ID tab-completion hints for the flow command.
Added localized usage messages for incomplete or invalid command arguments.
Improved
Redesigned help, balance leaderboard, and transaction tracking interfaces with MiniMessage styling.
Transaction records are now clickable and directly open their transaction details.
Pagination buttons now directly open the selected page.
Improved /xconomy track tab completion for income, expense, player names, cleanup, flow, page numbers, and cleanup durations.
Preserved the entered leaderboard command alias when using pagination buttons. Added automatic recovery for invalid message.yml files by backing them up and regenerating defaults.
Migrated default language messages to MiniMessage and added warnings for legacy color codes.
Fixed
Fixed MiniMessage click and hover events being lost through legacy string serialization.
Fixed /xconomy track completions being intercepted by the generic command completion branch.
Fixed malformed default Chinese help language YAML causing plugin startup failures.
Fixed Maven shading compatibility with Java 21 bytecode and MiniMessage 5.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:UdMN9hv5:RgwiHCMo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UdMN9hv5:RgwiHCMo"
}

