Update yarn, loader and api #31
Labels
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Steven/fabric-example-mod#31
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "bump-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Significant version bumps since August. I figure this should be updated.
Uh, we actually have a toolchain update and this pr may need to adjust accordingly.
Oh? This configuration builds and runs as-is. Perhaps no other updates are needed yet?
Modmuss backported the parser fix to 0.2.5 so this should be ok
We should just use v2 mappings in the example mod, so need an update to build.gradle
I'm not 100% on what you'd like me to change. Do you mean the loom version?
On my Ubuntu 18.04:
0.2.5 - Works fine.
0.2.6 - Crashes
Failed to locate library: liblwjgl.so
:Humm, 0.2.6 should work just fine? What IDE are you using to run the game? if its vscode or eclipse you need to re-run the setup tasks. For now its still classed as experimetal and there will be a full upgrade guide covering this once im sure its stable enough to be used by the masses.
I did plan on doing the full update to v2 mappings in one commit to this repo to show users how to do it along with the versions.
I use vscode, but this runtime failure occurs IDE-less in the CLI. I've recloned, changed the
5
to6
, run the build/client, and gotten the same issue multiple times:Crash log: crash-2019-11-14_11.42.01-client.txt
I've reproduced within Docker. The
runClient
task crashes with the same error conveniently before attempting to open a Window.I was hoping to just bump the other versions in this PR. Seems best to hold off on the v2 mappings for now? Feel free to just close this PR if you want to handle it later. Thanks!
What are the contents of
<project-dir>/.gradle/loom-cache/launch.cfg
? after running the runClient command?Complete log of a run within Docker: docker-openjdk11-fabric-loom-0.2.6.log Steps to reproduce:
Note: 0.2.5 also crashes within Docker, because there's no display. That is expected though. The error message is different.
Humm yeah, reproduced in docker. Need to fix this before 0.2.6 becomes the main version.
And can reproduce on MacOS
Can you try again now please? Seems to have fixed it on mac os
Works!
It's working in Docker (AKA crashing as expected) with the new snapshot. Was
Fabric Loom: 0.2.6-SNAPSHOT Build(jenkins #19)
, nowFabric Loom: 0.2.6-SNAPSHOT Build(jenkins #20)
. Locally, I had to manually remove the loom jars, since these snapshots don't have version numbers. Usedfind ~/.gradle/ -name "*fabric-loom*" | xargs rm -rf
because I didn't want to clear my entire gradle cache. Should/can Loom build versions be added?please include the build.gradle loom change since loom 0.2.6 works. also another part of build.gradle will need an update
I would rather know https://github.com/FabricMC/fabric-loom/pull/141 and https://github.com/FabricMC/fabric-loom/pull/145 are OK first.
@liach 😆 I forgot the
git add
, before the amend. Fixed. What else needs to be changed?There is a new loader update, and move to v2 mappings then im happy with this.
I've updated to the versions listed on https://modmuss50.me/fabric.html?&version=1.14.4
runClient
works as expected. I'm not sure this means I've set the "v2 mappings" though, because I cannot find documentation explaining the difference and internet searches lead me back to this PR. 😆Pushed V2 and a small tweak to the mod.json to your fork.
This should be good to be merged now.
@13rac1, the best way to stay up to date is joining the discord https://discord.gg/v6v4pMv
@natanfudge Ah ha! Thanks! We need to post elsewhere too, since information on Discord will not necessarily be available in the future. Should the Fabric Latest Versions website be updated too?
Yes, I need to do that.