Describe the bug
Even when disabled in the config, ae2 falls back to the crafting manager when autocrafting. I do believe this is an issue with this fork, as the config has been respected properly in standard ae2 1.12.2.

To Reproduce
Disable crafting manager fallback in config, configure a pattern in a way where the crafting manager would be used and attempt to autocraft. This is best shown with a debugger or spark.

Expected behavior
Ae2 does not fall back to the crafting manager and instead autocrafting fails to start.

Additional context
This is the only screenshot I have to hand, it's part of a spark profile.
Environment

Running on the Omnifactory dev branch. I did not encounter this issue elsewhere.

make sure all you ME system is chunkloaded. this call to the crafting manager would not be affected by the fallback config option

The full network is loaded, yes. Why would this not be affected by the config, and what exactly is affected?

do you have the original spark profile?

please test with 45n

45n? I don't have the original profile to hand but I should be able to get a new one soon. (the last one ran for an hour, if you mean 45 minutes)

https://github.com/PrototypeTrousers/Applied-Energistics-2/releases/tag/omni-fixes-v45
v45n, latest jar

not really, it wont connect with mismatched versions sorry

Can I safely update this on a server without requiring clients to update?

I can deal with the version mismatch, that's an easy change. I was more on about whether there'd be actual issues with the changes that were made between 43h and 45n? (looking at the change log I don't think so but I wanted your opinion before trying)