Mithi83

Simple setup, from left to right: Creative Energy Cell, Smart Cable with Pattern Access Terminal, Pattern Provider (without any name) and next to it different machines as follows yields a...

The named inscriber ends up in the code path in `PatternContainerGroup.fromMachine()` that consists of the last else block, there it checks `if (target instanceof Nameable nameable && nameable.hasCustomName())`. The first...

Ok, on second thought it would be a very stupid idea to push items into a full block interface that would immediately put them back into the main network… So...

Some more debugging as to why the Inscriber in my example has no name: AEBaseBlockEntity.loadTag is ```java if (data.contains("customName")) { this.customName = Component.literal(data.getString("customName")); } else { this.customName = null; }...

If I interpret my previous ramblings correctly the correct way to do what you want (i.e. changing the names in the pattern access terminals) is renaming the machines attached to...

This matches my findings in https://github.com/AppliedEnergistics/Applied-Energistics-2/issues/8049#issuecomment-2248749000

I'm using the latest main branch for my own development and can still reproduce it. I'm not sure what conditions are relevant, could be a GPU driver issue. I'm running...

I'm pretty sure it is mathematically impossible to make it work in all cases. Basically you have two different variants of the texture, A and B. To make it look...

The intention behind attaching multiple machines to the same pattern provider is that you can parallelize the **same** machines (which in this case means an inscriber with one defined press)...

A workaround for your specific use case might be to work without an inverter card and an explicit blacklist for the blood liquid and rather forbid any fluids to be...