Dev (#12)

* Remove Alloy Recipes: invar electrum rose-gold osmium
Remove Materials Melting Recipes: Aluminium Tungsten Osmium Platinum

* Remove steel and platinum byproducts from melting recipes

* Align casting recipes with GregTech material logic

- Plate: 1 ingot -> 1.5 ingots
- Gear: 4 ingots -> 6 ingots
- Rod: 0.5 ingots -> 0.75 ingots

* vacuum_freeze recipe & gear fluid value changed

* add GTConstructRecipeType and refactor GTConstructRecipes

* feat: add GTConstructRecipeType and refactor GTConstructRecipes

* disable Platinum VacuumFreezer recipe

* Update README.md

* Update README.md

* Enable enhanced class redefinition and set network timeout

* Update gradle.yml

Author: mmyddd

.github/workflows/gradle.yml

@@ -6,18 +6,18 @@ on:
 #  pull_request:
 #    branches: ["main"]
   workflow_dispatch:
+
 jobs:
   build:
     runs-on: ubuntu-latest
 
     steps:
     - uses: actions/checkout@v4
 
-    - name: Set up JDK
-      uses: actions/setup-java@v4
+    - name: Set up JetBrains Runtime (JBR)
+      uses: DeLaGuardo/setup-jbr@v1
       with:
-        distribution: 'temurin'
-        java-version: '17'  # 根据你的Mod需求调整Java版本
+        jbr-version: '17'
 
     - name: Grant execute permission for gradlew
       run: chmod +x gradlew

README.md

@@ -13,11 +13,17 @@ For documentation on writing addons or working with Tinkers' Consrtuct datapacks
 
 ## Setting up a Workspace/Compiling from Source
 
-Note: Git MUST be installed and in the system path to use our scripts.
-* Setup: Import Tinkers' Construct as a Gradle project into IDEA. Let it run setup.
-* Run: Run the `gradlew genIntellijRuns` through IDEA.
-* Build: Run `gradlew build`.
-* If obscure Gradle issues are found try running `gradlew clean` and `gradlew cleanCache`
+
+- Java 17
+- JetBrains Runtime (JBR) is mandatory. You must configure IntelliJ IDEA to use the bundled JBR (version 17 or newer) for the Gradle JVM. This can be set in `Settings > Build, Execution, Deployment > Build Tools > Gradle > Gradle JVM`.
+
+The project uses a modern Forge plugin to define run configurations directly in `build.gradle`. These are imported into your IDE by running the `genIntellijRuns` Gradle task.
+
+- **`client`**: Launches the Minecraft client for testing mod features, UI, and gameplay.
+- **`server`**: Launches a dedicated, no-GUI server instance for testing server-side logic and commands.
+- **`data`**: Runs the data generator. It scans your code for data providers and automatically generates resource files like recipes, models, and loot tables into the `src/generated/resources/` directory.
+
+To build the project, execute `gradlew build`. For troubleshooting Gradle issues, use `gradlew clean` and `gradlew cleanCache`. The build script is configured to skip tests to resolve plugin compatibility problems.
 
 ## Issue reporting
 Please include the following:

build.gradle

@@ -49,7 +49,8 @@ legacyForge {
             // "REGISTRIES": For firing of registry events.
             // "REGISTRYDUMP": For getting the contents of all registries.
             systemProperty 'forge.logging.markers', 'REGISTRIES'
-            //jvmArgument("-XX:+AllowEnhancedClassRedefinition")
+            jvmArgument("-XX:+AllowEnhancedClassRedefinition")
+            jvmArgument("-DnetworkTimeout=6000000")
             // Recommended logging level for the console
             // You can set various levels here.
             // Please read: https://stackoverflow.com/questions/2031163/when-to-use-the-different-log-levels