Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support Forge 1.20.6+ and NeoForge 1.20.4+ #23

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

Johni0702
Copy link
Contributor

See individual commits.
ML11 is required for NeoForge 1.21 (LexForge stayed on its fork of ML10).
KFF5 is required for 1.20.6+ (and is the only thing required for Forge 1.20.6+).

Former is Forge specific, latter is ModLauncher specific, and while they
tend to change at the same time, that'll no longer be true once we also
consider NeoForge.
Newer Forge versions will put inner jars (such as Kotlin inside KFF) on
a layer which depends on the outer jar (KFF), which may be different
than what one would expect from just looking at the Kotlin jar.
As such we can no longer determine the layer ahead of time and will
instead assume that layers are built in order, and just assume whichever
layer is the most recent one.
Note that we cannot easily just check which layer our SecureJar is in
because it may be further wrapped by e.g. KFFMerger and as such may not
directly appear in any of the lists at all.
Will be required for KFF5 which uses JarJar, so we want to emit all our
Kotlin jars separately instead of merging them into the outer jar.
Copy link

Test Results

16 files  ±0  16 suites  ±0   11m 46s ⏱️ -6s
95 tests ±0  95 ✅ ±0  0 💤 ±0  0 ❌ ±0 
99 runs  ±0  99 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 225bac4. ± Comparison against base commit f75128a.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant