Skip to content
RitomasssCommunity
Product documentation

NexaShop Documentation

NexaShop is a premium server shop and player-shop economy platform with multi-currency products, stock, dynamic pricing, transaction logs and network sync.

21Java target
Paper/FoliaServer target
SQL/RedisStorage mode
Economy hooksHook posture

Overview#

Product purpose, target audience, main systems, dependencies and quick links.

Quick links: Installation, First Setup, Commands, Permissions, Configuration, GUI, Placeholders, Storage, Integrations, Common Setups, Troubleshooting, Changelog and Support.

What is NexaShop?#

A complete shop system for server shops, sell flows, player markets, physical shops, stock and economy controls.

Who is it for?#

Economy, survival, skyblock, prison and network owners replacing basic shop menus with a production commerce layer.

Supported server types#

Survival, SkyBlock, Prison, Lifesteal, SMP and network economy servers.

Main features#

  • Server shops
  • Sell GUI
  • Player shops
  • Physical shops
  • Stock and dynamic pricing
  • Multi-currency
  • Transaction logs
  • Editor GUI
  • Genel Bakis
  • Moduler Shop Platformu
  • Son Uygulanan Production Katmani
  • Server Shop Sistemi

Dependencies#

  • Java 21
  • Paper-compatible server
  • LicenseGate key
  • Vault/PlaceholderAPI/economy hooks optional

Installation#

Installation gets the plugin to boot. First Setup prepares it for production use.

Do not replace plugin jars while the server is running. Always make a backup before updating.
Download the latest NexaShop jar from the official buyer/download source.
Stop the server before replacing the jar.
Upload the jar to /plugins.
Start the server once and confirm the plugin folder was generated.
Configure license, storage and core files listed in the Configuration section.
Restart the server and run the main status/admin command.

First Setup#

Recommended first configuration pass after the plugin has generated its files.

Make one change at a time, reload or restart, then test the player workflow with a real account.

Setup checklist#

  1. Choose modules preset
  2. Configure currencies
  3. Create categories and shops
  4. Set layouts
  5. Give shop permissions
  6. Test buy, sell and player shop flows

Production notes#

  • Give permissions through LuckPerms or your permission manager.
  • Keep backups of YAML files and database tables.
  • Use a staging server before large updates.
  • Do not claim Folia or network support unless the full setup has been tested.

Commands#

Commands, permissions, and usage examples.

Command entries are read from this product's plugin.yml.
/shopCommand
Description

Open and manage NexaShop.

Permission

Not declared in plugin.yml

Example

/shop

/sellCommand
Description

Sell items to NexaShop.

Permission

Not declared in plugin.yml

Example

/sell

/sellguiCommand
Description

Open the NexaShop sell GUI.

Permission

Not declared in plugin.yml

Example

/sellgui

/playershopCommand
Description

Create, search, and browse player-owned shops.

Permission

Not declared in plugin.yml

Example

/playershop

Permissions#

Permission nodes are based on plugin.yml. Assign admin and bypass permissions carefully.

/lp group admin permission set nexashop.admin true
/lp group default permission set nexashop.use true
nexashop.use

Allows opening public shops.

Default: truePlayers
nexashop.sell

Allows using sell commands.

Default: truePlayers
nexashop.admin

Allows administrative NexaShop commands.

Default: opOwner/Admin
nexashop.admin.license

Allows viewing NexaShop license status.

Default: opOwner/Admin
nexashop.admin.network

Allows viewing NexaShop cross-server status.

Default: opOwner/Admin
nexashop.admin.integrations

Allows viewing NexaShop integration diagnostics.

Default: opOwner/Admin
nexashop.editor

Allows using the in-game editor.

Default: opOwner/Admin
nexashop.playershop

Allows creating and using player-owned shops.

Default: truePlayers
nexashop.category.premium

Allows opening the example premium category.

Default: opOwner/Admin
nexashop.shop.premium

Allows opening the example premium shop menu.

