Skip to content

Getting Started

This page helps server administrators quickly understand the deployment process and recommended activation order for Emaki Series.

Requirements

ItemRequirement
Java25 or higher (GraalVM recommended)
ServerSpigot 1.21+ (or compatible forks such as Paper)
Runtime LibrariesAdventure, exp4j, BoostedYaml (automatically loaded by CoreLib via plugin.yml libraries)

提示

When deploying EmakiCoreLib 3.2.0 for the first time, make sure the server allows downloading runtime libraries via plugin.yml libraries, or prepare the corresponding library cache in advance.

Follow this order to enable modules step by step, minimizing troubleshooting effort:

Step 1: Infrastructure and Attribute Layer

  1. EmakiCoreLib — Hard dependency for all modules, must be installed first
  2. EmakiAttribute — Attribute and combat system, provides the numerical foundation for subsequent equipment progression

Verification: Confirm CoreLib loads correctly, and Attribute definitions and combat calculations work properly.

Step 2: Equipment Progression Loop

  1. EmakiForge — Forging system
  2. EmakiStrengthen — Strengthening system

Verification: Confirm forging recipes execute correctly, and the strengthening process and star-level progression work properly.

Step 3: World Interaction and Gem Progression

  1. EmakiGem — Gem system
  2. EmakiCooking — Cooking system

Verification: Confirm gem inlaying/extraction/upgrading processes work correctly, and cooking stations are interactable.

Step 4: Active Skill System

  1. EmakiSkills + MythicMobs content packs

注意

EmakiSkills is a skill management layer; the actual skill effects are handled by MythicMobs configurations. Skills can still be enabled without MythicMobs, but actual skill casting will fail.

Module Dependency Matrix

ModuleHard DependenciesSoft Dependencies
EmakiCoreLibVault, ExcellentEconomy, PlaceholderAPI, MMOItems, ItemsAdder, Nexo, NeigeItems, CraftEngine
EmakiAttributeEmakiCoreLibMythicMobs, PlaceholderAPI, MMOItems
EmakiForgeEmakiCoreLibEmakiAttribute, PlaceholderAPI
EmakiStrengthenEmakiCoreLibEmakiAttribute, PlaceholderAPI
EmakiCookingEmakiCoreLibCraftEngine, ItemsAdder, Nexo
EmakiGemEmakiCoreLibEmakiAttribute, PlaceholderAPI
EmakiSkillsEmakiCoreLibMythicMobs, EmakiAttribute, PlaceholderAPI

Command Quick Reference

ModuleRoot CommandAliases
EmakiAttribute/emakiattribute/eattribute, /ea
EmakiForge/emakiforge/eforge, /ef
EmakiStrengthen/emakistrengthen/estrengthen
EmakiCooking/ecooking/ec
EmakiGem/emakigem/egem, /eg
EmakiSkills/emakiskills/eskills

Default Resource Locations

Each module's configuration and resource files are automatically extracted to the server's plugins/<module-name>/ directory on first startup:

ModuleMain Resource Directories
EmakiCoreLibconfig.yml, lang/
EmakiAttributeattributes/, conditions/, damage_types/, lore_formats/, profiles/, config.yml
EmakiForgerecipes/, gui/, lang/, config.yml
EmakiStrengthenrecipes/, gui/, lang/, config.yml
EmakiCookingrecipes/, gui/, lang/, item_adjustments/, config.yml
EmakiGemgems/, items/, gui/, conditions/, lang/, config.yml
EmakiSkillsskills/, resources/, gui/, lang/, config.yml

Upgrade Notes

  • Back up custom configurations, language files, and default resource copies before upgrading
  • Migrate all custom vanilla item/block sources to minecraft-xxx, mc-xxx, v-xxx, or bare ID format
  • Migrate custom presentations to structured_presentation
  • For detailed upgrade instructions, see the Changelog

Released under the GPL-3.0 License