How jaron-wilson/minecraftplugins works
Project type and purpose
• This “minecraftPlugins” repo is a multi-module Maven workspace where each top-level folder (e.g. CustomBossesAndWeapons, GamericaPlugin, Duel, etc.) is an independent Bukkit/Spigot plugin written in Java.
• Each plugin’s job is to hook into the Minecraft server API (Bukkit), register commands and event listeners, manage game state or custom content (bosses, NPCs, minigames), and persist configuration or runtime data in YAML files.
File structure
• You have N Maven modules (one per plugin). Each module has:
• pom.xml (build/dependencies)
• src/main/java/me/... – Java packages for:
– Main plugin class (implements JavaPlugin)
– commands/ (CommandExecutors & TabCompleters)
– listeners/ (EventListeners for player join, block break, damage, etc.)
– managers/ or util/ (singleton-style classes handling config, item registry, NPC registry, etc.)
– subpackages (e.g. custom/itemEvents, allnpcs, mobManager, guis, minigames) for feature domains
• src/main/resources/plugin.yml (plugin metadata)
optional config.yml and data.yml for runtime persistence
• Pattern: Event-driven architecture using the Bukkit event bus + Command pattern. Managers and utility classes encapsulate business logic.
Extract insights from README
• The README confirms these are standalone plugins, each with a focused domain:
• CustomBossesAndWeapons: custom items/events, NPCs, bosses, recipes
• GamericaPlugin: minigames framework, AFK, quest NPCs
• Duel: 1v1 arenas, stats, kits
…etc.
a. Main components
– Minecraft Server (Bukkit API)
– Plugin Loader & Lifecycle (JavaPlugin class in each module)
– Event Bus & Command Dispatcher (provided by Bukkit)
– Feature Domains (packages / modules):
• Command Modules (commands/)
• Event Listeners (listeners/)
• Managers (ConfigManager, NPCManager, ItemManager, ArenaManager, etc.)
• Domain Services (mobManager, custom/itemEvents, guis, minigames, npcthings)
– Persistence Layer (YAML files: config.yml, data.yml)
– External Services (Vault economy/chat, Citizens NPC API, Metrics)
b. Relationships and interactions
– Server → onEnable(): loads plugin, instantiates MainClass
– MainClass → registers Commands & Listeners with Server
– Player issues /command → CommandDispatcher → CommandExecutor → calls Manager or Domain Service → updates game world or actor
– Server fires Event (PlayerJoin, BlockBreak, EntityDamage) → EventBus → appropriate Listener → invokes business logic in Manager/Service
– Managers read/write config/data files asynchronously or on shutdown
– Domain Services may call external APIs (Vault, Citizens) or schedule Tasks (timers)
c. Architectural patterns & design principles
– Event-driven design (publish/subscribe via Bukkit event bus)
– Command pattern (each command handler implements CommandExecutor)
– Manager/Service singletons encapsulating state and shared behavior
– Layered separation: API (commands & listeners) → Business Logic (managers/services) → Persistence
– Dependency injection is manual: MainClass passes references to managers when registering listeners/commands
d. Key technologies, frameworks, libraries
– Java & Bukkit/Spigot API
– Maven for build/dependency management
– SnakeYAML (bundled in Bukkit) for YAML config/data
– Optional plugins: Vault, Citizens, Metrics (bStats)