Links
Tags
Creators
Details
1.0.6
Compatibility
Changes
✅ ClipsEZEconomy v1.0.6 – Changelog
⭐ New Features
-
Added automatic economy autosave system
- Balances are now saved periodically instead of on every transaction
- Improves performance on busy servers
- Reduces risk of data loss during crashes or forced shutdowns
-
Added internal economy service (Vault-ready)
- Exposes ClipsEZEconomy through a clean service provider
- Allows other plugins to safely hook into the economy
- Prepares the plugin for future Vault support (Vault is NOT required)
-
Added configurable chat input timeout for bank actions
- Prevents chat from being permanently captured if a player goes AFK
- Timeout duration is configurable in
config.yml
🐛 Fixes
- Fixed economy data not saving reliably during heavy transaction spam
- Fixed chat getting stuck after bank actions when players disconnect or reload
- Fixed bank withdrawals removing balance without giving emeralds when inventory was full
- Fixed GUI drag, shift-click, number-key, and double-click exploits in the bank menu
- Fixed potential balance desync during partial bank transactions
- Fixed silent failures when saving balances to disk
✨ Improvements
- Improved overall economy performance by reducing disk writes
- Improved bank transaction safety using atomic deposit and withdraw logic
- Improved numeric input validation for bank chat actions
- Improved cleanup handling on player quit, kick, and server reload
- Improved internal architecture for future expansion and Vault compatibility
⚠ IMPORTANT: CONFIG.YML CHANGES REQUIRED
Version 1.0.6 introduces NEW config entries.
If you update from 1.0.5 or earlier, you MUST add the following to your existing config.yml:
✅ Add these sections (or delete config.yml to regenerate)
data:
autosave-interval-seconds: 300
bank:
chat-input-timeout-seconds: 15
withdraw:
drop-if-inventory-full: true
drop-message-enabled: true
messages:
withdraw-inventory-full: "%prefix%&cYour inventory is full. Clear space before withdrawing."
withdraw-dropped: "%prefix%&e%amount% &7emerald(s) were dropped because your inventory was full."
You do NOT need to regenerate player data files.
All existing balances remain fully compatible.
📝 Upgrade Instructions
- Stop your server.
- Replace the old JAR with ClipsEZEconomy v1.0.6.
- Update your
config.ymlwith the new entries (or delete it to regenerate). - Start your server.
- Run
/clipsezeconomy reload(optional).
🎉 1.0.6 Summary
This update focuses on stability, data safety, and exploit prevention.
ClipsEZEconomy is now safer for production servers, more resilient under load, and fully prepared for future Vault integration — without breaking existing player data.
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:p5a0lK0N:T3hbzLgQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:p5a0lK0N:T3hbzLgQ"
}

