AE ate my diamonds :(

[Affex]

Sure, but it's so simple, there's not really much to show. The portal from the portal gun is, about 20-30 blocks away on my left. It's actually on the wall of a giant 12x12x12 Xycraft tank.

Spoiler

View attachment 3229

Then It might be a problem with unloaded chunks. I dont think the portal loads that much area

 

[PhilHibbs]

Wow... ok, maybe we should just close this thread. I just came in here cos I encountered a problem, and I asked if anyone had seen similar, or had advice on how to avoid it in future.
I think what I'll avoid in future is asking for help.

So one person says something unhelpful, and you give up on the whole community? The internet is not for the thin-skinned.

 

[KirinDave]

My favorite is when you tell it to craft like 10 of something and it will craft like 3 and then delete the job out of the que like it never existed. A few times I've had it delete items that were going in the system, after a server restart it was fine.

I think recently the system changed so that eventually jobs time out and the system knows to stop retrying. Because it's definitely the case that I've abused the most recent f and g builds w.r.t. incorrectly using Factorization packagers (hopin' to save on quartz, yo!) with ME interfaces and eventually the system said, "Fine. Guess what? You've freakin' got iron dust and that's not my problem anymore." Which is fine, although I do wish the crafting monitor exposed that decision to my eyes.

 

[Velotican]

Additionally, if you add or remove something from your ME network, it instantly reboots the entire network and cancels all active crafting jobs. Some of you might be falling victim to that by mistake, but it's also a behaviour that's very useful for recovering a stalled crafting job.

I've found that on the default version used in FTB crafting will also time out if there is no noticable progress from external processing jobs after a certain period. This is probably to stop external machine jams from locking up your crafting system but it's not perfect.

 

[Iskandar]

I used to be a programmer. I hate these kind of bugs. HAAAAAATE hatey hate hate. Give me a bug that you can demonstrate reliably and on command, and I'll track it down and make it a very dead bug in a very short amount of time. But a bug that just shows up occasionally, or once, for no discernible reason, and just whenever in the process if damn well feels like? HAAAAAATE. Especially if it just happens for the user, and all he can do is try his best to explain what he was doing and what, exactly the bug was? So much hate. Nothing against end users, but they aren't programmers, and they usually have no idea what exactly I am looking for or how even the smallest detail left out could hide the bug.

I'd look, of course. And occasionally the bug would be found and fixed. Most got marked CNR, could not reproduce after a few hours, and logged for the next poor bastard who ran across it.

I have much sympathy for Minecraft modders. Some of these mods are huge, and all are fairly complicated.