Minecraft Mod banane ka tarika: Fabric project, Java code aur JAR build tak

Yah guide Minecraft Java Edition 26.2 aur Fabric ke adhar par pehli run par log output karne wala mod banati hai. Yeh ek beginner ka udaharan hai jo us bindu tak follow karta hai jahan mod file loader dwara pehchani jati hai aur aapka likha hua Java code execute hota hai. Bedrock addons, Forge aur NeoForge projects ki sanrachna alag hoti hai, isliye unhe ek hi project mein na milayein.

1. Development Environment ki Taiyari

Fabric ke vartaman 26.2 documentation mein JDK 25 ka sujhav diya gaya hai. Sirf Java runtime environment install karne ke bajaye development ke liye JDK install karein aur IntelliJ IDEA ya VS Code taiyar karein. Terminal mein neeche diye gaye command se actual mein use ho rahe Java ki janch karein. IDE ka Project SDK aur Gradle JVM bhi usi version ko point karna chahiye. 1.21.1 jaise purane versions ke liye, documentation ke upar diye gaye version selection aur generator version ko ek sath badlein aur us version ki JDK requirements ka palan karein.

java -version
javac -version

2. Fabric Generator mein Project Banana

1. Fabric ka official Template Mod Generator kholein.
2. Mod Name mein TroubleMaker Hello, Mod ID mein tmhello, aur Package Name mein com.ascgame.tmhello set karein.
3. Minecraft version ko 26.2 par set karein. Kotlin ya alag data generation jaise advanced options ko pehle udaharan mein add karna anivarya nahi hai.
4. ZIP download karein aur C:/Projects/TMHello jaise simple path mein extract karein. Project folder actual operating system ke anusar tay karein.
5. IDE mein build.gradle ya project root kholein aur Gradle importing poori hone ka intezar karein. Generator dwara tay kiye gaye Loader, Loom aur API versions ko waise hi rakhein.

3. File kya kaam karti hai, ise samjhein

src/main/java common Java code ke liye hai, src/main/resources/fabric.mod.json mod ID, entry class aur dependencies ki ghoshna ke liye hai, aur gradle.properties version aur project settings ke liye hai. Generator ke adhar par client code src/client/java mein alag ho sakta hai. Yah udaharan keval common initialization code ko badalta hai. Kisi bhi setting file ko apni marzi se delete na karein ya internet ki doosri version settings ko overwrite na karein.

4. Apni Initialization Class Likhein

Generated common ModInitializer implementation file ko dhundhein aur ise neeche di gayi sanrachna ke anusar modify karein. Agar aapne filename badal kar TMHello.java kar diya hai, toh package folder aur class name ko bhi match karein. Chunki yah SLF4J logs ka use karta hai, isliye aap game version ke badalne par badalne wali item registration API ke bina initialization ki janch kar sakte hain.

package com.ascgame.tmhello;

import net.fabricmc.api.ModInitializer;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

public class TMHello implements ModInitializer {
    public static final String MOD_ID = "tmhello";
    private static final Logger LOG = LoggerFactory.getLogger(MOD_ID);

    @Override
    public void onInitialize() {
        LOG.info("TroubleMaker: my first Fabric mod is ready.");
    }
}

fabric.mod.json ki baki cheezon ko waise hi rakhte hue check karein ki entrypoints.main upar di gayi class ke poore naam ko point karta hai. Neeche di gayi file poori file nahi hai balki check karne wala hissa hai. Purane mixins ya client settings ko poori tarah se replace na karein.

{
  "entrypoints": {
    "main": ["com.ascgame.tmhello.TMHello"]
  }
}

5. Development Run aur Final File Build

1. Project root se Windows par gradlew.bat runClient aur macOS/Linux par ./gradlew runClient chalayein.
2. Development client console ya run/logs/latest.log mein TroubleMaker phrase ko search karein. Yah ek udaharan hai jo world mein enter hone se pehle initialization ke dauran ek baar output hota hai.
3. Game exit karein aur Windows par gradlew.bat build aur macOS/Linux par ./gradlew build se deployment file banayein.
4. build/libs mein normal distribution JAR check karein. Naam mein sources ya dev jude hue development files ko normal distribution ke roop mein use na karein.
5. Usi Minecraft version ke alag Fabric instance ke mods folder mein JAR dalein. Agar generated dependencies mein Fabric API hai, toh usi version ke anusar install karein.
6. Actual launcher se run karein aur check karein ki instance ke logs/latest.log mein wahi phrase print ho raha hai.

6. Aksar hone wali errors aur recovery

Unsupported class file version ke liye Java version aur entry class loading error ke liye package, class name aur entrypoints ki mismatch ko sabse pehle check karein. Agar mods folder mein dalne par kuch nahi hota, toh check karein ki kya aapne ise kisi doosre launcher instance mein dala hai. Yah udaharan save data add nahi karta, isliye aap game exit karke aur JAR remove karke tulna (compare) kar sakte hain. Iske baad jab aap items ya blocks add karenge, toh target version ka Fabric First Item document padhein aur file path aur registration API ko us version ke anuroop banayein.

7. Share karte samay sath mein di jane wali jankari

Mod ID, supported Minecraft version, Loader aur Fabric API conditions, JDK requirements, udaharan ki suvidhayein aur remove karne ka tarika README mein likhein. Code source aur distribution JAR ko alag rakhein aur game body ya doosre creators ki mod files ko shamil na karein. Pehla version asli normal launcher mein log print hone ki janch karne ke baad 1.0.0 jaise version ke sath distribute karein.

Mool Document aur Janch ke Adhar

Yah TroubleMaker operations team dwara 7 October 2026 ko creator aur official tool documents ki janch karke likhi gayi beginner guide hai. Code aur diagrams spashtikaran ke liye hamare apne udaharan hain aur is server par is game ke actual play ko verify nahi kiya gaya hai. Mool lekh mein nirdisht version ke sath alag test save mein janch karke distribute karein. Tools ke latest versions aur dependencies ki tulna neeche diye gaye mool sources se karein.

Fabric 개발 환경

Fabric 프로젝트 생성

Fabric 모드 빌드

Fabric 공식 생성기