ShyamDuels: Build a Modern Minecraft Practice, FFA and Duels Server
Running a competitive Minecraft PvP server involves much more than teleporting two players into an arena. A complete practice experience must coordinate matchmaking, kits, arena availability, rounds, statistics, parties, spectators, rematches and safe player restoration.
ShyamDuels brings those systems together as a standalone practice core for modern Paper and Purpur servers. It is designed for owners building a dedicated practice network, adding structured PvP to a community or creating custom features through a documented API.
What is a Minecraft practice core?
A practice core manages the complete lifecycle of competitive PvP. It decides who can fight, selects an available arena, applies the correct kit, starts the countdown, tracks rounds and deaths, calculates results and safely returns every player when the match ends.
That lifecycle becomes complicated when a server supports multiple queues, team modes, spectators, editable kits and persistent rankings. A unified core gives those features one shared source of truth instead of forcing owners to connect unrelated duel, queue, party and statistics plugins.
ShyamDuels follows that unified approach. Duels, queues, arenas, kits, FFA, parties, tournaments and statistics operate as parts of the same platform.
ShyamDuels at a glance
- Standalone Minecraft practice and duels core
- Designed for modern Paper and Purpur servers
- Direct challenges plus ranked and unranked queues
- ELO, statistics and leaderboard foundations
- Multi-round duel formats
- Multiple FFA arenas and rekit flows
- Party FFA, party split and party-versus-party modes
- Tournament registration, brackets and rounds
- Configurable kits, player layouts and kit sharing
- Spectating and post-match rematches
- Friends, player preferences and country profiles
- Placeholders plus a documented developer API
One connected competitive flow
The value of a practice core is not the number of isolated commands it contains. The value is how reliably its systems cooperate.
Choose how to compete
Players can challenge someone directly or enter a queue. Ranked queues connect matchmaking to ELO progression, while unranked play gives new or casual players a lower-pressure option.
Assign the match
ShyamDuels associates players with a kit, arena and format. Central arena availability prevents conflicting assignments, while multi-round formats support competitive best-of series instead of limiting every duel to sudden death.
Run and conclude the match
Countdowns, combat state, deaths, rounds and victory conditions belong to one lifecycle. Results can feed ELO, leaderboards, placeholders, rewards or custom integrations. Spectating and rematches reduce the friction between one fight and the next.
Duels, ranked queues and multi-round PvP
Direct challenges place two players into a controlled match with an agreed kit and round format.
Ranked and unranked queues help players find opponents automatically. Ranked results connect to ELO; unranked queues support experimentation and casual practice.
Multi-round matches provide longer competitive formats. Round start and end events can drive scoreboards, broadcasts, rewards and custom logic.
Rematches and spectating keep players engaged and let communities, staff or tournament viewers follow active competition.
FFA inside the same PvP ecosystem
FFA should not feel like a disconnected minigame installed beside the practice server. ShyamDuels includes FFA as part of the same core platform.
Owners can configure multiple FFA arenas for repeatable practice outside formal matchmaking. Players can warm up in FFA, join a queue, duel friends and return to FFA without leaving the server's central PvP loop.
FFA services are exposed through the API, allowing custom menus, portals, NPCs or network tools to integrate through supported interfaces.
Parties and team battles
ShyamDuels supports more than 1v1 competition:
- Party FFA: party members compete individually until one winner remains.
- Party split: one party is divided into opposing teams.
- Party versus party: two organized parties challenge each other.
These modes use the same match foundation as individual duels. Dedicated start and end events support custom scoreboards, rewards and statistics.
Tournament structure
Tournaments turn occasional PvP into scheduled community events. ShyamDuels documents a lifecycle covering creation, registration, bracket generation, rounds, match completion, eliminations and champion selection.
Tournament events provide extension points for announcements, prizes, Discord integrations, custom menus and seasonal competitions.
Kits, layouts and progression
A practice server needs consistent rules without forcing every player to use an uncomfortable inventory layout.
ShyamDuels separates kit definitions from player-specific layouts. Staff define the items and rules while players arrange supported layouts for combat. Kit sharing helps teams and communities distribute preferred configurations.
Ranked results connect to ELO and player statistics, creating a foundation for ladders and leaderboards. Placeholders and API services can present information in scoreboards, tab lists, menus, holograms or web integrations.
Player-facing quality of life
- Player settings and preferences
- Friends management
- Spectator access and rematch offers
- Scoreboard, tab and nametag services
- Placeholder resolution
- Country selection and optional GeoIP-based profiles
- Configurable messages and interfaces
Each server can choose the systems that match its identity. ShyamDuels provides a connected foundation without forcing one visual style.
A documented API for custom development
ShyamDuels is also a platform for server developers. Focused services cover players, duels, arenas, kits, kit sharing, queues, parties, FFA, spectators, rematches, statistics, settings, friends, placeholders, tournaments and presentation systems.
Custom Bukkit events cover duel countdowns, duel starts and endings, fight deaths, virtual deaths, round transitions, party matches, tournaments and country changes.
This lets addons build custom rewards, cosmetics, analytics, dashboards, Discord announcements or private gameplay rules against documented contracts instead of patching the core.
ShyamDuels Core or the complete setup?
Shyam Studio offers two products for different buyers.
Choose ShyamDuels Core when:
- You already operate a Paper or Purpur server.
- You want to design your own arenas, menus and identity.
- You need a standalone practice plugin.
- You plan to build API integrations.
- You want control over the surrounding server.
View ShyamDuels Core on BuiltByBit
Choose the complete setup when:
- You want a configured Practice, FFA and Duels server.
- You prefer prebuilt kits, arenas, menus, tab and scoreboard configuration.
- You want to launch faster.
- You do not want a separate premium practice-core dependency.
View the complete ShyamDuels setup on BuiltByBit
The core is the software foundation; the setup is the configured server experience built around it.
Compatibility and safe deployment
The current listing supports Paper and Purpur across modern Minecraft releases beginning with the 1.21 generation. Confirm exact versions on the live listing before upgrading production.
- Back up server and plugin data.
- Confirm the target Paper or Purpur version.
- Install current required dependencies.
- Configure kits and arenas in staging.
- Test completion, disconnects, restarts and restoration.
- Enable queues, ELO, FFA, parties and tournaments in stages.
Try ShyamDuels
Public test server:
139.99.125.156:25607Use the test server to evaluate menus, queues, kits, arenas and match flow from a player's perspective.
Explore ShyamDuels Core
Get support and release information
Build a PvP loop players return to
A successful practice server needs a reliable loop: join, choose a mode, find an opponent, fight under clear rules, receive a result and return for the next match.
ShyamDuels provides that loop through one connected core while owners retain control over branding, configuration and custom development.
Start with ShyamDuels Core
ShyamDuels documentation hub
Quick navigation: installation | commands | configuration | arenas | kits | troubleshooting | Core vs SetupInstallation checklist
- Install Java 21 and a supported Paper 1.21.x build on staging.
- Back up the server and database before replacing any existing PvP system.
- Install the required FastAsyncWorldEdit, PacketEvents, LuckPerms and PlaceholderAPI builds.
- Add ShyamDuels, boot once, and resolve console warnings before configuration.
- Configure storage, spawn behavior and permissions before importing player data.
- Create one kit and one arena, then complete an end-to-end duel before expanding.
Command map
| Area | Primary commands | Purpose |
|---|---|---|
| Duels | /duel, /queue, /spectate | Challenges, matchmaking and spectating. |
| FFA | /ffa, /spawn, /leavefight | Enter or leave persistent combat modes safely. |
| Kits | /kiteditor, /kitcreator, /customkits, /kit | Create, edit and select kit content. |
| Administration | /arena, /shyamduels | Manage arenas and core administrative tasks. |
Use
/<command> help and the versioned documentation for exact subcommands and permission nodes. Do not grant wildcard administrative permissions to ordinary staff.Configuration map
Treat configuration as a deployment artifact. Keep a private copy under version control, document local changes and compare release notes before replacing files.
- Core and storage: server identity, SQLite or MySQL, save intervals and shutdown behavior.
- Matchmaking: queues, team sizes, party boundaries, ranked rules and ELO tiers.
- Gameplay: kits, rounds, win conditions, build permissions, projectiles and item behavior.
- Arenas: spawn points, bounds, cloning or reset strategy and mode eligibility.
- Presentation: menus, messages, scoreboards, tab data, titles and placeholders.
- Integrations: optional Nexo, FancyNpcs and SkinsRestorer features only when installed and required.
Safe arena workflow
Create and validate arenas on staging. Confirm both spawn positions, spectator boundaries, void handling, world borders and the reset mechanism. Run simultaneous match endings to expose race conditions or slow FAWE restores. Keep an untouched source copy of every arena.
Kits, queues and progression
Use consistent identifiers across kits, menus and queues. Test custom kit editing with a normal player's permissions, including full inventories and disconnects. For ranked play, verify that results are committed once and only once after wins, forfeits, timeouts and server restarts.
Data and upgrade safety
Stop the server cleanly before copying SQLite files. For MySQL, use a database-aware backup and verify that it can be restored. Before each ShyamDuels upgrade, read the changelog, clone production to staging, apply the update there, and test the complete launch matrix. Never treat an untested backup as a recovery plan.
Troubleshooting
Plugin does not enable: confirm Java 21, Paper 1.21.x, required dependencies and the first complete stack trace.
Commands are missing: test without operator status, review LuckPerms assignments and confirm that another plugin is not claiming the command.
Arena does not reset: verify FAWE compatibility, file permissions, source arena data and concurrent reset load.
Players keep the wrong inventory: reproduce on staging with join, queue, match, death, disconnect and reconnect steps. Include console output and exact versions in a support request.
Database data is delayed: check connection latency, credentials, pool limits and shutdown completion before changing gameplay settings.