Skip to content

PureEconomy 1.2.0

Latest

Choose a tag to compare

@TamaWish TamaWish released this 13 Sep 15:13

Paper-only thin JAR, no MySQL on the scoreboard thread, and SQL that scales.

Drop PureEconomy-1.2.0.jar on Paper, Purpur, or Folia. First boot downloads Kotlin, Hikari, Caffeine, and JDBC drivers through Paper libraries: and therefore needs access to Maven Central once. Spigot is no longer supported.

For proxy networks, install PureEconomy-Velocity-1.2.0.jar or PureEconomy-Bungee-1.2.0.jar on the proxy and the Bukkit artifact on every backend. Configure the same shared MySQL database and currency definitions on every instance.

Highlights

  • Native Velocity and BungeeCord/Waterfall plugins with authoritative, strongly consistent MySQL transactions.
  • Thin Bukkit JAR using Paper's library loader; heavy JDBC and runtime dependencies are no longer shaded.
  • SQL schema v2 with DECIMAL(20,8), UPSERT saves, indexed server-side /baltop, and automatic VARCHAR-to-DECIMAL migration.
  • Multi-currency PureEconomyAPI, reason-coded mutation results, Vault support, and PlaceholderAPI wallet/bank placeholders.
  • Memory-only PlaceholderAPI balance reads with deduplicated stale-while-refresh network caching.
  • Folia-aware scheduling and globally dispatched post-success economy events.

Reliability and threading

  • Scoreboard rendering never waits for MySQL.
  • Successful network mutations update the balance cache immediately and preserve specific failure reasons such as insufficient funds and maximum balance.
  • Bukkit command parsing, permissions, player lookup, messaging, and transaction events run on their proper Paper/Folia thread.
  • Network account setup on join runs asynchronously.
  • Dirty cache evictions remain queued across overlapping save passes.

Upgrade notes

  • Back up plugins/PureEconomy/ before upgrading or changing storage.
  • Existing configuration and language files are merged with new defaults without overwriting custom values.
  • Existing SQL amount columns are migrated automatically on startup.
  • YAML remains suitable for small servers; SQLite or MySQL is recommended for busy installations.

See the README and full changelog for setup and technical details.