Cassian Godsted
Cassian Godsted
Yeah, it's not an issue for me on 1.21.5 as I (alongside Architectury) dropped Forge in favour of NeoForge back on 1.20.4.
Can confirm PR #278 fixed this issue.
I'd recommend using the Architectury[ template generator](https://generate.architectury.dev/) to generate projects instead of the IntelliJ plugin. The Gradle plugins handles NeoForge fine when the project is created.
`c:chests/metal` could always include `c:chests/copper` - though I think mods are less likely to register their own copper chests at this point. The primary use case to me would be...
Tag differences aren't available on both loaders, making a dedicated tag the preferred solution in my eyes.
Nevermind, the format was different and I wasn't aware of it. There's custom ingredients.
NeoForge on 1.20.1 is equivalent to Forge on 1.20.1, and has to be set up as Forge on 1.20.1 instead of NeoForge - replace `neoForge()` and similar with `forge()`.
Either use MCA on Fabric or NeoForge, or downgrade to 1.20.1. Architectury does not support Forge on 1.21.1, and a port is not currently planned.
One of your mods (most likely Mo Structures) is using Omegaconfig, which causes a crash with Architectury (see https://github.com/architectury/architectury-api/issues/528). You will likely need to remove it until they fix the...
One of your mods is requiring Java 18 and you're using Java 17. Try running with Java 18 or higher, and/or send a full crash log.