How martijn-heil/fables-and-fantasy-rp works
This project is a multi-module Gradle repository that produces a suite of independent Spigot plugins written in Kotlin. Each subproject (located mostly under the “plugin” directory) corresponds to a distinct functional or technical plugin for a Minecraft role-playing server. The project also contains dedicated directories for build conventions (buildSrc), code examples (examples), and third‐party dependency jars (lib).
Build and Deployment Infrastructure
• A “Gradle Build System” component at the top. Note that the buildSrc module is used as the centralized conventions plugin for dependency management, configuration, and shared build rules.
• “Deployment Scripts” (e.g., deployto.sh, dependencies.sh) that take the produced plugin JAR files and copy them to the destination server.
• Overall build pipeline: source code (per subproject) → Gradle build → Individual plugin JARs.
Modular Plugin Architecture
• Subprojects into logical clusters. For instance, the “plugin/core” folder holds key function plugins (Characters, Chat, Economy, Inventory, etc.); “plugin/extra” contains add‑ons (Activity, DailyRewards, FastTravel and others); and “plugin/technical” includes integrations (Database, DenizenInterop, Discord, WorldGuardInterop, etc.).
– Core plugins (direct gameplay systems),
– Extra plugins (optional or add-on systems), and
– Technical plugins (infrastructure, integrations, and utilities).
Runtime and External Dependencies
• Connections from plugins to external libraries or systems:
– Database components (H2 Database, migration scripts, and associated repository layers) for persistence support.
– Third‑party jar dependencies from the “lib” folder and any external APIs referenced in the README (e.g., Spigot Javadocs).
• Mention that many plugins follow similar architectural patterns: a main plugin class, event listeners, commands, domain layers (for data and business logic), and sometimes web or interop modules (e.g., for Discord and Denizen).
• If space permits, include annotations that mention key design principles applied in the project – such as modularity (each plugin is a self-contained subproject), separation of concerns (domain logic, presentation via GUIs, data persistence), and the event‐driven architecture typical of Spigot plugins.
• Depicting a layered view: the top layer shows build/deployment processes, the middle layer shows the various plugin modules interacting with the Spigot server, and the bottom layer shows data sources (e.g., H2 database, configuration files) and external integrations (Discord, Denizen).