Try to understand the things I told in this field and do the work.
📎
1 file
13,584 chars
📄
eternalcore.txt
txt
748 lines
▶
eternalcore.txt
txt
748 lines
You are a senior Minecraft Paper plugin developer.
Create a complete original Paper plugin called EternalCore for my Minecraft network EternalMC.
IMPORTANT:
Do not copy code from any server.
Make original code.
Do not use placeholders.
Do not leave TODOs.
Do not skip files.
Every class you reference must exist.
Every command must be registered.
Every config key used in code must exist.
Every phase must compile using Maven.
SERVER:
Paper 1.21.x
Java 21+
Current setup: one Paper server
Future setup: Velocity network
Lobby world name: world
Permissions: LuckPerms
Optional hooks: PlaceholderAPI, Citizens, Vault later
Database: SQLite now, MySQL support later
Theme: purple
Build tool: Maven
I use Termux on Android, so include pasteable shell scripts that create files and compile with mvn clean package.
PLUGIN NAME:
EternalCore
PACKAGE:
com.eternalmc.core
GOAL:
Make a configurable network-core plugin for EternalMC with Friends, Parties, Profiles, Credits, Tiers, XP/Levels, Guilds, Collectibles, Cosmetics framework, and Seasonal Pass.
Everything should be configurable through config.yml, messages.yml, INVENTORY GUI.yml, and admin commands where possible. All messages must be colorful, not plain white.
==================================================
PHASE SYSTEM
Generate the project in phases.
Phase 1:
Base plugin + Friends system
Phase 2:
Party system
Phase 3:
Profiles + Credits + Tiers
Phase 4:
XP + Levels
Phase 5:
Guilds
Phase 6:
Collectibles
Phase 7:
Cosmetics framework
Phase 8:
Seasonal Pass
Each phase must compile independently before generating the next phase.
==================================================
BASE PLUGIN
Generate:
pom.xml
plugin.yml
config.yml
messages.yml
INVENTORY GUI.yml
all Java source files
Core commands:
/ecore reload
/ecore help
Base systems:
Config manager
Message manager
INVENTORY GUI utility
Item utility
Database manager
Player data manager
LuckPerms hook
PlaceholderAPI hook if installed
Velocity-ready server tracking model
Store player data:
uuid
name
first_join
last_seen
playtime_seconds
current_server
current_gamemode
last_lobby_location
==================================================
HOTBAR LOBBY ITEMS
Only give lobby items in world named "world".
Default hotbar:
slot 0 = Friends
slot 1 = Party
slot 2 = Profile
slot 3 = Cosmetics
slot 4 = Guilds
slot 5 = Pass
slot 6 = Collectibles
All hotbar items configurable:
enabled
worlds
slot
material
custom-model-data
name
lore
glow
Clicking item opens its INVENTORY GUI.
==================================================
INVENTORY GUI STYLE
All GUIs must use a purple NetherGames-inspired style.
Use inventory GUIs for Java Paper.
All INVENTORY GUI titles, sizes, items, names, lore, filler items, sounds, and buttons must be configurable in INVENTORY GUI.yml.
Use purple stained glass panes or configurable filler items.
==================================================
FRIENDS SYSTEM - PHASE 1
Commands:
/friends
/friend
/f
Subcommands:
/friends add
/friends remove
/friends accept
/friends deny
/friends cancel
/friends list
/friends requests
/friends join
/friends toggle
/friends help
Hotbar:
Friends item in slot 0 by default.
Clicking it opens Friends INVENTORY GUI.
INVENTORY GUI:
Main Friends INVENTORY GUI:
- Add Friend
- Online Friends
- Offline Friends
- Friend Requests
- Friend Settings
- Close
Add Friend INVENTORY GUI:
- Shows online players who are not already friends
- Clicking sends request
- Also allow command input through /friends add
Requests INVENTORY GUI:
- Incoming requests
- Outgoing requests
- Accept button
- Deny button
- Cancel outgoing request button
Friend List INVENTORY GUI:
- Show online friends first
- Show offline friends separately
- Friend head item
- Lore shows status, server, gamemode, and actions
Friend limits:
Default players can have 10 friends only.
Limits must be configurable by LuckPerms group or permission.
Example:
default: 10
vip: 25
legend: 50
emerald: 100
eternal: 150
Also support permission-based limits:
eternalcore.friends.limit.25
eternalcore.friends.limit.50
eternalcore.friends.limit.100
Highest permission wins.
Friend request rules:
- Cannot friend yourself
- Cannot duplicate requests
- Cannot add existing friend
- Cannot exceed sender friend limit
- Cannot exceed receiver friend limit
- Request expires after configurable time
- Notify receiver when request arrives
- Notify sender when accepted/denied
- Notify friends when player joins/leaves if enabled
FRIEND JOIN SYSTEM:
This must be included.
Friends INVENTORY GUI must include a Join Friend button/action.
If the friend is online and in lobby:
- If same server setup: teleport player to friend's current lobby location if enabled.
- If future Velocity setup: connect player to friend’s current server.
- Message: "&dFriends &8» &aJoining &e%player%&a."
If the friend is online and in a game like BedWars, SkyWars, Duels, etc:
- Do NOT teleport into the match by default.
- Show message: "&dFriends &8» &e%player% &cis currently in game."
- INVENTORY GUI lore should show: "Status: In Game"
- Config option:
friends.join.allow-joining-games: false
If true in future, allow connecting to same game server but only if target game plugin allows spectators or party joining.
If the friend is offline:
- Message: "&dFriends &8» &c%player% is offline."
Server/gamemode tracking:
Track every player's:
current_server
current_gamemode
status
For current single-server mode:
current_server = "lobby"
current_gamemode = "lobby" when in world "world"
Future Velocity mode:
Prepare API methods:
setPlayerServer(UUID, String serverName)
setPlayerGamemode(UUID, String gamemode)
joinFriend(Player player, UUID friendUuid)
Do not require Velocity in Phase 1, but design code so Velocity can be added later.
Friend privacy settings:
- Allow friend requests: true/false
- Allow friends to join me: true/false
- Show online notifications: true/false
Database tables:
players
friends
friend_requests
friend_settings
player_status
Friend relationship must be UUID-based and bidirectional.
==================================================
PARTY SYSTEM - PHASE 2
Commands:
/party
/p
Subcommands:
create
invite
accept
deny
leave
kick
promote
transfer
disband
chat
list
warp
settings
INVENTORY GUI:
- Create Party
- Invite Players
- Party Members
- Party Settings
- Leave/Disband
Features:
- Party leader
- Party members
- Party invites
- Invite timeout
- Party chat
- Kick
- Promote
- Transfer
- Disband
- Party warp
- Party join game together
- Future Velocity support
When party leader joins BedWars/SkyWars/Duels:
- party members should follow if enabled
- if game is full, show message
- design API for game plugins
==================================================
PROFILE SYSTEM - PHASE 3
Commands:
/profile
/profile
Behavior:
- /profile opens own profile
- /profile opens that player's profile
- Right-clicking a player with Profile item opens their profile
Profile INVENTORY GUI shows:
name
rank
tier
level
xp
credits
guild
friends count
join date
playtime
current status
current gamemode
Stats shown:
BedWars wins
BedWars kills
BedWars final kills
BedWars beds broken
SkyWars wins
SkyWars kills
Duels wins
Duels kills
Stats are stored even if game plugins are not added yet.
Create API methods for other plugins to update stats.
==================================================
CREDITS SYSTEM - PHASE 3
Credits like NetherGames-style credits.
Commands:
/credits
/balance
/ecore credits add
/ecore credits remove
/ecore credits set
Credits sources:
games
admin commands
collectibles
pass rewards
events later
Config:
starting credits
currency name
currency symbol
format
==================================================
TIERS SYSTEM - PHASE 3
Credits unlock tiers.
Default tiers:
Bronze I-V
Silver I-V
Gold I-V
Diamond I-V
Emerald I-V
Master I-V
Eternal
Each tier configurable:
required credits
display name
chat format
rewards
permissions to run commands
Chat format:
[LP Rank] [Tier] Player
Example:
[Legend] [Gold III] KRIS
Everywhere possible:
chat
profile
INVENTORY GUI lore
scoreboard placeholders
==================================================
XP AND LEVELS - PHASE 4
XP separate from credits.
XP sources:
kill
final kill
bed break
win
playtime reward later
Default:
kill_xp: 10
final_kill_xp: 25
bed_break_xp: 50
win_xp: 100
Levels unlock:
chat colors
cosmetics
future rewards
Admin commands:
/ecore xp add
/ecore xp set
/ecore level set
Create API:
addXP(UUID, amount, reason)
addGameReward(UUID, kills, finalKills, bedsBroken, won)
==================================================
GUILDS - PHASE 5
Commands:
/guild
/g
Features:
create
invite
accept
deny
kick
promote
demote
leave
disband
chat
motd
info
list
Only Legend rank or any rank/permission I configure can create guilds.
Others can join guilds.
Use LuckPerms permission:
eternalcore.guild.create
Guild tags:
Show guild tag in chat and profile.
Example:
[ABC] [Legend] [Gold III] Player
Guild XP:
Guild levels up when members win games.
Guild XP sources configurable.
Guild unlocks:
more member slots
guild tag colors
guild cosmetics
guild upgrades
All configurable.
==================================================
COLLECTIBLES - PHASE 6
Lobby collectibles.
Admin commands:
/collectible create
/collectible delete
/collectible list
/collectible reward
/collectible tp
Each collectible stores:
world
x
y
z
display item/entity
reward
found message
Rewards configurable:
credits
xp
cosmetic unlocks
commands
Completion reward:
Reward for finding all collectibles.
Admin can edit rewards and locations.
No global Eternal level.
No titles.
No event menu.
No plots.
==================================================
COSMETICS FRAMEWORK - PHASE 7
Framework for adding cosmetics later.
Categories:
hats
particles
capes
trails
join effects
kill effects
gadgets
Cosmetics should be configurable without code changes.
Each cosmetic:
id
display name
permission
category
icon
description
unlock requirement
effect settings
Support:
equipping
unequipping
permission unlocks
pass rewards
level rewards
INVENTORY GUI:
Purple cosmetics menu.
If capes are impossible on normal Java Paper without resource pack/mods, create placeholder framework and document limitation.
==================================================
SEASONAL PASS - PHASE 8
Hotbar item opens pass INVENTORY GUI.
Pass system like Free Fire / BGMI style.
Tracks:
Free track
Premium track
I take payments externally and grant premium pass using command.
Commands:
/pass
/passadmin give
/passadmin remove
/passadmin season create
/passadmin season end
/passadmin season reset
/passadmin reward add
/passadmin reward remove
Admin can configure:
season name
duration
end date
rewards
free rewards
premium rewards
required XP/points per level
Rewards:
credits
xp
cosmetics
commands
Everything configurable.
==================================================
CHAT FORMAT
Format configurable.
Default:
%guild_tag% %luckperms_prefix% %tier% %player% &8» &f%message%
Supports:
LuckPerms rank
Tier
Guild tag
Unlocked chat colors
No white-only system messages.
==================================================
PLACEHOLDERS
If PlaceholderAPI installed, add placeholders:
%eternalcore_credits%
%eternalcore_tier%
%eternalcore_level%
%eternalcore_xp%
%eternalcore_guild%
%eternalcore_friends_count%
%eternalcore_playtime%
%eternalcore_status%
%eternalcore_gamemode%
==================================================
DATABASE TABLES
Create tables automatically:
players
friends
friend_requests
friend_settings
player_status
parties
party_members
profiles
credits
tiers
xp
levels
guilds
guild_members
guild_invites
collectibles
player_collectibles
cosmetics
player_cosmetics
season_passes
player_passes
stats
Use SQLite now.
Design DatabaseManager with interface so MySQL can be added later.
==================================================
ADMIN CONFIG COMMANDS
/ecore reload
/ecore save
/ecore debug
/ecore set friendlimit
/ecore set lobbyworld
/ecore set message
/ecore set INVENTORY GUI
/ecore credits add/remove/set
/ecore xp add/set
/ecore level set
/ecore tier set
/ecore guild
/ecore collectible
/ecore cosmetic
/ecore pass
All admin command messages colorful.
==================================================
TERMUX REQUIREMENTS
I use Termux on Android.
Generate a single pasteable shell script for each phase.
Each script should:
cd ~
create or update EternalCore folder
create folders
write files using cat << 'EOF'
run mvn clean package
Final jar should be:
target/EternalCore-.jar
Use Maven.
==================================================
OUTPUT REQUIREMENTS
Start with Phase 1 only:
Base plugin + complete Friends system including friend joining system.
Phase 1 must compile by itself.
After Phase 1, wait for me to test.
Then generate Phase 2 script that adds Parties without deleting existing code.
Do not generate all phases at once unless asked.
Do not leave incomplete files.
Do not cut off Java files.
If response limit is too small, split Phase 1 into Part A, Part B, Part C and clearly say where each part continues.
Final goal:
A complete EternalCore.jar with all systems.
Kodari can make mistakes. Review important code before using.
Files
No files in this session
Code