EmakiCoreLib 3.2.0

EmakiCoreLib 3.2.0 is the release that fully consolidates the Emaki suite around the newer structured-presentation runtime, the unified vanilla item-source syntax, and the lighter runtime loading path. The most visible benefit for administrators is not a single flashy mechanic, but a cleaner base: layered name and lore rendering is more stable, rollback flows are more precise, vanilla item and block sources now follow one shared shorthand rule, CraftEngine-backed block matching has a proper bridge in CoreLib, and runtime libraries are no longer carried through the old bundled packaging path.

• Structured presentation is now the main display path. The old item-presentation compiler, editor, and lore-search insertion chain were removed in favor of the newer template, validation, and rendering stack.
• Layer removal is explicit now, and the cooking namespace is wired in. Item assembly can remove one or multiple layers directly, and CoreLib now registers the cooking namespace for downstream rebuild, rollback, and cleanup flows.
• Vanilla source parsing is now standardized. CoreLib only accepts minecraft-, mc-, v-, or bare vanilla identifiers for item and block sources, while the legacy minecraft:item_id format is no longer treated as a valid source input. Runtime shorthand output is normalized to the minecraft-item_id style.
• CraftEngine block integration is cleaner. CoreLib now exposes a reusable CraftEngine block bridge, and both GUI preview building and item-source resolution share the same vanilla material parsing path.
• Item text handling is more reliable. The text bridge preserves translation-key based names and provides stable helpers for effective names, plain text, and hover-linked display output.
• Runtime packaging and YAML loading were simplified. Adventure platform libraries, serializers, exp4j, and boosted-yaml are now loaded through Spigot libraries, the previous bundled Gson / SnakeYAML path has been cleaned out, and YAML IO is consolidated around BoostedYaml.

Upgrade Notes

• Migrate any remaining minecraft:item_id item or block source entries to minecraft-item_id, mc-item_id, v-item_id, or a bare vanilla id.
• Migrate any remaining legacy display editing configs to structured_presentation.
• Make sure the server environment can resolve the declared Spigot runtime libraries on first boot.
• If your deployment still carries older defaults-based resource layouts, re-check them against the current bootstrap synchronization path instead of relying on the removed legacy migration behavior.

View Full Documentation | Join Discord Community | QQ Group