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

Update to 1.21 + NeoForge #3

Closed
wants to merge 11 commits into from
Closed

Conversation

Leo40Git
Copy link
Contributor

This PR will replace the Forge release with a NeoForge release.

Leo40Git and others added 5 commits December 29, 2024 21:22
Update Architectury Loom
Disable legacy mixin AP
Disable Forge subproject for now, pending conversion to NeoForge
Fix mysterious XML-related error during project build
Update Architectury Loom
Disable legacy mixin AP
Disable Forge subproject for now, pending conversion to NeoForge
@Leo40Git Leo40Git changed the title Update to 1.12 + NeoForge Update to 1.21 + NeoForge Dec 30, 2024
This somehow fixes a method in Supplementaries that doesn't get remapped. Don't ask questions...
We only need one mixin now, since there's only one onBlockUse method
Removed the mixin plugin and RchSupplementariesCompatPlatform.isFabric, since they're no longer used

Unfortunately, the mixin is apparently broken in some arcane way; the ModifyArg injection is never invoked...
@Leo40Git
Copy link
Contributor Author

Leo40Git commented Dec 30, 2024

In theory, the mixin (yes, one, see 98ca84a) is now functional.

Problem is, the ModifyArg injection never gets invoked...

Simply RightClickHarvestMixin: remove Inject for capturing Level argument, use ModifyArg with full method signature instead
Bump version to 2.0.0
Fix ModMenu and Supplementaries versions
Disable NeoForge subproject for now (until I can figure out how to unbreak it)
@Leo40Git
Copy link
Contributor Author

HALLELUJAH THE MIXIN WORKS (I had to rewrite it entirely to redirect the completeHarvest calls instead)

NeoForge is still nonfunctional, though...

@Jamalam360 Jamalam360 linked an issue Jan 28, 2025 that may be closed by this pull request
@Jamalam360 Jamalam360 mentioned this pull request Jan 29, 2025
@Jamalam360 Jamalam360 closed this Jan 29, 2025
@Jamalam360
Copy link
Member

I know maintainers can somehow push to PRs not owned by them on GitHub, but it was easier to just open a different PR

Thanks for the help!

Jamalam360 added a commit that referenced this pull request Jan 29, 2025
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.

Update to 1.21
2 participants