Skip to content

Compatibility Update for ForgeGradle 1.0#1073

Open
zeng-github01 wants to merge 2 commits intoMinecraftForge:FG_1.0from
zeng-github01:FG_1.0-fix
Open

Compatibility Update for ForgeGradle 1.0#1073
zeng-github01 wants to merge 2 commits intoMinecraftForge:FG_1.0from
zeng-github01:FG_1.0-fix

Conversation

@zeng-github01
Copy link
Copy Markdown

@zeng-github01 zeng-github01 commented May 7, 2026

Pull Request: Compatibility Update for ForgeGradle 1.0

Summary

This PR introduces critical compatibility updates for ForgeGradle 1.0. It primarily addresses the asset downloading failures caused by legacy Mojang service deprecation and upgrades the build system to a more stable Gradle version.

Changes

  • Asset Download Fix:
    • Replaced the legacy asset downloading logic with the current Mojang API implementation.
    • This fix is backported and adapted from anatawa12/ForgeGradle-1.2.
  • Gradle Wrapper Upgrade:
    • Updated Gradle from the legacy version to 4.10.
    • This improves build performance and enhances compatibility with Java 8 environments, which is essential for late-stage 1.6.4 development.
  • Build Environment Adjustments:
    • Minor internal task adjustments to ensure compatibility with Gradle 4.10 APIs. (Rewrite by AI)

Reasoning

The original asset download servers used by ForgeGradle 1.0 are no longer functional, leading to "Download Failed" errors during workspace setup. By utilizing the updated Mojang API logic, the development environment for legacy Minecraft versions remains viable. Upgrading to Gradle 4.10 provides better support for modern IDEs and CI/CD pipelines.

Testing Performed

  • Executed ./gradlew clean and successfully ran ./gradlew setupDevWorkspace.
  • Verified that game assets (sounds, icons, etc.) are correctly downloaded to the local cache.
  • Successfully compiled the project using Gradle 4.10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant