◆ EmakiCoreLib 3.2.0 ◆
Structured Presentation And Item Source Refresh
A core-library release focused on cleaner display layering, unified vanilla source rules, and lighter runtime packaging
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
✦ Highlights ✦
- ◆ The legacy item-presentation editing chain, lore-search insertion helpers, and old edit-item action path were removed in favor of the structured presentation stack.
- ◆ Item assembly now supports explicit layer removal, and the CoreLib namespace registry now includes the cooking layer for downstream rebuild and rollback flows.
- ◆ Vanilla item and block sources are now normalized around minecraft-, mc-, v-, or bare identifiers; the old minecraft:item_id style is no longer accepted as a valid source input.
- ◆ CoreLib now exposes a CraftEngine block bridge, while GUI previews and item-source services share the same vanilla material resolver to reduce parsing drift.
- ◆ Item text bridging now preserves vanilla translation keys, adds stable effective-name helpers, and improves hover-text output for item-linked messages.
- ◆ Adventure, MiniMessage, serializer, exp4j, and boosted-yaml runtime dependencies are now declared through Spigot libraries instead of the previous bundled packaging path, 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.
- ◆ Custom configs that still rely on legacy edit-item or old lore-operation style display paths should be migrated to structured_presentation.
- ◆ This build expects runtime library resolution through Spigot libraries, so first boot should be allowed to fetch or reuse the required dependency cache.
- ◆ If you still carry old defaults-based data layouts, re-check them against the current bootstrap synchronization path instead of expecting legacy migration behavior.