Applied Energistics 2

Applied Energistics 2

137M Downloads

A lot of the recipes don't work

Audixas opened this issue ยท 11 comments

commented

Description

Some of the recipes don't work. The ones I have tested so far are: ME (Crafting, Interface) Terminal, Silicon, any of the Inscriber recipes, Molecular Assembler, Nether Quartz tools, Network Tool, Crafting Card, Storage Monitor, all P2P devices apart from the ME one.

Environment

First noticed on me and my friend's modded server. Testing also done in singleplayer with the same mods and then in singleplayer with just AE2 and JEI installed. The problem persists across all of these, meaning the problem is not with the other mods we're using.

  • Minecraft Version:
  • AE2 Version: appliedenergistics2-rv5-stable-8
  • Forge Version: 1.12.2-forge1.12.2-14.23.2.2613
commented

fml-junk-earlystartup.log
latest.log
fml-client-latest.log

Here are the logs that I think are relevant.

commented

Can you post the full path of the ae2 config folder? What are the contents of the "aerecipes" subfolder?

commented

config.zip

Here you go. There are a bunch of other configs for mods that I removed before testing to make sure it wasn't some sort of mod conflict. And the aerecipes folder is empty.

commented

Can you please post the full path? We had problems with some path names in the past. Although it should be fixed this issue looks awfully similar.

commented

!singleplayer.zip

This is in AppData/Roaming/.minecraft. I seperate all my profiles into different folders with an ! at the start so they appear at the top.

Hopefully that's what you meant by full path.

commented

hmm, yeah .. can you try withouth the "!" ? eg create a new instance with an alphanumeric name?

commented

Removing the ! solved the problem. Thank you very much!

commented

This is most likely not an AE2 bug, but a vanilla or forge one as most of the mentioned recipes are handled by them.

commented

Cannot reproduce.

commented

Can you post some logs?

commented

Forge does not even allow ! as buildpath. Why it allows it for a normal instance compared to a dev one is beyond my grasp. But they should certainly display a warning in these cases.