Default: opOwner/Admin
nexashop.item.premium_key

Allows seeing and buying the example premium key product.

Default: opOwner/Admin
nexashop.rank.premium

Example requirement permission used by the premium key product.

Default: opOwner/Admin
nexashop.playershop.limit.vip

Example elevated player shop limit.

Default: falseCustom group
nexashop.playershop.limit.elite

Example elevated player shop limit.

Default: falseCustom group
nexashop.price.vip

Example VIP buy discount and sell multiplier.

Default: falseCustom group
nexashop.price.elite

Example elite buy discount and sell multiplier.

Default: falseCustom group

Configuration#

Configuration YAML files below contain short bundled default excerpts, not full files. Message YAML is documented only in Messages & Language.

Validate YAML indentation before restarting the server.
config.yml short excerpt, not full file

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

Short YAML preview only. This block shows selected lines from config.yml. The generated file contains more options than this docs excerpt.
# ...
# Short documentation excerpt from config.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
settings:
  default-currency: "vault"
  language: "en"
  debug: false
  transaction-log-file: true

license-key: "LICENSE"

storage:
  type: "sqlite"
  sqlite-file: "nexashop.db"
  mysql:
    host: "localhost"
    port: 3306
    database: "nexashop"
    username: "root"
    password: ""
    use-ssl: false
  mariadb:
    host: "localhost"
    port: 3306
    database: "nexashop"
    username: "root"
    password: ""
    use-ssl: false

network:
  enabled: false
  server-id: "server-1"
  require-production-database: true
  heartbeat-seconds: 10
  stock-sync: true
  player-shop-sync: true
  redis:
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/config.yml to review every setting.
# ...
Top-level keys

settings, license-key, storage, network, gui, sell-all

Production handling

Back up this file, edit the generated copy under the plugin folder, then run the product reload command or restart for startup-level settings.

currencies.yml short excerpt, not full file

Plugin-specific YAML settings used by this product.

Short YAML preview only. This block shows selected lines from currencies.yml. The generated file contains more options than this docs excerpt.
# ...
# Short documentation excerpt from currencies.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
default: "vault"

currencies:
  vault:
    type: "vault"
    display-name: "$"
  experience:
    type: "experience"
    display-name: "EXP"
  emeralds:
    type: "item"
    display-name: "Emeralds"
    material: "EMERALD"
  playerpoints:
    type: "playerpoints"
    display-name: "Points"
  coinsengine:
    type: "coinsengine"
    display-name: "Coins"
    currency-id: "coins"
  tokenmanager:
    type: "tokenmanager"
    display-name: "Tokens"
    withdraw-command: "tokens remove {player} {amount_int}"
    deposit-command: "tokens add {player} {amount_int}"
  gemseconomy:
    type: "gemseconomy"
    display-name: "Gems"
    withdraw-command: "gems take {player} {amount_int}"
    deposit-command: "gems give {player} {amount_int}"
  ultraeconomy:
    type: "ultraeconomy"
    display-name: "Ultra"
    withdraw-command: "ultraeconomy remove {player} {amount}"
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/currencies.yml to review every setting.
# ...
Top-level keys

default, currencies

Production handling

Back up this file, edit the generated copy under the plugin folder, then run the product reload command or restart for startup-level settings.

layouts.yml short excerpt, not full file

Inventory layout, titles, slots, materials, names, lore and click behavior.

Short YAML preview only. This block shows selected lines from layouts.yml. The generated file contains more options than this docs excerpt.
# ...
# Short documentation excerpt from layouts.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
default:
  content-slots:
    - 10
    - 11
    - 12
    - 13
    - 14
    - 15
    - 16
    - 19
    - 20
    - 21
    - 22
    - 23
    - 24
    - 25
    - 28
    - 29
    - 30
    - 31
    - 32
    - 33
    - 34
  filler:
    material: "BLACK_STAINED_GLASS_PANE"
    name: " "
  back:
    slot: 45
    material: "ARROW"
    name: "<yellow>Back"
  previous:
    slot: 48
    material: "ARROW"
    name: "<yellow>Previous Page"
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/layouts.yml to review every setting.
# ...
Top-level keys

