NexaTrade Documentation

Main runtime settings, license, modules, limits, storage and feature behavior.

# ...
# Short documentation excerpt from config.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
server-id: "server-1"
license-key: "LICENSE"
color-format: "legacy" # legacy or minimessage

trade:
  enabled: true
  request-timeout-seconds: 60
  request-cooldown-seconds: 8
  final-countdown-seconds: 5
  max-offer-items: 18
  transaction-timeout-seconds: 45
  cancel-on-inventory-close: true # Safety locked: closing any active trade view cancels the session.
  shift-right-click: true
  require-same-world-proximity: false
  blocked-worlds: []
  blocked-regions: []
  blocked-gamemodes:
    - SPECTATOR
  compact-number-format: true

cross-server:
  enabled: false # legacy display flag; effective module gate is modules.yml
  require-production-database: true
  stop-trades-if-redis-down: false
  allow-single-server-trades-if-redis-down: true
  player-lookup-mode: LOCAL_ONLY
  redis-failure-behavior:
    disable-cross-server: true
    allow-single-server-trades: true
    cancel-active-cross-server-trades: true
  player-ttl-seconds: 15
  heartbeat-seconds: 5
  lock-ttl-seconds: 120

# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/config.yml to review every setting.
# ...

Plugin-specific YAML settings used by this product.

# ...
# Short documentation excerpt from currencies.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
coinsengine:
  enabled: true
  auto-register: true
  disabled-currencies: []

currencies:
  vault:
    enabled: true
    type: "vault"
    display-name: "Coins"
    cross-server-safe: true
    menu:
      material: "EMERALD"
  exp:
    enabled: true
    type: "exp"
    display-name: "EXP"
    cross-server-safe: false
    menu:
      material: "EXPERIENCE_BOTTLE"
  internal:
    enabled: true
    type: "internal"
    display-name: "Nexa Coins"
    cross-server-safe: true
    menu:
      material: "SUNFLOWER"
  coinsengine-example:
    enabled: false
    type: "coinsengine"
    currency-id: "coins"
    display-name: "CoinsEngine Coins"
    cross-server-safe: true
    menu:
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/currencies.yml to review every setting.
# ...

Economy, product, currency, marketplace or limit behavior.

# ...
# Short documentation excerpt from limits.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
limits:
  min-currency-amount: 1
  max-currency-amount: 1000000000
  daily-completed-trades: 100
  same-player-cooldown-seconds: 30
  new-player-protection:
    enabled: true
    high-value-threshold: 100000
    require-extra-confirmation: true

fees:
  enabled: false
  percentage: 0.0
  fixed: 0.0
  per-currency:
    vault:
      percentage: 0.0
      fixed: 0.0

rank-limits:
  default:
    daily-trades: 10
    max-trade-value: 100000
  vip:
    daily-trades: 50
    max-trade-value: 1000000
  admin:
    bypass: true

first-join-protection:
  enabled: true
  min-playtime-minutes: 120
  max-trade-value: 50000
  block-trading-with-risky-players: true
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/limits.yml to review every setting.
# ...

Economy, product, currency, marketplace or limit behavior.

# ...
# Short documentation excerpt from marketplace.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
marketplace:
  enabled: false
  max-active-offers-per-player: 25
  allow-partial-accept: false
  require-escrow: true
  public-offers: true
  allow-offline-accept: false
  expire-after-hours: 48
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/marketplace.yml to review every setting.
# ...

Feature modules and ready setup presets.

# ...
# Short documentation excerpt from modules.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
preset: SAFE # SIMPLE, SAFE, NETWORK, ECONOMY, ENTERPRISE, CUSTOM

modules:
  single-server-trade: true
  double-confirmation: true
  countdown: true
  escrow: true
  item-snapshot: true
  fingerprint: true
  blacklist: true
  illegal-item-detector: true
  receipt: true
  history: true
  admin-logs: true
  signed-audit-log: true
  recovery: true
  claim-storage: true
  templates: false
  reputation: true

  cross-server: false
  redis: false
  mysql-required: false
  marketplace: false
  contracts: false
  scheduled-trades: false
  scam-reports: false
  disputes: false
  refunds: false
  replay: false
  smart-risk-check: false
  price-database: false
  discord-webhooks: false
  rest-api: false
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/modules.yml to review every setting.
# ...

Economy, product, currency, marketplace or limit behavior.

# ...
# Short documentation excerpt from prices.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
enabled: false
source: MANUAL # MANUAL, TRADE_HISTORY_AVERAGE, MARKETPLACE_AVERAGE, HYBRID
defaults:
  DIAMOND: 100
  EMERALD: 75
  NETHERITE_INGOT: 2500
custom-items: {}
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/prices.yml to review every setting.
# ...

Economy, product, currency, marketplace or limit behavior.

# ...
# Short documentation excerpt from reputation.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
reputation:
  enabled: true
  show-warning-before-trade: true
  allow-reviews: true
  allow-scam-reports: true
  require-completed-trade-for-review: true
  same-player-review-weight-limit: true
  admin-can-reset: true
  tiers:
    trusted: 85
    normal: 60
    risky: 30
  weights:
    completed-trade: 1
    negative-review: -15
    neutral-review: -3
    scam-report: -25
    dispute: -10
  review-cooldown-hours: 24
  same-partner-review-weight-limit: 3
  display:
    show-tier-to-players: true
    show-score-to-players: false
    show-negative-count-to-players: false
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/reputation.yml to review every setting.
# ...

# ...
# Short documentation excerpt from messages.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
prefix: "&8[&bNexaTrade&8]&r "
no-permission: "&cYou do not have permission."
player-only: "&cOnly players can use this command."
unknown-player: "&cThat player is not online on this server."
unknown-network-player: "&cThat player is not online on the network."
usage: "&7Use &f/trade <player>&7, &f/trade accept&7, or &f/trade help&7."
module-disabled: "&cThe %module% module is disabled."
maintenance: "&cTrade system is currently under maintenance."
license-status: "&7License status: &f%status%"
request-sent: "&aTrade request sent to &f%player%&a."
request-received: "&f%player% &awants to trade."
request-accept-button: " &a&l[ACCEPT]"
request-deny-button: " &c&l[DENY]"
request-accept-hover: "&7Click to accept &f%player%&7's trade request."
request-deny-hover: "&7Click to deny &f%player%&7's trade request."
cross-server-unavailable: "&cCross-server trade service is temporarily unavailable. Your trade has been safely cancelled."
request-expired: "&cTrade request expired."
request-denied: "&cTrade request denied."
trade-started: "&aTrade started with &f%player%&a."
trade-cancelled: "&cTrade cancelled: %reason%"
trade-completed: "&aTrade completed. Receipt: &f%receipt%"
confirm-reset: "&eThe offer changed. Confirmations were reset."
confirmed: "&aYou confirmed the trade."
waiting-confirm: "&7Waiting for the other player to confirm."
countdown: "&eTrade completes in &f%seconds%&e..."
inventory-full-claim: "&eSome items were moved to your claim storage. Use &f/trade claims&e."
blacklisted-item: "&cThat item cannot be traded."
illegal-item: "&cThat item failed safety validation and cannot be traded."
currency-offered: "&aOffered &f%amount%&a."
currency-not-found: "&cUnknown currency."
currency-insufficient: "&cYou do not have enough %currency%."
limit-reached: "&cTrade limit reached: %reason%"
trade-toggle: "&7Trade toggle is now &f%status%&7."
ignore-updated: "&7%player% is now &f%status%&7."
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/messages.yml to review every setting.
# ...

Purpose: Provides economy withdrawals, deposits, prices, banks or metadata through Vault.

Troubleshooting: If balances, rewards or banks do not work, confirm Vault has an active economy provider and that no economy plugin loads after this product.

1. Install Vault and one compatible economy or permission provider.
2. Restart the server and confirm Vault reports a provider in console.
3. Enable prices, banks, rewards or currency features that depend on Vault.
4. Test one deposit and one withdrawal with a non-op account.

Purpose: Provides a named currency provider for prices, rewards, trades or shop transactions.

Troubleshooting: If transactions fail, verify the currency id, provider startup order and whether the player has enough balance or inventory space.

1. Install the economy/shop provider and create the currency key used by this product.
2. Match the currency id in the product config.
3. Test a buy/sell/withdraw flow with a player account.
4. Check transaction logs if balances do not change.

Purpose: Registers or consumes PlaceholderAPI values for scoreboards, formats and external displays.

Troubleshooting: If values stay blank, reload expansions and verify the identifier exactly matches the placeholder shown in this docs page.

1. Install PlaceholderAPI or the listed placeholder provider.
2. Install required expansions when the provider uses external expansions.
3. Use the exact placeholder identifiers documented in this page.
4. Reload the display plugin after changing scoreboard, tablist, menu or chat format files.

Purpose: Connects gameplay behavior to claims, regions or group ownership rules.

Troubleshooting: If region or claim rules do not apply, check region priority, claim ownership, world names and whether the hook is enabled.

1. Install the claim or region plugin before this product starts.
2. Create the region, claim, town or faction area you want the plugin to read.
3. Enable the matching hook in the integration/config file when a toggle exists.
4. Test the protected workflow inside and outside the region with a normal player.

Purpose: Adds Bedrock player compatibility handling for request, GUI or input workflows.

Troubleshooting: If Bedrock users cannot complete the workflow, test the same flow on Java first and then check Floodgate UUID/input handling.

1. Install Floodgate/Geyser and confirm Bedrock players can join normally.
2. Enable Bedrock compatibility options when the product exposes them.
3. Test GUI/request flows with one Java and one Bedrock account.
4. Adjust confirmation or input settings if Bedrock clients cannot click a specific UI path.

Purpose: Synchronizes runtime state between servers in a network setup.

Troubleshooting: If sync fails, verify server ids are unique, secrets match and the Redis/proxy channel is reachable from every server.

1. Configure a unique server id for every server in the network.
2. Set the same secret/channel values on every connected server.
3. Start Redis or the proxy messaging layer before testing cross-server state.
4. Test the same player workflow on two servers and watch for sync warnings.

Purpose: Publishes logs or events to Discord channels or webhooks.

Troubleshooting: If Discord messages do not send, check webhook validity, rate limits and whether the event type is enabled.

1. Create the webhook or channel integration in Discord.
2. Paste the webhook/token into the product config if the feature exists.
3. Send one test event from the product.
4. Confirm Discord receives only the events you want to expose.

1. Define counterparties, items, currency and expiry.
2. Test accept/deny and partial offer changes.
3. Verify commit/rollback and receipt creation.

1. Review receipt, snapshots and history.
2. Use dispute/reputation tools without editing inventory directly.
3. Document refund or claim result in the case.

Check request distance, disabled worlds, ignore/privacy toggles, cooldowns and whether another plugin blocks the trade command alias.

Look for inventory click errors, blacklist violations, currency withdrawal failure or a storage write rollback in console.

Verify provider balance, currency key, Vault/CoinsEngine hook status and whether the trade requires escrow before confirmation.

Check material, display name, lore and NBT matching rules. Custom item plugins may require explicit id whitelisting.

Verify host, port, database name, credentials, firewall access and the storage type in the generated YAML file.

Confirm transaction logging is enabled and storage writes complete after both players accept the trade.