Problem
ModFactory currently documents and implements a Windows-oriented setup, but a fresh clone on macOS cannot reach the documented runClient workflow.
Observed on an Apple Silicon MacBook:
install.bat and tools/setup-minecraft-ai.bat cannot run natively on macOS.
- Asset, validation, QA, and MCP helper scripts are PowerShell-only (
.ps1), while PowerShell is not listed as an explicit macOS bootstrap step.
- The README says
fabric-mod-dev/ contains a working reference implementation, but that directory is not present in the repository.
- The repository contains no
gradlew, Gradle build files, or fabric.mod.json, so ./gradlew runClient cannot be executed after cloning.
- Some documentation and skills contain machine-specific Windows paths such as
D:\MC\fabric-mod-dev.
Expected outcome
A fresh clone on macOS should have a documented and tested path to launch the Minecraft development client.
Suggested scope:
- Add a macOS bootstrap script such as
install.sh.
- Add or generate a minimal runnable Fabric example project, including the Gradle wrapper.
- Provide a macOS command for starting the client:
./gradlew runClient.
- Replace hard-coded Windows paths with project-relative or configurable paths.
- Document Java 21, Node.js, PowerShell, and MCP prerequisites for macOS.
- Add a smoke test or CI check proving the example project builds on macOS/Linux.
Environment
- macOS on Apple Silicon
- Java 21
- Node.js 24 / npm 11
- Git 2.50
Current workaround
A new Fabric project must be created outside this repository before any runClient QA gate can run. This also means the Ruby/Thunder reference implementation described by the README is unavailable from a fresh clone.
Problem
ModFactory currently documents and implements a Windows-oriented setup, but a fresh clone on macOS cannot reach the documented
runClientworkflow.Observed on an Apple Silicon MacBook:
install.batandtools/setup-minecraft-ai.batcannot run natively on macOS..ps1), while PowerShell is not listed as an explicit macOS bootstrap step.fabric-mod-dev/contains a working reference implementation, but that directory is not present in the repository.gradlew, Gradle build files, orfabric.mod.json, so./gradlew runClientcannot be executed after cloning.D:\MC\fabric-mod-dev.Expected outcome
A fresh clone on macOS should have a documented and tested path to launch the Minecraft development client.
Suggested scope:
install.sh../gradlew runClient.Environment
Current workaround
A new Fabric project must be created outside this repository before any
runClientQA gate can run. This also means the Ruby/Thunder reference implementation described by the README is unavailable from a fresh clone.