ВЕРСИИ (3)

## MekaCrafter 1.0.0 for NeoForge 1.21.1 ### Requirements - Minecraft 1.21.1, NeoForge 21.1.100 or newer, Java 21 - Mekanism 10.7.19 or newer - Mekanism Extras (optional) ### Changes - First release. - Autocrafting machine bound to a QIO frequency: plans the full recipe tree from base materials and crafts every intermediate step, storing the result back into the QIO. - Crafting table and stonecutter recipes. - Complete and precise missing-materials list in a pinnable Mekanism-style window. Each entry shows what it is needed for and whether it must be made in another machine (control circuits, alloys...). - Item variants in the QIO (charged energy tablets, renamed items...) count as stock. - Energy model like a Mekanism machine: configurable usage per tick (400 FE/t by default), energy upgrades, pause and resume without losing progress or materials. - Job queue with intermediate sub-jobs, progress bar with total energy and time left, cancel and clear buttons. - Planning runs off the server thread, so big recipe trees do not freeze the tick. - Animated machine model with active LED, Minecraft-style buttons, energy gauge and energy tab. - Settings in `config/mekacrafter-server.toml`: energy usage, storage, ticks per craft, job overhead. ### Notes - Only crafting table and stonecutter recipes are automated. Items made in Mekanism machines are listed as materials to supply. - Binding needs a Portable QIO Dashboard set to your frequency; there is no frequency selector in the GUI yet. - This replaces QIOAutocrafter 0.2.0 (Forge 1.20.1), which is no longer maintained.

## 0.2.0 — First beta **⚠️ Update server and clients together: the network protocol changed (v3). Old worlds load fine.** ### Fixed - **Item duplication on chunk unload**: reserved materials were refunded twice if a chunk unloaded mid-craft. - Machines bound to a private QIO frequency can no longer be used, rebound or drained by other players (Mekanism PUBLIC/TRUSTED/PRIVATE security is now enforced). - A failed job no longer stalls the rest of the queue. - Completed and cancelled jobs are removed from the queue automatically; the job history can no longer cause a false "queue full". - "Clear list" in the missing-materials view now actually clears it. - Craftable search results no longer leak between worlds/servers after switching or `/reload`. - Cancelling a job now also stops its background planning computation. ### Added / Changed - **Redesigned GUI**: wider window, single action row, live status in the activity bar. - **New "Missing Materials" side panel** (toggled by the Missing button): item icon, name, missing amount and live availability — red/orange/green as you restock the QIO. - Identical duplicate requests are rejected while one is already queued. - If the QIO changes between planning and reservation (other players/machines), the job re-plans automatically instead of failing.

# WORK IN PROGRESS # This update improves how missing materials are calculated and displayed when attempting to craft items. ### What changed ### The recipe planner now analyzes the entire crafting dependency tree when a recipe cannot be completed. Instead of only reporting missing items at the current step, the system now: Traverses all sub-recipes recursively Calculates missing materials across all branches Consolidates duplicate requirements into a single total Returns a complete and accurate list of everything needed Result You now get all missing materials in a single message, including intermediate components. No more iterative guessing or repeated crafting attempts. ## Example ## ### Before: ### Missing materials were revealed step by step Multiple retries were needed to discover full requirements ### Now: ### All required materials are shown instantly Fully consolidated and ready to act on Technical details estimateMissingMaterials() is now always executed on planning failure Fallback to flatten(state.missing) if estimation returns empty No impact on existing crafting logic or performance Uses already optimized internal systems Stability Build successful All tests passing Safe change focused on logic improvement Impact Improved user experience Faster crafting workflow Eliminates friction when dealing with complex recipes