How alonsomoros/lkt_mods works
Project Components
• Minecraft Game Engine – The base game that will run with the Forge mod loader.
• Forge Mod Loader – The framework that loads and manages the mod jar files.
• Mod Categories – Organize the mods into logical groups:
– Server Mods (mods/server): Mods that affect server-side functionality (gameplay mechanics, world generation, quests, dungeons, etc.).
– Client Mods – Divided into at least two groups:
▪ “Personales” (mods/personales): Personal or client-specific mods for UI enhancements, help interfaces (like JADE, JEI, Journey Map, etc.).
▪ “Crashed” (mods/crashed): Mods that appear oriented towards performance or rendering improvements (e.g., ImmediatelyFast, Legendary Tooltips, Embeddium).
– “por_determinar”: Mods under consideration (e.g., Paraglider, SecurityCraft) which might later be categorized.
Relationships and Interactions
• The Minecraft Engine interfaces with Forge, which acts as the central mod loader.
• Inter-mod interactions, such as FTB Quest integrating with the quest and menu system, or mods like Patchouli providing in-game guide book functionality.
Architectural Patterns and Design Principles
• Separation of Concerns: The directory split clearly delineates server-side mods, client personal mods, and performance enhancements.
• Extensibility and Modularity: Since the project supports adding new mods (as seen in the “por_determinar” and “nuevos” directories), include an element indicating the support for extensibility.
Technologies and Frameworks
• Minecraft using Forge as the mod framework, identifying that mods are jar files compatible with the Forge version (note the version numbers in jar names).
• Specific mods that bring in specialized functionality (e.g., Biomes O’Plenty for world biomes, Apotheosis for gem/tier systems, and Clumps for XP optimization).
Detail and Clarity
• Be very detailed: break down the architecture so that every element in the file tree is captured as a component in the system.
Happy diagramming!