How magemonkeystudio/fabled works
Project type and purpose
• This is a Java-based Minecraft server plugin (Paper/Spigot) and API library (“Fabled”) that extends SkillAPI to provide dynamic, data-driven RPG classes, skills, events, and mechanics on a Minecraft server.
• It is not a web or full-stack app, but a domain-specific plugin/tool designed to register commands, listen to in-game events, load and parse skill/class/trigger definitions (YAML), and apply game logic via a scheduler and event loop.
File structure
• Top‐level “src/main/java” contains two main packages:
• com.sucy.skill – the original SkillAPI fork core classes and interfaces
• studio.magemonkey.fabled – the Fabled plugin itself
• Under Fabled:
• api/… – public API interfaces and default implementations for classes, skills, events, player data, armor stands, particles, etc.
• data/… – configuration definitions, IO and SQL management
• dynamic/… – the engine for loading and running user-defined components: triggers, conditions, mechanics, targets, effects
• cmd/… – command definitions and dispatcher
• listener/… – Bukkit event listeners that funnel events into the Fabled engine
• hook/… – integrations with other plugins (Vault, PlaceholderAPI, etc.)
• gui/… – inventory-based GUIs for class/skill menus
• manager/… – singleton managers for attributes, combos, titles, resource loading
• shield/, cast/, task/, thread/, tree/, util/… – sub-domains handling shields, cast bars, scheduled tasks and threading, skill tree layouts, helper utilities
• Configuration and resource files in src/main/resources (YAML configs, plugin.yml, images, internal/jar modules).
README for additional insights
• Confirms this is a fork of SkillAPI with premium features and a “dynamic editor” external web service for authoring class/skill definitions.
• Provides Maven coordinates – this plugin is consumed as a library, so the API layer must be cleanly separated from implementation.
Elements
• Labels: e.g. JavaPlugin, ResourceManager, ComponentRegistry, SQLManager, Bukkit EventBus, TaskScheduler
• Plugin Enable → ConfigIO, SQLManager, ResourceManager
• Bukkit Event → FabledListener → DynamicEngine → MechanicExecutor
• DynamicEngine → TaskScheduler → Task Execution
• GUI click → GUIHandler → ResourceManager → PlayerData
• Green for core implementation managers
• Orange for dynamic engine components
• Purple for external hooks
Final advice
• Be very detailed: break the plugin down into its subsystems (entrypoint, config, data, engine, commands, GUI, persistence).
• How configuration files drive class/skill loading, how triggers and mechanics execute, and how data flows in and out via events and SQL/YAML.