default, sell-gui, hub

Production handling

Back up this file, edit the generated copy under the plugin folder, then run the product reload command or restart for startup-level settings.

modules.yml short excerpt, not full file

Feature modules and ready setup presets.

Short YAML preview only. This block shows selected lines from modules.yml. The generated file contains more options than this docs excerpt.
# ...
# Short documentation excerpt from modules.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
server-shops: true
player-shops: true
stock-system: true
dynamic-pricing: true
rotating-items: true
seasonal-pricing: true
temporary-sales: true
shop-stands: true
npc-shops: true
discord-logs: false
transaction-export: true
migration-tools: true
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/modules.yml to review every setting.
# ...
Top-level keys

server-shops, player-shops, stock-system, dynamic-pricing, rotating-items, seasonal-pricing

Production handling

Back up this file, edit the generated copy under the plugin folder, then run the product reload command or restart for startup-level settings.

shops.yml short excerpt, not full file

Economy, product, currency, marketplace or limit behavior.

Short YAML preview only. This block shows selected lines from shops.yml. The generated file contains more options than this docs excerpt.
# ...
# Short documentation excerpt from shops.yml.
# This is not the complete YAML file.
# Lines before and after this preview are omitted from the docs.
# ...
categories:
  building:
    title: "<aqua>Blocks</aqua>"
    currency: "vault"
    item: "BRICKS"
    slot: 10
    lore:
      - "<gray>Building blocks and decoration materials."
      - "<dark_gray>{products} products available"
  ores:
    title: "<blue>Ores</blue>"
    currency: "vault"
    item: "DIAMOND"
    slot: 11
    lore:
      - "<gray>Ingots, gems, blocks and mine drops."
      - "<dark_gray>{products} products available"
  farming:
    title: "<green>Farming</green>"
    currency: "vault"
    item: "WHEAT"
    slot: 12
    lore:
      - "<gray>Crops, seeds and farm materials."
      - "<dark_gray>{products} products available"
  food:
    title: "<gold>Food</gold>"
    currency: "vault"
    item: "COOKED_BEEF"
    slot: 13
    lore:
      - "<gray>Cooked meals, raw food and snacks."
      - "<dark_gray>{products} products available"
  mobs:
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/shops.yml to review every setting.
# ...
Top-level keys

categories

Production handling

Back up this file, edit the generated copy under the plugin folder, then run the product reload command or restart for startup-level settings.

Messages & Language#

Translation and formatting guidance based on the product's bundled resources.

Message reload follows the product's reload command. Restart after jar, storage or license changes.

How to edit messages#

This product ships messages.yml. Edit the generated copy in the plugin folder, keep placeholders intact, then reload the plugin command or restart for startup-level changes.

Formatting#

<red>Error message</red>
&cLegacy color message
{player} {amount} {reason}
messages.yml short excerpt, not full file
Short YAML preview only. This block shows selected lines from messages.yml. The generated file contains more message keys than this docs excerpt.
# ...
# 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: "<aqua>NexaShop</aqua> <dark_gray>|</dark_gray> "
missing-message: "<red>Missing message: <key>"

no-permission: "<red>You do not have permission."
player-only: "<red>Only players can use this command."
reload-complete: "<green>NexaShop reloaded."
module-disabled: "<red>The <module> module is disabled."
shop-not-found: "<red>Shop not found."
product-not-found: "<red>Product not found."
item-not-found: "<red>Item not found."
category-not-found: "<red>Category not found."
shop-or-item-not-found: "<red>Shop or item not found."
shop-or-category-not-found: "<red>Shop or category not found."
currency-unavailable: "<red>Currency provider is unavailable."
transaction-success: "<green>Transaction complete."
transaction-failed: "<red>Transaction failed: <reason>"
operation-success: "<green><message>"
operation-warning: "<yellow><message>"
operation-failed: "<red><message>"
status-ok: "ok"
status-enabled: "<green>enabled"
status-disabled: "<red>disabled"
status-enabled-plain: "enabled"
status-disabled-plain: "disabled"

