How koirdsuzu/uberitems works
Project type and purpose
• This is a Minecraft “Paper” server plugin named UberItems.
• Purpose: provide a GUI-based item shop with distance-based shipping, integrating with Vault for economy and optionally QuickShop for player shops.
• Minecraft Server → UberItems Plugin Core (lifecycle hooks, events)
• Plugin Core → Configuration Layer (load/save)
• Plugin Core → Command Layer & Event Layer (register)
• Command Layer → GUI Layer (open main menu)
• Event Layer → GUI Layer (handle clicks → navigate GUIs)
• GUI Layer ↔ Model Layer (GUI displays CategoryItem/ShopItem data)
• GUI Layer → Persistence Layer (read/write player shop data)
• GUI Layer → Economy Layer (calculate shipping + price)
• Economy Layer → Vault API (external service)
• GUI Layer → Integration Layer (when accessing player shops via QuickShop)
• Integration Layer ↔ QuickShop API (external plugin)
• Utility Layer – used by GUI Layer, Model Layer, Integration Layer for common tasks
Architectural patterns & design principles
• Modular package‐based separation (commands, listeners, gui, model, util, config, database, economy, integration)
• Event-driven design (listeners respond to server & GUI events)
• MVC-inspired layering in GUI: Model stores data, View = GUIs, Controller = listeners/commands
• Dependency Injection via ConfigManager, VaultManager, PlayerDatabase
Essential elements
• Main plugin component with lifecycle
• Layers: Config, Commands, Listeners, GUI, Model, Persistence, Economy, Integration, Utils
• External services (Vault API, QuickShop API)