Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 4 months ago
All versions
1.0.0
Release
GL-EcoAudit | 1.0.04 months ago 33
Compatibility
Minecraft: Java Edition
1.21.4–1.21.11
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
v1.0.0 – Initial Release
GL-EcoAudit is a plugin that automatically records all /pay economy transactions and provides an in-game GUI to browse sent and received history.
Features
- Automatic transaction recording – Captures every
/paycommand and stores sender, recipient, amount, and timestamp. - Balance verification – Only records transactions that actually succeeded (checks balance change via Vault).
- Shorthand amount support – Accepts
100k,1.5m,2bin addition to raw numbers. - Interactive GUI menus – Browse sent and received transactions with paginated navigation, player heads, and configurable layouts.
- Multi-database support – SQLite (default), H2, MySQL, PostgreSQL, and MongoDB.
- Transaction limits – Configurable max records per player with
DELETE_OLDESTorSTOP_RECORDINGbehavior. - Auto-purge – Automatically removes old records after a configurable number of days.
- Vault integration – Displays player balance in the menu.
- Fully configurable – Messages (
language.yml), menus (menus/), and database (database.yml) are all hot-reloadable via/ecoaudit reload.
Commands
| Command | Description | Permission |
|---|---|---|
/transactions (/trans, /tx) |
Opens the transactions GUI | golden.ecoaudit.transactions |
/ecoaudit reload |
Reloads all configurations | golden.ecoaudit.admin |
/ecoaudit purge [days] |
Purges records older than specified days | golden.ecoaudit.admin |
Dependencies
- Paper 1.21.4
- Vault + any economy plugin (EssentialsX, CMI, etc.)
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:roOL28n6:QsqwqmZx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:roOL28n6:QsqwqmZx"
}

