Create a complete, production-ready Minecraft plugin called RELITE SMP CORE.
This must be ONE all-in-one plugin for a Minecraft SMP server.
The plugin should combine administration, moderation, player protection, permissions, kits, teleportation, item transfer, vanish, identity hiding, Creative detection, Creative alerts, enchantments and anti-X-Ray monitoring.
Use a clean modular architecture, persistent UUID-based data, SQLite storage and configurable settings.
Do NOT use pseudocode, fake implementations or placeholder methods.
==================================================
- TARGET PLATFORM
==================================================
Target a modern Minecraft server using Paper/Spigot API.
Clearly define the supported Minecraft version.
Provide:
- Complete source code
- plugin.yml
- config.yml
- SQLite database
- Maven/Gradle configuration
- Commands
- Permissions
- Tab completion
- GUI
- Installation instructions
- Build instructions
- Final JAR build configuration
==================================================
- FIRST JOIN WELCOME
When a player joins the server for the FIRST TIME, show:
"Welcome to Relite SMP!"
The message must be configurable.
Example:
&6Welcome to Relite SMP!
Important:
- Show this message only once.
- If the player leaves and joins again, do NOT show the first-join welcome message.
- Store first-join status using UUID.
- Server restart must not reset it.
Command:
/smp firstjoin <player> reset
Allow authorized admins to reset first-join status.
==================================================
- NEW PLAYER PROTECTION — EXACTLY 1 HOUR
Every completely new player receives 1 hour of protection.
Duration:
3600 seconds.
DO NOT make the default protection 24 hours.
During this 1-hour period:
- Other players cannot damage the new player.
- New player cannot damage other players.
- Prevent PvP damage.
- Prevent normal player attacks.
- Protection survives relog.
- Protection survives server restart.
- Relogging must NOT restart the 1-hour timer.
Show:
"New Player Protection: 59m 32s"
Use an action bar.
When the 1 hour expires:
"Your New Player Protection has expired."
Commands:
/newprotect <player> on /newprotect <player> off /newprotect <player> time
Permissions:
smp.newprotect smp.newprotect.bypass
Admins can manually enable or disable protection.
==================================================
- HIDE NAME / IDENTITY
Create an identity-hiding system.
Commands:
/hide <player> /unhide <player> /hideall /unhideall
When hidden:
- Hide nametag.
- Hide name from normal tab list.
- Hide identity from normal players.
- Normal players should not be able to identify the hidden player through normal player-list features.
- Authorized admins can see hidden players.
Permissions:
smp.hide smp.hide.bypass
==================================================
- VANISH
Commands:
/vanish /vanish <player> /vanish on /vanish off
When vanished:
- Player becomes invisible to normal players.
- Remove them from normal tab list.
- Prevent normal player interaction.
- Authorized staff can see vanished players.
Permissions:
smp.vanish smp.vanish.see
Optional action bar:
"VANISH: ON"
==================================================
- INDIVIDUAL KEEP INVENTORY
Keep Inventory must NOT be only a global server setting.
Allow the admin to enable it for individual players.
Commands:
/keepinv <player> on /keepinv <player> off /keepinv <player> toggle /keepinv list
Example:
/keepinv Sujay on
Only Sujay receives Keep Inventory.
Other players continue using normal death rules.
Store the setting permanently by UUID.
Permissions:
smp.keepinv smp.keepinv.others
==================================================
- KIT SYSTEM
Create a complete kit system.
Commands:
/kit /kit list /kit <kitname> /kit give <player> <kitname> /kit create <kitname> /kit delete <kitname> /kit edit <kitname>
Kits can contain:
- Weapons
- Armor
- Tools
- Food
- Potions
- Enchanted items
- Custom names
- Custom lore
- Custom enchantments
Example:
/kit give Sujay starter
Support configurable cooldowns.
Permissions:
smp.kit.use smp.kit.create smp.kit.give smp.kit.admin
==================================================
- INDIVIDUAL PERMISSION SYSTEM
Create a permission system where an admin can give a specific permission to a specific player.
Commands:
/smpperm <player> add <permission> /smpperm <player> remove <permission> /smpperm <player> list
Example:
/smpperm Sujay add smp.vanish
IMPORTANT:
Giving a permission must NOT give OP.
A player receiving:
smp.vanish
must only receive the vanish ability.
Support groups:
Owner Admin Moderator Helper Player
Commands:
/smpgroup <player> <group> /smpgroup list
Permissions:
smp.permission.admin smp.group.admin
==================================================
- OP-SAFE PERMISSIONS
OP players can have full administrative permissions unless disabled in config.
Non-OP players can receive individual permissions.
Never allow normal players to:
- Give themselves OP
- Give themselves permissions
- Escalate their own permissions
All administrative commands must check permissions.
==================================================
- ADVANCED ENCHANTMENTS
Allow authorized admins to apply high-level enchantments.
Command:
/enchant <player> <enchantment> <level>
Examples:
/enchant Sujay sharpness 100 /enchant Sujay protection 50 /enchant Sujay efficiency 100 /enchant Sujay fortune 20
Allow configurable maximum levels.
Also add:
/givecustom <player> <item> <amount> <enchantment>:<level>
Example:
/givecustom Sujay diamond_sword 1 sharpness:100
Multiple enchantments:
sharpness:100,fire_aspect:20,looting:50
Support:
- Custom name
- Lore
- Enchantments
- Item amount
- Supported item attributes
==================================================
- CREATIVE NAMETAG MARK
When a player enters Creative mode, display the status directly beside their nametag.
Example:
Sujay [CREATIVE]
The mark must be visible to normal players.
When they leave Creative:
Sujay
The current Creative mark disappears immediately.
Requirements:
- Update immediately.
- Work for admins.
- Work for normal players.
- Players joining later see the correct status.
- Work after relog.
- Work after server restart.
Use a proper scoreboard/team/name-tag implementation.
Config:
creative_mark: enabled: true current_format: "&c[CREATIVE]"
==================================================
- CREATIVE HISTORY
Remember if a player has recently used Creative.
Currently Creative:
Sujay [CREATIVE]
After leaving Creative:
Sujay [CREATIVE USED]
The history mark remains for exactly 24 hours after the last Creative use.
After 24 hours:
Sujay
If Creative is used again, restart the 24-hour timer.
Commands:
/creativehistory <player> /creativehistory reset <player> /creativehistory info <player>
Store timestamps permanently.
==================================================
- CREATIVE ALERT
Whenever ANY player enters Creative mode, immediately:
- Send a chat alert.
- Play a Dragon sound.
- Show Creative mark beside nametag.
Default chat:
"⚠ ALERT: Sujay has entered Creative Mode!"
If the player is an admin:
"⚠ ADMIN ALERT: Sujay is now in Creative Mode!"
The alert must also happen when an admin uses Creative.
==================================================
- CREATIVE DRAGON SOUND
When a player enters Creative, play:
ENTITY_ENDER_DRAGON_GROWL
Allow configuration:
creative_alert: enabled: true
sound: enabled: true sound: "ENTITY_ENDER_DRAGON_GROWL" volume: 1.0 pitch: 1.0
The alert must trigger each time the player actually changes into Creative.
Do NOT trigger the sound every server tick.
==================================================
- CREATIVE AUDIT LOG
Log:
[Relite SMP] PlayerName entered Creative mode.
and:
[Relite SMP] PlayerName left Creative mode.
Store:
- UUID
- Player name
- Start time
- End time
- Duration
Authorized admins can view the history.
==================================================
- TPA SYSTEM
Every normal player can receive the TPA permission if configured.
Permission:
smp.tpa
Command:
/tpa <player>
Example:
/tpa Sujay
The target MUST ACCEPT the request.
Never automatically teleport without acceptance.
Target receives:
"PlayerName wants to teleport to you."
Buttons:
[ACCEPT] [DENY]
Commands:
/tpaccept /tpdeny /tpacancel
==================================================
- TPA REQUEST EXPIRATION
Default request expiration:
60 seconds.
After 60 seconds:
"Teleport request has expired."
Config:
teleport: enabled: true require_accept: true request_expiration: 60 delay: 0
Cancel the request if either player disconnects.
==================================================
- TPA TAB COMPLETION
For:
/tpa <TAB>
Show eligible online players.
Do not expose hidden/vanished players unless the sender has the required bypass permission.
==================================================
- ITEM SEND SYSTEM
Create a system allowing an authorized player/admin to send an item from their own inventory to another player.
The sender should be able to open a GUI and select exactly which item they want to send.
Command:
/smp senditem <player>
Example:
/smp senditem Sujay
Open an inventory GUI showing the sender's available items.
The sender clicks an item.
Then show confirmation:
"Send this item to Sujay?"
Buttons:
[CONFIRM] [CANCEL]
After confirmation:
- Remove the selected item from the sender's inventory.
- Send the selected item to the target player.
- Preserve the item's exact properties.
Preserve:
- Item type
- Amount
- Enchantments
- Custom name
- Lore
- Durability/damage
- Potion properties
- Item metadata
- Custom model data where supported
- Other supported item components
Message to sender:
"You sent Diamond Sword x1 to Sujay."
Message to receiver:
"You received Diamond Sword x1 from AdminName."
==================================================
- ITEM SEND FROM ANYWHERE
The item-send system should work regardless of the sender's physical location.
The sender does NOT need to be near the target player.
Example:
Admin is at Spawn.
Sujay is at a completely different location.
Admin can use:
/smp senditem Sujay
Select an item.
Confirm.
Sujay receives it.
No distance restriction.
The target player must be online unless offline delivery is enabled in config.
==================================================
- OFFLINE ITEM DELIVERY
Optionally support offline item delivery.
If enabled:
/smp senditem Sujay
can send an item to a player who is offline.
Store the item safely in the database.
When Sujay joins:
"You received an item from AdminName."
Do not lose items if the server restarts.
Config:
item_send: enabled: true allow_offline: false require_confirmation: true
==================================================
- ITEM SEND PERMISSIONS
Permissions:
smp.itemsend smp.itemsend.others smp.itemsend.offline
Normal players should only receive the ability if explicitly granted.
Giving item-send permission must NOT give OP.
==================================================
- X-RAY MONITORING
Create server-side X-Ray monitoring.
Monitor suspicious behavior such as:
- Unusually high valuable-ore discovery.
- Suspicious direct paths toward ores.
- Repeated suspicious mining patterns.
- Configurable statistical thresholds.
Do NOT automatically ban based on one detection.
Use a suspicion score.
Example:
X-Ray Suspicion: 75%
When threshold is reached:
"[Relite SMP] Possible X-Ray activity detected: PlayerName"
Send alert to authorized staff.
Permissions:
smp.xray.alert smp.xray.admin
==================================================
- X-RAY MONITOR MODE
Commands:
/xraymonitor <player> on /xraymonitor <player> off /xraymonitor <player> info
Track suspicious activity while monitoring is active.
==================================================
- X-RAY PUNISHMENT
Do NOT automatically punish solely because of statistical suspicion.
Admin must confirm the case.
Command:
/xraypunish <player>
Configurable actions:
- Warning
- Temporary mining restriction
- Monitoring
- Temporary punishment
- Custom command
==================================================
- ADMIN GUI
Create:
/smpadmin
Main sections:
PLAYER MANAGEMENT
- Hide
- Unhide
- Vanish
- New Player Protection
- Keep Inventory
- Give Kit
- Permissions
- Groups
- Creative History
- X-Ray Monitoring
- Item Send
- Player Information
SERVER MONITORING
- Current Creative Players
- Recent Creative Users
- X-Ray Monitoring
- Suspicious Activity
- Active New Player Protection
Use player heads.
Selecting a player opens their management menu.
==================================================
- PLAYER INFORMATION
Command:
/smp player <player>
Show authorized staff:
- Name
- UUID
- Online status
- Group
- Permissions
- Hide status
- Vanish status
- Keep Inventory
- New Player Protection
- Creative status
- Creative history
- X-Ray monitoring
- Kit information
==================================================
- ADMIN LOGGING
Log important actions.
Examples:
[Relite SMP] Admin gave smp.vanish permission to Sujay.
[Relite SMP] Admin enabled Keep Inventory for Sujay.
[Relite SMP] Admin gave Starter Kit to Sujay.
[Relite SMP] Admin sent Diamond Sword to Sujay.
[Relite SMP] Sujay entered Creative mode.
==================================================
- DATABASE
Use SQLite by default.
Store using UUID:
- First join
- First join timestamp
- New Player Protection expiration
- Hide status
- Vanish status
- Keep Inventory
- Permissions
- Groups
- Kit cooldowns
- Creative status
- Last Creative timestamp
- Creative history
- X-Ray monitoring
- X-Ray statistics
- Pending item deliveries
- Relevant admin logs
Data must survive:
- Relog
- Server restart
- Plugin reload
==================================================
- CONFIGURATION
Create a clean config.yml.
Example:
welcome: enabled: true first_join_only: true message: "&6Welcome to Relite SMP!"
new_player_protection: enabled: true duration: 3600 prevent_pvp: true show_actionbar: true
creative_mark: enabled: true current_format: "&c[CREATIVE]" history_format: "&e[CREATIVE USED]" history_duration: 86400
creative_alert: enabled: true
chat: enabled: true normal_message: "&c⚠ ALERT: &f%player% &chas entered Creative Mode!" admin_message: "&c⚠ ADMIN ALERT: &f%player% &cis now in Creative Mode!"
sound: enabled: true sound: "ENTITY_ENDER_DRAGON_GROWL" volume: 1.0 pitch: 1.0
teleport: enabled: true require_accept: true request_expiration: 60 delay: 0
item_send: enabled: true allow_offline: false require_confirmation: true
xray: enabled: true automatic_punishment: false alert_threshold: 75 monitoring_enabled: true
==================================================
- MAIN COMMANDS
Implement:
/smp /smpadmin /smp player <player> /smp firstjoin <player> reset
/hide /unhide /hideall /unhideall
/vanish
/keepinv
/kit
/smpperm
/smpgroup
/enchant
/givecustom
/newprotect
/creativehistory
/tpa /tpaccept /tpdeny /tpacancel
/smp senditem
/xraymonitor /xraypunish
Add complete tab completion to all commands.
==================================================
- PERMISSIONS
Create permissions including:
smp.hide smp.hide.bypass
smp.vanish smp.vanish.see
smp.keepinv smp.keepinv.others
smp.kit.use smp.kit.create smp.kit.give smp.kit.admin
smp.permission.admin smp.group.admin
smp.enchant smp.givecustom
smp.newprotect smp.newprotect.bypass
smp.tpa smp.tpaccept smp.tpdeny smp.tpa.bypass
smp.itemsend smp.itemsend.others smp.itemsend.offline
smp.xray.alert smp.xray.admin
All permissions must be individually assignable.
==================================================
- PERFORMANCE
Optimize the plugin.
Avoid:
- Heavy repeating loops
- Unnecessary database calls
- Main-thread database operations
- Excessive entity creation
- Constant Creative checks every tick
Use event-based detection wherever possible.
Use asynchronous database operations where safe.
Cache player data appropriately.
==================================================
- SECURITY
Every administrative command must check permissions.
Never allow:
- Self-OP
- Permission escalation
- Unauthorized item creation
- Unauthorized Creative access
- Unauthorized player information access
Item-send must remove the actual selected item from the sender before delivery.
Use secure transaction logic so items cannot be duplicated.
==================================================
- MODULAR PROJECT STRUCTURE
Organize the project into classes/modules such as:
ReliteSMPPlugin CommandManager PermissionManager PlayerDataManager DatabaseManager ConfigManager MessageManager
FirstJoinManager NewPlayerProtectionManager
HideManager VanishManager KeepInventoryManager
KitManager EnchantmentManager ItemSendManager
CreativeManager CreativeHistoryManager CreativeAlertManager
TeleportRequestManager
XRayManager AuditLogManager
AdminGUIManager TabCompletionManager
Do not put the entire plugin into one giant class.
==================================================
- FINAL RESULT
The final plugin must be:
RELITE SMP CORE
An all-in-one SMP plugin containing:
✓ One-time "Welcome to Relite SMP!" message ✓ Exactly 1-hour new-player protection ✓ Hide Name ✓ Hide Identity ✓ Hide Nametag ✓ Vanish ✓ Individual Keep Inventory ✓ Kits ✓ Individual Permissions ✓ Permission Groups ✓ OP-safe permissions ✓ High-level Enchantments ✓ Custom Items ✓ Creative Nametag Mark ✓ Creative History for 24 hours ✓ Creative Audit Log ✓ Creative Chat Alert ✓ Dragon Sound Alert ✓ Admin Creative Alert ✓ TPA Request System ✓ TPA Accept/Deny ✓ TPA Expiration ✓ TPA Delay ✓ Item Send GUI ✓ Select item from inventory ✓ Send item to any online player from anywhere ✓ Optional offline item delivery ✓ X-Ray Monitoring ✓ X-Ray Suspicion Alerts ✓ Configurable X-Ray Punishment ✓ Admin GUI ✓ Player Management ✓ SQLite Storage ✓ Configurable Messages ✓ Permissions ✓ Tab Completion ✓ Admin Logs ✓ Persistent UUID-based data
All features must work together.
The plugin must compile successfully into a working ".jar".
Provide the complete project files and exact build instructions.