Corrupted workspace with geckolib!

My computer crashed while rebuilding the gradle and now my workspace won't open at all. I've tried replacing the .mcreator file with a backup, and deleting the .classpath file, but still get the same result. Please help! I've been working on this mod for months now.

Executing Gradle task: eclipse
Build info: MCreator 2024.2.32117, forge-1.20.1, 64-bit, 15724 MB, Windows 11, JVM 21.0.3, JAVA_HOME: C:\Program Files\Pylo\MCreator\jdk, started on: 2024-08-07-15:00:08
Loaded APIs: geckolib

> Configure project :
[Fatal Error] geckolib-forge-1.20.1-4.4.2.pom:2:1: Content is not allowed in prolog.
]: ] > Task :downloadMCMeta UP-TO-DATE
> Task :extractNatives UP-TO-DATE
> Task :downloadMcpConfig
> Task :extractSrg UP-TO-DATE
> Task :createSrgToMcp UP-TO-DATE
> Task :downloadAssets UP-TO-DATE
> Task :makeSrcDirs
> Task :prepareRuns
> Task :eclipseClasspath FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':eclipseClasspath'.
> Could not resolve all dependencies for configuration ':compileClasspath'.
> Failed to calculate the value of task ':compileJava' property 'javaCompiler'.
> Cannot find a Java installation on your machine matching this tasks requirements: {languageVersion=17, vendor=any, implementation=vendor-specific} for WINDOWS on x86_64.
> No matching toolchain could be found in the locally installed toolchains or the configured toolchain download repositories. Some toolchain resolvers had provisioning failures: foojay (Unable to download toolchain matching the requirements ({languageVersion=17, vendor=any, implementation=vendor-specific}) from 'https://api.foojay.io/disco/v3.0/ids/ecc5be1e7943d4ad79b234060140a18b/r…', due to: Unexpected lock protocol found in lock file. Expected 3, found 0.).
* Try:
> Learn more about toolchain auto-detection at https://docs.gradle.org/8.8/userguide/toolchains.html#sec:auto_detection.
> Learn more about toolchain repositories at https://docs.gradle.org/8.8/userguide/toolchains.html#sub:download_repo….
> 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.
BUILD FAILED in 15s
8 actionable tasks: 3 executed, 5 up-to-date

BUILD FAILED
Task completed in 15 seconds