1. Price Budget
- $200 USD for plugin development
- Timeline: 1-2 weeks
2. Developer Requirements
- Knowledge and practical experience with Redis Database
- Experience developing cross-server plugins (specifically Duel/Arena type systems)
- Java programming experience (minimum 2+ years)
3. Tech Stack
- Database: Redis for data persistence and cross-server communication
- Server Software: Purpur 1.21.1 (Paper fork)
- Hosting: OVH server infrastructure
- Runtime: Java 21
4. Server Architecture
- Main Server: Open-world map with all biomes
- Second/Third Server: Arena instances for PvE combat (identical purpose, load distribution)
5. Server Gameplay Flow
- Main "Map" server contains 10 biomes with player damage disabled
- When a player clicks on a mob, a battle instance is created
- Player is teleported to a battle server with an appropriate arena
- Upon victory, player is teleported back to their last location on the Map server
- Upon defeat, player is teleported to the Map server's spawn point
6.1 Arena System Requirements
- Void world as the arena environment
- Dynamic arena creation from schematics based on mob type
- Arena spacing of 8 chunks in any direction for isolation
- Each arena approximately 100x100 blocks
- Performance optimization for arena creation (whether pre-generated or on-demand)
- Proper arena state management (creation, usage, recycling)
6.2 Battle System Requirements
- Battle initiation via left-click on mob with sword
- Confirmation GUI before battle starts
- Battle creation function: createBattle(players, mobs)
- Arena allocation: getAvailableArena() or createArena()
- Transfer function without BungeeCord dependency (debatable)
- Redis-based player state checking on arena server join
- Designated spawn points for players and mobs within arenas
- Battle conclusion handling: endBattle() to save stats, update battle/arena states
- State management for arenas (PENDING, AVAILABLE, IN_USE, RETURNING, INACTIVE)
- Comprehensive battle state tracking
6.3 Command System
- Battle management:
- /battle start <player> <mobtype>
- /battle end <id>
- /battle status <id>
- /battle list
- /battle info <id>
- Arena management:
- /arena create <name> <type>
- /arena delete <name>
- /arena paste <name> <location>
- /arena list
- /arena changestate <name> <state>
- /arena tp <name>
- Admin commands:
- /battlesystem reload
- /battlesystem debug
- /battlesystem stats
7. Additional Requirements
- Configurable options via config files for:
- Redis configuration:
- Host, port, password
- Database name/index
- Connection pool settings
- Key prefixes
- Server network settings:
- Map server IP/hostname and port
- Arena servers IPs/hostnames and ports
- Server identification keys
- Arena settings:
- Distance between arenas (in chunks)
- Arena world name
- Schematic folder path
- Default arena type mappings
- Arena creation mode (pre-generated vs on-demand)
- Battle settings:
- Battle duration limits
- Cooldown between battles
- Mob difficulty scaling
- Battle rewards configuration
- Player data saving frequency
- Performance options:
- Max concurrent battles per server
- Arena recycling thresholds
- Arena cleanup timing
- Redis configuration:
- Optimization for high player counts and concurrent battles
- Clean, well-structured, and documented code
- Full source code access for future modifications
All this information represents my current vision for the plugin, but I'm open to any suggestions for better implementation approaches, command structures, or feature modifications that would enhance the final product.
WARNING: I have Java experience as beginner-intermediate so I know that Redis cross-server can be tricky to implement. Please do not accept this job if you've never used Redis and never developed cross-server arena/duel type plugins. Serious developers only.
This is intended as a building block for my project, and I'm looking for ongoing collaboration. If we work well together on this plugin, I'd be interested in commissioning additional plugins in the future.
This post was created with AI assistance.
- Type
- Requesting
- Provided by
- Individual
