Add clear Forge compatibility information to address user questions#5
Add clear Forge compatibility information to address user questions#5
Conversation
|
@Lyzev 👋 This repository doesn't have Copilot instructions. With Copilot instructions, I can understand the repository better, work faster and produce higher quality PRs. I can generate a .github/copilot-instructions.md file for you automatically. Click here to open a pre-filled issue and assign it to me. I'll write the instructions, and then tag you for review. |
Co-authored-by: Lyzev <69327579+Lyzev@users.noreply.github.com>
|
add mal support dafür auf chillo millo @copilot |
Could you clarify what specific support you'd like me to add? The comment isn't clear about what technical changes are needed. If you're referring to mod loader support, I've already added comprehensive Forge compatibility information in the README. Let me know what specific functionality or documentation you'd like me to add. |
forge as mentioned in the issue and pull request |
I've already added comprehensive Forge compatibility documentation in commit 83c7dd1. The README now clearly explains this is a Fabric-only mod and why Forge isn't supported. Are you asking for actual Forge support implementation? That would require a complete rewrite since this mod uses Fabric-specific features (mixins, fabric-loom, Fabric APIs). Could you clarify if you want documentation improvements or actual Forge support code? |
|
dumm |
This PR addresses the common question about Forge compatibility by adding comprehensive documentation to the README.
The issue arose from users asking "used in forge?" without clear information about mod loader support. This project is built specifically for Fabric using Fabric-specific features like mixins, APIs, and build toolchain (fabric-loom), making it incompatible with Forge or NeoForge.
Changes Made
This documentation helps users quickly understand compatibility requirements and provides clear guidance for those interested in different mod loaders.
Fixes #4.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
maven.fabricmc.net/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED -Xmx1G -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/REDACTED/.gradle/wrapper/dists/gradle-8.14-bin/38aieal9i53h9rfe7vjup95b9/gradle-8.14/lib/gradle-daemon-main-8.14.jar -javaagent:/home/REDACTED/.gradle/wrapper/dists/gradle-8.14-bin/38aieal9i53h9rfe7vjup95b9/gradle-8.14/lib/agents/gradle-instrumentation-agent-8.14.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 8.14(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.