Closed ClementRomac closed 5 years ago
Currently the maven repo that Gradle (java package manger) uses for MinecraftForge (the mod of minecraft which decompiles it and lets malmo use deobfuscated game code) is down.
This is not a Malmo issue and it effects the whole Minecraft modding community. This is currently being fixed:
http://www.minecraftforge.net/forum/topic/68782-1122-setupdecompworkspace-no-such-version/
In the mean time, I'll look into making a gradle script which skips rebuilding each time you run your client.
If you're desperate to run Malmo rn, one fix that works for our team is the following:
~/.minecraft
, on mac and windows its hidden in some shitty ApplicationData
folder or something like this), mods
sub folder (on linux this will be ~/.minecraft/mods
), <path to ur malmo repo>/Minecraft/build/libs/MalmoMod-<ur version bro>.jar
) and put it in your <path to ur minecraft folder specified by the launch profile u just made folder>/mods
folder.Now every time u want to use malmo u can launch Minecraft with that launch profile and malmo will automatically load. It should be on port 10000
unless that port is already taken in which it will be 10000 + n
where 10000 + (n-1)
is taken. After Minecraft is launched you can now run whaterver python
script or (C++) script u normally do which references MalmoPython
(or if ur downstream, maybe gym_minecraft
) and it will use the minecraft client u just launched.
Hope this helps dawg.
// IJCAI deadline here we come!!!!!!!1
Update (Solution): See https://github.com/Microsoft/malmo/issues/795#issuecomment-464209772
Pinging ms folks so they know @AndKram
In the mean time, I'll look into making a gradle script which skips rebuilding each time you run your client.
It would be great not having to build each time we run client, also thanks for info!
https://github.com/MinecraftForge/MinecraftForge/issues/5477#issuecomment-464195569 For information on this issue and an updated comment with how to fix issues.
Deleting the gradle cache for ForgeGradle is also an option, but that will require users to find their cache folder and delete something, not entirely user friendly. But new users shouldn't have a problem, just those with the old version still cached.
Yep! So here is what is up: If your Malmo installation suddenly stopped working one day read this.
People over at MinecraftForge updated a certain file used by the ./launchClient.sh(bat)
script for building (and launching) the Malmo mod that caused a certain dependency (ForgeGradle) to no longer be found. This causes your launchClient
script to fail, without fail.
Since then, MinecraftForge has fixed the dependency (ForgeGradle) to no longer rely on this file. However your current instillation is caching and older version of the dependency (ForgeGradle) that your Malmo Mod has been using for months now!
To get it to use the newer non-breaking version you'll need to get your hands dirty. Run the following in your Malmo's /Minecraft
folder.
./gradlew setupDecompWorkspace --refresh-dependencies
./gradlew runClient
good luck dawgs
Hi,
It works thank you very much !
Hi,
I've been using Malmo (0.34) for more than a month now, and suddenly this morning I get a build failed error when I run the launchClient.bat:
I tried on another computer where Malmo was running yesterday and I have the same error. Both my computers are running Windows 10 and have Java 1.8.0_201 installed.
Do you have any idea where that could come from ? Thanks