usage-sell: "<red>Usage: /sell <hand|handall|all|inventory|gui>"
sell-unknown-mode: "unknown sell mode"
sell-all-total: "<gray>Sell-all total: <green><total>"
sell-all-summary-line: "<dark_gray>- <gray><line>"

license-header: "<gold>NexaShop License"
license-status-line: "<gray>Status: <white><status>"

network-header: "<gold>NexaShop Network"
# ...
# More options continue in the generated plugin YAML file.
# Open plugins/<plugin-folder>/messages.yml to review every setting.
# ...

GUI / Menus#

GUI cards describe the actual menus available in this product build.

Each card shows the configured menu title, inventory size, item count and detected actions when those values exist.

Layouts#

Shop layout definition used by the GUI service for category placement, product browsing and marketplace presentation.

  • Configured items: 1

Placeholders#

PlaceholderAPI examples available for this product.

Use the exact identifier shown here in scoreboards, chat formats and external display plugins.

Placeholder surface#

Identifier: nexashop. The expansion covers stock, player stock, buy/sell prices, total spent, bought/sold counts and top buyer/seller stats.

Usage notes#

  • Install PlaceholderAPI before using these values in scoreboards or chat formats.
  • Reload PlaceholderAPI expansions after plugin updates.
  • Keep placeholder identifiers lowercase exactly as shown unless the product uses a legacy mixed-case identifier.
PlaceholderAPI examples documented
PlaceholderExample outputDescription
%nexashop_stock_blocks:diamond%128Returns stock for a shop item key.
%nexashop_buyprice_blocks:diamond%250Returns the current buy price for a product.
%nexashop_sellprice_blocks:diamond%125Returns the current sell price for a product.
%nexashop_total_spent%18,420Returns the player's total spend value.
%nexashop_top_buyer%RitoMasssReturns the leading buyer tracked by shop stats.

Storage#

Storage docs explain YAML, SQLite, MySQL, MariaDB and backup expectations when supported.

Always back up before changing storage type or updating a production server.

Storage recommendation#

Use SQLite starter mode for testing. Use MySQL/MariaDB for production and Redis when cross-server stock/player-shop sync is enabled.

Backup checklist#

  • Stop the server before copying live flat files.
  • Export SQL databases before updates.
  • Keep plugin version and server version in backup notes.
  • Test migration on a copy first.

Integrations#

Each integration explains purpose, required/optional status, setup steps and troubleshooting.

Soft hooks load after the dependency is available through Bukkit's plugin manager.
Vault Optional hook

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.
PlaceholderAPI Optional hook

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.
CoinsEngine Optional hook

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.
ItemsAdder Optional hook

Purpose: Provides custom item, glyph or resource-pack integration.

Troubleshooting: If visuals are missing, check asset ids, resource-pack generation and provider reload order.

  1. Install the visual/resource plugin and load its pack or asset registry.
  2. Use valid item, glyph or hologram ids from that plugin.
  3. Reload the visual provider first, then reload this product.
  4. Open the GUI or display feature and check missing material/glyph warnings.
Oraxen Optional hook

Purpose: Provides custom item, glyph or resource-pack integration.

Troubleshooting: If visuals are missing, check asset ids, resource-pack generation and provider reload order.

  1. Install the visual/resource plugin and load its pack or asset registry.
  2. Use valid item, glyph or hologram ids from that plugin.
  3. Reload the visual provider first, then reload this product.
  4. Open the GUI or display feature and check missing material/glyph warnings.
Nexo Optional hook

Purpose: Provides custom item, glyph or resource-pack integration.

