-
Notifications
You must be signed in to change notification settings - Fork 12
Description
I have an error when trying to use the mod's 1st person animations, I saw a video that explained how to do it but I get this error
C:\Users\gbrun\OneDrive\Escritorio\Improved-Animations-Release-3-Forge>gradlew build
To honour the JVM settings for this build a single-use Daemon process will be forked. For more on this, please refer to https://docs.gradle.org/8.5/userguide/gradle_daemon.html#sec:disabling_the_daemon in the Gradle documentation.
Daemon will be stopped at the end of the build
Configure project :Common
SpongePowered Vanilla 'GRADLE' Toolset Version '0.2.1-SNAPSHOT'
Found hash mismatch on file at C:\Users\gbrun.gradle\caches\VanillaGradle\v2\manifests\versions\1.20.4.json, re-downloading
Configure project :Common
Targeting Minecraft '1.20.4' on a 'JOINED' platform
Configure project :Fabric
Fabric Loom: 0.12.56
Processing file: minecraft-project-@Fabric-merged-named.jar
Processing file: minecraft-project-@Fabric-merged-named.jar
Processing file: minecraft-project-@Fabric-merged-named.jar
:remapping 53 mods (TinyRemapper, intermediary -> named)
:remapping sources
FAILURE: Build failed with an exception.
- What went wrong:
A problem occurred configuring project ':Forge'.
Could not resolve all files for configuration ':Forge:classpath'.
Could not resolve net.minecraftforge.gradle:ForgeGradle:[6.0.16,6.2).
Required by:
project :Forge
> Failed to list versions for net.minecraftforge.gradle:ForgeGradle.
> Unable to load Maven meta-data from https://maven.minecraftforge.net/net/minecraftforge/gradle/ForgeGradle/maven-metadata.xml.
> Could not HEAD 'https://maven.minecraftforge.net/net/minecraftforge/gradle/ForgeGradle/maven-metadata.xml'.
> Read timed out
- Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
Get more help at https://help.gradle.org.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.5/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 2m 46s