Introduction

Emaki Series is a set of RPG plugin modules for Minecraft 1.21.8+. CoreLib holds shared infrastructure; business modules add attributes, equipment, strengthening, gems, levels, skills, cooking stations, and the advancement codex.

Technical baseline

Item	Value
Server	Paper 1.21.8+ (minimum supported: 1.21.8)
API	paper-api:1.21.8-R0.1-SNAPSHOT
Java	25
paper-plugin.yml api-version	1.21.8
Build system	Maven multi-module project

Modules

Module	Version	Aggregation	Purpose
EmakiCoreLib	4.6.0	default	Shared infrastructure for all business modules.
EmakiAttribute	4.6.0	default	Attributes, resources, damage, conditions, and API bridges.
EmakiForge	4.6.0	default	Forging, blueprint requirements, material contributions, quality, recipe book.
EmakiStrengthen	4.6.0	default	Star strengthening, protection, failure handling, presentation.
EmakiCooking	4.1.0	default	World-based cooking stations.
EmakiLevel	1.4.0	default	Multiple level types, exp sources, requirements, PDC, placeholders, and MythicMobs exp drops.
EmakiCodex	1.0.0	default	Vanilla advancement codex pages, advancement config, and CoreLib action triggers.
EmakiGem	2.6.0	private-modules	Gems, sockets, opening, inlay, extraction, upgrades.
EmakiSkills	2.6.0	private-modules	Active/passive skills, triggers, resources, MythicMobs bridge.
EmakiItem	2.6.0	private-modules	Custom items, sets, triggers, auto update.
EmakiStorage	1.0.0	private-modules	Paged GUI warehouse, large per-slot quantities, capacity tiers, paid unlocks.

private-modules is a profile declared in the root pom.xml. It activates automatically when a .key file exists in the project root and adds EmakiSkills, EmakiGem, EmakiItem, and EmakiStorage to the build.

Besides the server plugins above, the project also builds compile-time-only artifacts: the per-module emaki-*-api jars and the pure protocol module emaki-skills-protocol (2.6.0), which owns the equipment skill PDC codec contract. None of them are server plugins, so do not put them into plugins/. emaki-skills-protocol is shaded and relocated into CoreLib, Item, Skills, Forge, Gem, and Strengthen at build time.

Why CoreLib exists

Most modules need the same infrastructure: actions, GUI sessions, item-source resolution, PDC storage, economy access, expressions, and structured item presentation. CoreLib centralizes those pieces so business modules can focus on their own gameplay rules.

Common module combinations

• Attribute-only combat: install CoreLib + Attribute. Add PlaceholderAPI, MythicMobs, or MMOItems only if you use those integrations.
• Equipment progression: install CoreLib + Attribute + Item + Forge + Strengthen + Gem.
• Level progression: install CoreLib + Level. Add PlaceholderAPI, MythicMobs, Attribute, Cooking, or Forge when progression needs placeholders, mob drops, attributes, or process rewards.
• Skill system: install CoreLib + Skills + MythicMobs. Add Attribute, Item, or Level when skills need resources, attributes, equipment unlocks, or level requirements.
• Life-skill gameplay: install CoreLib + Cooking. Add Level for cooking/profession exp, and add CraftEngine, ItemsAdder, or Nexo when stations use custom blocks or items.
• Advancement codex: install CoreLib + Codex. Add PacketEvents for advancement tree coordinate injection, and PlaceholderAPI or MythicMobs for their integrations.