BitAspire Wiki
CyberTokensCyberTokens

Economy Overview

Understand how CyberTokens models balances, formatting, storage, and account limits.

CyberTokens is intentionally simple: one global currency, one balance per player, one transaction history stream, and one shared set of formatting and payment rules.

Core model

AreaHow it behaves
Currency countOne currency for the entire plugin
NamesSeparate singular and plural labels
SymbolCustomizable string such as $, , or S/.
FormattingCompact suffixes, decimal trimming, rounding mode, and overflow style
Starting balanceApplied to first-time users
Maximum balanceHard cap that prevents balances from growing past the configured value
Negative balancesBlocked when prevent-negative is enabled

Number formatting

config.currency.format controls how large values are presented to players. That includes:

  • custom suffix labels like K, M, B, Qa, or Qi
  • decimal precision for compact output
  • whether .00 should be trimmed away
  • rounding mode and overflow style

This matters most for /money, /baltop, /pay, placeholders, and any plugin that reads the formatted balance string.

Storage backends

CyberTokens supports:

  • SQLITE
  • MYSQL / MARIADB
  • POSTGRES / POSTGRESQL

SQLite is the easiest default for a single server. SQL backends make more sense if you want shared storage, backups outside the server folder, or easier external inspection.

Runtime behavior

  • Balances are cached to reduce repeated database reads.
  • Autosave can run on online users, offline users, or both.
  • After each autosave cycle, cached data can be cleared and reloaded.
  • Transaction history can be retained and purged over time.

Single-currency by design

If your economy needs distinct currencies with their own files, representation ranges, and shops, move to XenoTokens instead of trying to stretch CyberTokens past its intended model.

Last updated on

On this page