TierKits

TierKits: Higher Ranks Get Better Kits

A straightforward, permission-based kit system that rewards players as they rank up.



TierKits provides a clean, organized kit system where players unlock increasingly powerful kits as they progress through your server's ranks. From basic starter gear to legendary equipment, each tier provides clear progression for your players.




Key Features:

• Clean GUI Menu - Intuitive, glass-paned menu with clear indicators for available, locked, and cooldown kits
  
  
• Rank-Based Access - Control kit access through permission nodes, perfect for rank progression
  
  
• Tiered Structure - Organize kits in a hierarchy from basic to legendary
  
  
• Customizable Cooldowns - Set different cooldown times for each kit
  
  
• Visual Status Indicators - Players can easily see which kits they can claim with color-coding and symbols
  
  
• Item Preview - Shows players what's included in each kit before claiming
  
  
• Command Access - Claim kits directly via command or through the GUI

How It Works:

1. Players type /kit to open the menu
   
   
2. Available kits show with a green checkmark
   
   
3. Rank-locked kits display which rank is required
   
   
4. On-cooldown kits show remaining time
   
   
5. Players can claim kits with a simple click

Simple Setup:

1. Drop the plugin in your plugins folder
   
   
2. Configure kits in the config.yml file
   
   
3. Set up permissions with your permissions plugin
   
   
4. Ready to use!

Perfect for survival, faction, prison, and RPG servers looking to implement a clear progression system that incentivizes players to rank up.

Permission Structure:

• tierkits.command.kit - Access to the /kit command (default: true)
  
  
• tierkits.rank.vip - Access to VIP tier kits
  
  
• tierkits.rank.elite - Access to Elite tier kits
  
  
• tierkits.rank.legend - Access to Legend tier kits

• tierkits.admin - Access to admin control of kits

Easy to configure, lightweight, and designed with both admins and players in mind.

check out the config.yml file here