Troubleshooting: If visuals are missing, check asset ids, resource-pack generation and provider reload order.

  1. Install the visual/resource plugin and load its pack or asset registry.
  2. Use valid item, glyph or hologram ids from that plugin.
  3. Reload the visual provider first, then reload this product.
  4. Open the GUI or display feature and check missing material/glyph warnings.
WorldGuard Optional hook

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.
DiscordSRV Optional hook

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.
Citizens Optional hook

Purpose: Provides NPC entities used by bot or combat punishment workflows.

Troubleshooting: If NPCs or bots fail, check Citizens startup errors, skin fetch warnings, disabled worlds and pathfinder restrictions.

  1. Install Citizens before starting the server.
  2. Confirm Citizens loads without NPC registry errors.
  3. Enable the feature that uses NPCs, bots, corpses or combat entities.
  4. Spawn or trigger one test entity and check console for skin, pathfinder or trait errors.

Quick Start#

Create one shop from currency setup to a verified player transaction.

Use a test currency/account and never validate pricing with live balances first.
Verify currencyConfirm the currency in currencies.yml and make sure its economy provider is available.
Create the shopRun /shop editor create <shop> <currency> [title], then add a held item with /shop editor addhand <shop> <id> <buy> <sell>.
Test the transactionOpen /shop as a normal player and verify buy, sell, amount selector, insufficient balance and transaction history.

Player Buy & Sell Setup#

Make prices, limits, stock and failed transactions understandable to players.

Item lore must show the same price and availability that the transaction validator uses.

Buy flow#

  1. Open /shop or a category.
  2. Inspect buy price, stock, limits and availability window.
  3. Choose an amount and confirm the total.
  4. Reconnect and verify item delivery after a successful purchase.

Sell flow#

  1. Open /shop sellgui when bulk selling is enabled.
  2. Verify sell price and accepted materials.
  3. Test invalid item, amount limit and economy failure.
  4. Check history after a cancelled or failed transaction.

Preset, Import & Stock Setup#

Use editor, preset and import workflows without overwriting live pricing accidentally.

Run migrations as dry-runs, review the result and only then apply stock or price changes.
Preset workflow starter catalog
  1. Install a preset with /shop preset install survival on staging.
  2. Review categories, item ids, currencies and prices.
  3. Open the generated shop as a non-op and test one buy/sell item.
  4. Copy only approved entries to the production catalog.
Import and stock workflow migration
  1. Run import/dry-run commands against a backup.
  2. Map legacy material, price, category and stock fields.
  3. Apply the import, then verify stock decrement, restock and limits.

Production Rollout#

Keep catalog, currency and stock consistent during updates.

Back up shops, currencies and transaction data before changing ids or price semantics.

Go-live#

  • Separate editor, stock and admin permissions.
  • Use explicit transaction confirmation and audit history.
  • Test full inventory, disconnect and provider failure.
  • Monitor stock and transaction logs after launch.

Baseline#

transactions: require-confirmation: true write-history: true rollback-on-delivery-failure: true stock: prevent-negative: true

Operational Reference#

Use NexaShop as a catalog pipeline: currency → shop/category → item → transaction → stock/log.

Use presets and dry-runs for migration. Never edit live stock or pricing while testing with real player balances.

Admin: create a shop#

  1. Define or verify the currency in currencies.yml.
  2. Run /shop editor create <shop> <currency> [title].
  3. Add a held item with /shop editor addhand <shop> <id> <buy> <sell>.
  4. Set material/type, limits, stock and availability window from the editor.
  5. Open the shop as a normal player and test buy, sell, custom amount and insufficient balance.

Player: buy and sell#

  1. Open /shop or /shop <category>.
  2. Inspect item lore for buy/sell price, stock and limit state.
  3. Use the amount selector or /shop amount ... for a controlled quantity.
  4. Use /shop sellgui for bulk selling if enabled.
  5. Check transaction history after a cancelled or failed transaction.

Preset/import workflow#

