-
Notifications
You must be signed in to change notification settings - Fork 49
Fabric 1.20.4 update #127
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
Fabric 1.20.4 update #127
Conversation
Co-authored-by: Matt Sturgeon <matt@sturgeon.me.uk>
Co-authored-by: Matt Sturgeon <matt@sturgeon.me.uk>
Co-authored-by: Matt Sturgeon <matt@sturgeon.me.uk>
…t.java Co-authored-by: Matt Sturgeon <matt@sturgeon.me.uk>
|
Added changes suggested |
Can confirm it works in production |
|
Added nitpicks |
MattSturgeon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great. Personally, I'd squash all commits into one & then force-push, but idk how picky @hashalite is about keeping commit history clean.
I might post some build artifacts on #125 as idk how long it'll take for @hashalite to see/merge this...
|
Will leave how the commits are for now until hashalite responds then will go from there, easier to squash than unsquash |
|
Here's a prod fabric build: freecam-fabric-1.2.1.1-1.20.4.zip For some reason the forge build is failing in prod with I haven't got time to look into this right now, it may or may not be 1.20.4 specific (could be a bug with #118)... The only changes I've made are to the archive base: MattSturgeon@725ee5d |
|
hmm I managed to load up mc with the forge build and it all worked fine |
|
Just installed the official launcher and tested again. Works fine there. I wasn't hitting an issue with our build, rather LexForge has broken support for unofficial launchers: MinecraftForge/MinecraftForge#9815 |
|
Hello, apologies for the delay in getting back to you. I have been quite busy with exams over the past couple weeks. Thanks for taking the time to update the mod! Don't worry about cleaning up the commit history, I'm not too picky about that. I just want to confirm the issue with the forge build is not on our end before merging. Has anyone had time to look into it further? |
No worries, hopefully they went well 🤞
I've not looked into it much yet. My understanding is there's two separate issues; one effecting the dev env and the other affecting unofficial launchers. I suspect the dev env will be solved by an architectury-loom update or some workaround discussed in they're discord. This shouldn't block doing a release. I believe the unofficial launcher issue has nothing to do with our mod, and (if it's not fixed by launchers yet) would be reproducible even without any mods installed. Again, I haven't confirmed that yet. |
|
Tried installing forge on multimc, just met with an error when attempting to lanch even without any mods. Seems to be a forge related issue rather than a mod one |
|
@hashalite It'd be great to get this merged and/or get a 1.20.4 release out before xmas 😀 🎄 I know I've created a bunch of merge conflicts in other PRs. Let me know if you'd like me to put a branch together with the current conflicts resolved. |
Yup! That's my goal
If it isn't too much trouble, this would be very helpful |
Never mind, it was just a couple of changes |
|
Thanks again you all! |
Compiled well on Fabric. Disabled forge as it would not compile.
Attempted troubleshoot but only have limited experience with forge over fabric.