I originally posted this over on the AE2 github located here:
AppliedEnergistics/Applied-Energistics-2#2934

After exhaustive troubleshooting, I've come to the conclusion that this issue only occurs when your mod is installed on the server.

• Minecraft Version: 1.7.10
• AE2 Version: appliedenergistics2-rv2-stable-10
• Forge Version: I'm not sure...Here are the list of jar's within the 1.7.10 folder:
  ForgeMultipart-1.7.10-1.2.0.345-universal
  ForgeRelocation-0.0.1.4-universal
  ForgeRelocationFMP-0.0.1.2-universal

After spending a considerable of time trying to learn AE2, I discovered that when an item, any item, is placed within a specific slot in your inventory, the autocraft window will close when you should be presented with a followup window asking how many you'd like to create.

Also, when something is placed in this inventory slot, when viewing 'Crafting Status' within the ME Crafting Terminal, the client will definitely crash and occasionally, the server will crash.

The inventory slot is 2nd row down, 4th from the left.

I wouldn't believe this report if I had seen it for myself, so I've included a video, where I go through a few different permutations in an attempt to rule out chance.

https://vid.me/CGQg

Should you need any further information, I'd be more than happy to offer whatever assistance I can.

I recently encountered this as well and have done some testing to figure out why only 2 of my terminals were crashing when others in my void dimension were working fine. It appears that it only affects terminals which are placed in the portal chunk of the Void dimension get affected by this bug (at least for me).

I posted this here because it exists in your current codebase if you'd bother to read the other bug report.

read here:

https://forum.feed-the-beast.com/threads/ae2-clicking-autocrafting-closes-inventory.240633/

Please remember when posting on mc mod issue trackers: We do this for free. I fail to see how I'm supposed to just assume that you mean all versions when you only specify 1.7.10 no matter what the other issue on another mod's tracker says.

see here:

Still, I definitely appreciate your taking the time to research this and even make a video..I was kinda lost as to exactly how many slots/which caused this. I'll def get this handled in the next update. No ETA atm..I have a ton of stuff I'm working on atm not mention recovered from recent health issues. Please bare with me.

I didn't read your bottom note. I guess I poured gas on the fire. I'm sorry about your health issues, I hope everything is better.

I just lost my job myself. I read your original giant picture as a middle finger. Perhaps I took that too harshly.

Best of luck friend. I'll offer whatever help I can.

Thing is...it's not always that slot. When I did it on my own server (which was the same world) it was 3rd from the left on the bottom row....But everybody who uses AE2 on the same server, experiences the same slot....if that makes sense. Now the thrown exception is within AE2's packet handling code. So I'm guessing your addon hooks into AE2 there?

If you're going to look into it... You should note that the other bug report contains the caught exception for when I dropped out in the video. (EDIT: pastebin for caught exception)

And again, if it helps, I'm willing to help out with whatever testing you require....just note that I'm running 1.7.10.

EDIT: https://pastebin.com/2gX0k5Vj

cool..the crash log should definitely help, thanks again

it looks like same/similiar issue that was present in 1.7 (#72) :(

I'm swamped with stuff atm, I will get to this as soon as I can. All of the settings that were at one point saved, seem to now not be saving..something got borked somewhere down the line..thanks for the reports..sorry I can't do it any faster.

is this still happening on latest version on curse (v0.1.32)?

Unfortunately I won't be able to test this update for a few days, maybe up to a week as I'm out of town. When I'm back, I'll put it in my test server and see. Thanks for the update.

No worries, test when you have time :) @JasonMcRay I would like your input on this as well if you can find the time.

I would really like to get someone experiencing this to try and help fix the problem..I have tested and tested and I can't reproduce this bug. I'm going to close the issue as I haven't gotten any replies...You're more than welcome to reopen if you wish to help me in being able to reproduce this bug.