/shop preset install survival
/shop layout install compact
/shop import shopguiplus --dry-run
/shop import report

Review warnings, materials, currencies and price conversion before running the real import.

Stock and pricing#

Set finite stock, refill/reset intervals and dynamic pricing together. A stock reset should not silently overwrite player-shop data; verify the selected shop/item scope first.

Common Setups#

Ready-to-follow scenarios reduce support tickets and make the product easier to configure.

Tune durations, limits, prices and permissions with the YAML files above.

Survival Server Shop Setup#

Use conservative defaults, SQLite or simple file storage, readable messages and relaxed limits for community servers.

Player Market Setup#

Define currencies first, then prices, limits, permissions, logs and rollback or recovery behavior.

Physical Shop Setup#

Define currencies first, then prices, limits, permissions, logs and rollback or recovery behavior.

Lifesteal Economy Setup#

Use stricter cooldowns, staff visibility, abuse protection and clear player feedback for high-conflict gameplay.

Network Shop Setup#

Use production SQL, unique server IDs, shared sync secrets and a controlled Redis or proxy transport.

Troubleshooting#

Start with console logs, config diffs, plugin version and reproduction steps.

The first error in console is usually more useful than repeated follow-up errors.
Shop GUI does not open issue

Check menu materials, category ids, command aliases and whether the economy/storage provider loaded before the GUI opened.

Items cannot be bought issue

Verify buy price, stock, currency provider, inventory space, permission requirements and any WorldGuard/shop region restriction.

Sell price is wrong issue

Check item matcher rules, NBT/custom item ids, price priority and whether the sell menu uses a different product key than the buy menu.

Stock does not sync issue

Confirm the selected storage/network backend is enabled on every server and that product ids are identical across configs.

Currency provider not detected issue

Check Vault/CoinsEngine startup order, currency id casing and whether the provider is enabled in hooks/config.

Player shops do not save issue

Verify database writes, owner UUID storage, shutdown save logs and whether the shop world is excluded.

FAQ#

Short answers for common buyer and staff questions.

Does NexaShop support Folia?#

Yes. The product descriptor or docs metadata marks this product as Folia-oriented; keep third-party hook thread-safety in mind during production testing.

Does it support old Minecraft versions?#

This page targets Paper/Folia with Java 21. Legacy 1.8 support is not part of this docs page.

Does it require MySQL?#

Use SQLite starter mode for testing. Use MySQL/MariaDB for production and Redis when cross-server stock/player-shop sync is enabled.

Can I disable modules?#

Yes. Use the Configuration section to manage the product modules and behavior exposed by YAML.

Can I edit all messages?#

Yes. Edit messages.yml and reload or restart according to the setting changed.

Does it support PlaceholderAPI?#

Yes. The documented identifier and examples are listed in the Placeholders section.

Changelog#

Product release notes grouped by version. Major public changes are written for buyers and server owners, not as raw commit logs.

v1.0.0#

Latest documented update: 2026-04-29.

Added
  • Added maven-wrapper.properties.
  • Added documentation/Features content.
  • Added mvnw.
  • Added mvnw.cmd.
  • Added build, dependency or obfuscation setup.
Changed
  • initialize NexaShop project structure with core economy, shop, and API modules
  • Updated .gitignore.
  • Updated build, dependency or obfuscation setup.
  • Updated NexaShop.java.

Support#

Send enough information to reproduce the issue.

Join Discorddiscord.gg/fANhQcyA7XInclude logs, config snippets and exact steps. Screenshots alone are not enough for config or database issues.

Before asking for support#

  • Test on the latest available plugin version.
  • Check server version and Java version.
  • Temporarily remove unrelated plugins when debugging conflicts.
  • Attach changed YAML files when config is involved.
Plugin: NexaShop
Plugin version:
Server version:
Java version:
Server software:
Database type:
Installed hooks:
Error log:
Steps to reproduce:
Expected behavior:
Screenshots/video: