Clarify in the book that crafting results have to be inserted into the network

[rubensworks]

Problem

info_book.integratedcrafting.crafting_interface.crafting.text3 currently says:

The Crafting Interface will track changes in the storage network, and it will only mark the crafting job as completed once the expected outputs are present in the storage network.

That reads as "any route into an attached storage counts". It does not: since a11738d completion is detected solely through the network's ingredient channel insert pre-consumer, so only an Integrated Tunnels importer or the machine outputting into the Crafting Interface will do it.

The paragraph does go on to name those two mechanisms, but the sentence before them promises something broader, and that is the reading people take away. It is also the sentence that section explicitly exists to support — "This information is essential to get the most out of this mod, and to debug any issues you may encounter."

I reproduced the resulting state in a game test: a vanilla hopper moving a furnace result into a network-attached chest leaves the ingot sitting in storage, visible to the network, while the crafting job waits forever. The importer variant of the same setup completes normally. That is exactly what #213 reported, and it took eight rounds to resolve there.

Change

Replaces the misleading sentence with one that says outputs must be inserted into the network, keeps the two supported mechanisms where they were, and adds an explicit note about the failure mode and how it presents:

The Crafting Interface will only mark the crafting job as completed once the expected outputs are inserted into the storage network. This can be achieved by either placing an active Integrated Tunnels importer onto the machine, or by letting the machine automatically output into the Crafting Interface. Outputs that reach an attached storage by any other route, such as a pipe or hopper from another mod writing straight into a chest or drawer, will not be detected, and the crafting job will keep waiting even though the outputs are visible in a terminal.

English only; the translations come through Crowdin.

Note

I deliberately did not mention the blocked-output-buffer case here, even though it belongs to the same debugging topic, because the status it refers to only exists once #233 lands. Happy to add a sentence about it in a follow-up if you want the book to cover both stall causes.

Validation

./gradlew build passes.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ACuxaa5QeiZ8mVsEQtwSq1

---

Generated by Claude Code