DDONSUP / ALL IN ONE

DOCUMENTATION / 0.5 DEVELOPMENT

Installation

These instructions describe the packaged 0.5.1-SNAPSHOT development preview. Read the development compatibility and upgrade notes before evaluating it.

Wiki home

Requirements

Component Tested target
Server Spigot, Paper, Purpur or Folia; see exact builds in the compatibility guide
Java Java 21 for 1.21.11; Java 25 for qualified 26.2 builds
Player client Java Edition 1.21.11
Required plugins None
Storage Local YAML files and normal Minecraft world/player files

Read server compatibility for Folia differences, Spigot inventory menus, qualified server builds and the translated-client scope of 26.2 tests. Bedrock/Geyser, proxies, Forge/Fabric and unlisted forks remain unqualified.

First installation

  1. Stop the server. Back up its worlds, player data and plugins.
  2. Place DonsupAllInOne-0.5.1-SNAPSHOT.jar in plugins/. Keep only one Donsup JAR.
  3. Start the server and look for DonsupAllInOne enabled. in the log.
  4. Join and run /donsup. Open /settings to see the six settings categories, native on Paper/Folia and inventory-based on Spigot.
  5. With donsup.admin, run /creator to inspect the configuration tools. Set your spawn with /setspawn.
  6. Configure prices and rewards for your server before inviting players. Defaults are a starting point, not a balanced production economy.

Use /shop for player-market Quick Buy and /servershop for the fixed-price server shop. Both are included and serve different purposes.

Updating

Stop the server, make a complete backup, replace the JAR and start the server again. Do not use Bukkit /reload or hot-loading tools. Configuration edits can be applied with /donsup reload; stored account files should only be edited while the server is stopped.

Version 0.2 reads the older plain-material orders. Do not downgrade to 0.1 while exact-item orders exist: the old version cannot preserve their matching rules.

Local testing

Create a separate disposable server for evaluation and follow the source archive's integration-tests/README.md. Never point the automated fixture at customer/player data. It deliberately uses offline mode bound only to loopback so that test clients can connect.

For a public server, use normal authenticated server configuration and your host's address. No public demo server is supplied by this package.