After a normal or an emergancy restart from the server, all craftingpipes are not working so the hole provess must started again which is impossible if the required items are not in the system but in the logistics crafting table.

So I think that it will be better, if you store all active craftings in a file with current status of the crafting, updated after 10 to 15 min (should be good enough but editable over config, only client side).

It happends on FTB Infinity 1.5.0 (MC 1.7.10).

Sincerly
Chaos234

It is impossible for us to really come around this issue, as storing the current crafting tasks e.g. in a file (as you said) would horribly fail, because on servers with a busy LP network we would have far too many file system accesses. That is bad, as the file system is still the computer's slowest part.
We can look into this again and think of something to prevent this from happening, but I do not know if we come to a solution. Until then you can consider the cleanup upgrade for crafting pipes. That should clean all the contents of your crafting table when you restart your server.

Well, this is actually the best workarround I think and yes, it will be very slow with a filesystem part.

Hmmm, what is with the crafting monitoring/status upgrade? It's actually only for one special table, but if it's possible to add the crafting logistics table also as supported one, then the current crafting order can be stored in there and after a reboot reactivatet. So it should be, at the "stop" cmd, save the current state (amount to craft, materials stored, amount left to craft) and then simply reload it.

Is this possible? It's better as my first idea, I think.

It would be a shitload of work...to actually remember the Items it has, It needs and it has to make. And reorder missing items.

plus, when the Server Crashes by Exeption, the data is lost Anyways since you have no stop Command there, exept the Server Stopped Event by Forge and thats allready to late

@Bitterholz For the first comment, Actually LP already is keeping track of this. It would just be a matter of storing it to disk on shutdown.

As for the second comment, that is exactly right. If LP doesn't get a chance to save the data... yeah... But, it would be a nice feature to have for normal server restarts. But the cleaner upgrade can essentially do that anyways, as any automated systems using requests would auto-start themselves again anyhow, and manual requests could just be repeated once you see the cleaned items land in storage.

Another thought for people that are not far enough along to have the cleaner upgrades would be a feature of the table that when the sever is started, or perhaps the LP 'network' is rebooted by yanking the junction off and replacing it, the tables would automatically empty out.