update README accordingly

Author: stabu-dev

README.md

@@ -28,7 +28,7 @@ Before diving in, a good understanding of Java and Git is **highly recommended**
 
     *   **`mod.json`:** This file contains your mod's metadata.
         *   `name`: The internal, unique ID for your mod (e.g., `my-awesome-mod`). This is critical and used by Gradle, generators, annotations, tools, and Mindustry itself. **It's highly recommended that your main Java package and related initial `template` folders (like `main/src/template`, `annotations/src/template/annotations`, `tools/src/template/tools`) are renamed to match this value (e.g., if `name` is `my-awesome-mod`, rename the `template` package to `myawesomemod`). This consistency greatly improves clarity, convenience, and compatibility with the template's systems.**
-        *   `displayName`: The user-friendly name shown in Mindustry's mod browser (e.g., `My Awesome Mod`). This also influences the default names of your built JAR files via Gradle.
+        *   `displayName`: The user-friendly name shown in Mindustry's mod browser (e.g., `My Awesome Mod`). This also influences the default names of your built JAR files via Gradle and the artifacts generated by GitHub Actions.
         *   `author`: Your name or your team's name.
         *   `description`: A brief description of your mod.
         *   `version`: Your mod's version (e.g., `1.0.0`).
@@ -45,29 +45,6 @@ Before diving in, a good understanding of Java and Git is **highly recommended**
             *   `annotations/src/template/annotations/...` to `annotations/src/myawesomemod/annotations/...`
             *   `tools/src/template/tools/...` to `tools/src/myawesomemod/tools/...`
             *   Update the `package` declarations within the Java files in these refactored directories.
-    *   **GitHub Actions CI (`.github/workflows/ci.yml`):**
-        *   The Gradle build system will name your JAR files based on `modDisplayName` from `mod.json` (e.g., `MyAwesomeMod.jar`, `MyAwesomeModDesktop.jar`).
-        *   However, the `ci.yml` file has **hardcoded paths and artifact names** that you **must update** to match your mod's `displayName`.
-        *   Specifically, find these sections and update them:
-            *   Under `steps:` for the `Build and Publish Jar` job:
-              ```diff
-              - name: Upload built mod artifact as a GitHub Action artifact
-                # ...
-                with:
-              -   name: Template (in a box)
-              -   path: main/build/libs/Template.jar
-              +   name: YourModDisplayName (in a box) # Or any artifact name you prefer
-              +   path: main/build/libs/YourModDisplayName.jar # Match Gradle output
-              ```
-            *   And for the release:
-              ```diff
-              - name: Upload built mod artifact into release
-                # ...
-                with:
-              -   files: build/libs/Template.jar
-              +   files: build/libs/YourModDisplayName.jar # Match Gradle output for the cross-platform JAR
-              ```
-            Replace `YourModDisplayName` with the value of `modDisplayName` from your `mod.json` (with spaces removed, e.g., if `displayName` is "My Awesome Mod", use `MyAwesomeMod`).
 
     Here's an example of a properly configured mod base, assuming the mod's `displayName` is "My Awesome Mod" and `name` in `mod.json` is `my-awesome-mod`:
 
@@ -207,9 +184,9 @@ This produces a JAR compatible with both Android and PC (e.g., `MyAwesomeMod.jar
 
 *   **Using GitHub Actions (Recommended):**
     *   Push your changes to your GitHub repository.
-    *   The CI workflow (defined in `.github/workflows/ci.yml` and **manually updated by you as described in step 4**) will automatically build both Desktop and Android JARs.
-    *   You can download these from the "Artifacts" section of the completed workflow run. The cross-platform JAR artifact might be named something like `MyAwesomeMod (in a box).zip` (containing `MyAwesomeMod.jar`), depending on how you updated `ci.yml`.
-    *   When you create a GitHub Release, the cross-platform JAR (e.g., `MyAwesomeMod.jar`) is automatically uploaded if you configured `ci.yml` correctly.
+    *   The CI workflow (defined in `.github/workflows/ci.yml`) will automatically build both Desktop and Android JARs using names derived from your `mod.json`.
+    *   You can download these from the "Artifacts" section of the completed workflow run. The cross-platform JAR artifact might be named something like `MyAwesomeMod (in a box).zip` (containing `MyAwesomeMod.jar`).
+    *   When you create a GitHub Release, the cross-platform JAR (e.g., `MyAwesomeMod.jar`) is automatically uploaded.
 
 *   **Local Android Build (Optional):**
     If you need to build for Android locally: