Jump to content

Name and texture of the item I added in Minecraft Mod is not resolved - 1.15.2 - IntellJ IDE


Recommended Posts

Posted

i am not working on a mod. (I have just started) there is no problem with the code, but when I add an item to the game, the name appears as (item.mtools.example_item) and the Texture appears as black purple squares. I rewrote the codes 15 times but the game does not accept it (texture size is 16x16) please who knows the solution can I write it urgently

Posted
Danebi 17 saat önce demiş ki:

Json'larınızı ve konumlarını gösterin.

Lang ; 

 

{
  "item.mtools.ruby": "Ruby"
}

mTools.java

package com.maces.mtools;

import com.maces.mtools.util.RegistryHandler;
import net.minecraftforge.common.MinecraftForge;
import net.minecraftforge.fml.common.Mod;
import net.minecraftforge.fml.event.lifecycle.FMLClientSetupEvent;
import net.minecraftforge.fml.event.lifecycle.FMLCommonSetupEvent;
import net.minecraftforge.fml.javafmlmod.FMLJavaModLoadingContext;
import org.apache.logging.log4j.LogManager;
import org.apache.logging.log4j.Logger;


@Mod("mtools")
public class mTools
{
    private static final Logger LOGGER = LogManager.getLogger();
    public static String MOD_ID = "mtools";
    mTools instance;


    public mTools() {

        FMLJavaModLoadingContext.get().getModEventBus().addListener(this::setup);
        FMLJavaModLoadingContext.get().getModEventBus().addListener(this::doClientStuff);

        RegistryHandler.init();
        instance = this;
        MinecraftForge.EVENT_BUS.register(this);
    }

    private void setup(final FMLCommonSetupEvent event)
    {

    }

    private void doClientStuff(final FMLClientSetupEvent event)
    {

    }
}

İtemBase.java

package com.maces.mtools.items;

import net.minecraft.item.Item;
import net.minecraft.item.ItemGroup;


public class ItemBase extends Item
{
    public ItemBase() {
        super(new Item.Properties().group(ItemGroup.MISC).maxStackSize(10));
    }
}

RegistryHandler.java

package com.maces.mtools.util;


import com.maces.mtools.items.ItemBase;
import com.maces.mtools.mTools;
import net.minecraft.item.Item;
import net.minecraftforge.fml.RegistryObject;
import net.minecraftforge.fml.javafmlmod.FMLJavaModLoadingContext;
import net.minecraftforge.registries.DeferredRegister;
import net.minecraftforge.registries.ForgeRegistries;


public class RegistryHandler
{
    public static final DeferredRegister<Item> ITEMS = new DeferredRegister<>(ForgeRegistries.ITEMS, mTools.MOD_ID);

    public static void init()
    {
        ITEMS.register(FMLJavaModLoadingContext.get().getModEventBus());
    }


    // Items
    public static final RegistryObject<Item> RUBY = ITEMS.register("ruby", ItemBase::new);


}

 

Ruby.json

{
  "parent": "items/generated",
  "textures": {
      "layer0": "mtools:items/ruby"
  }
}

 

Posted (edited)
18 hours ago, Danebi said:

Show your jsons and their positions.

 

File Locations ; 

mTools.java = main / com.maces.mtools / mTools.java

RegistryHandler.java = main / com.maces.mtools / RegistryHandler.java

en_us.json = main / resources / assest.mtools / lang / en_us.json

ruby.json = main / resources / models / items / ruby.json

ruby.png = main / resources / textures / items / ruby.png ( 16x16 Pixel Size )

 

Edited by Maces Games STUDİOS
Posted
4 minutes ago, Maces Games STUDİOS said:

assest

It should be 'assets'

5 minutes ago, Maces Games STUDİOS said:

ruby.json = main / resources / models / items / ruby.json

Did you forgot to write the 'assets' folder or you placed it in the wrong folder?

6 minutes ago, Maces Games STUDİOS said:

ruby.png = main / resources / textures / items / pubg.png ( 16x16 Pixel Size )

Same.

 

Posted

Also,

10 minutes ago, Maces Games STUDİOS said:

main / resources / assest.mtools / lang / en_us.json

do you have a folder named assets.mtools or you have a folder named mtools inside of assets?

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • When I first heard about Bitcoin back in 2018, I was skeptical. The idea of a decentralized, digital currency seemed too good to be true. But I was intrigued as I learned more about the technology behind it and its potential. I started small, investing just a few hundred dollars, dipping my toes into the cryptocurrency waters. At first, it was exhilarating to watch the value of my investment grow exponentially. I felt like I was part of the future, an early adopter of this revolutionary new asset. But that euphoria was short-lived. One day, I logged into my digital wallet only to find it empty - my Bitcoin had vanished without a trace. It turned out that the online exchange I had trusted had been hacked, and my funds were stolen. I was devastated, both financially and emotionally. All the potential I had seen in Bitcoin was tainted by the harsh reality that with decentralization came a lack of regulation and oversight. My hard-earned money was gone, lost to the ether of the digital world. This experience taught me a painful lesson about the price of trust in the uncharted territory of cryptocurrency. While the technology holds incredible promise, the risks can be catastrophic if you don't approach it with extreme caution. My Bitcoin investment gamble had failed, and I was left to pick up the pieces, wiser but poorer for having placed my faith in the wrong hands. My sincere appreciation goes to MUYERN TRUST HACKER. You are my hero in recovering my lost funds. Send a direct m a i l ( muyerntrusted ( @ ) mail-me ( . )c o m ) or message on whats app : + 1 ( 4-4-0 ) ( 3 -3 -5 ) ( 0-2-0-5 )
    • You could try posting a log (if there is no log at all, it may be the launcher you are using, the FAQ may have info on how to enable the log) as described in the FAQ, however this will probably need to be reported to/remedied by the mod author.
    • So me and a couple of friends are playing with a shitpost mod pack and one of the mods in the pack is corail tombstone and for some reason there is a problem with it, where on death to fire the player will get kicked out of the server and the tombstone will not spawn basically deleting an entire inventory, it doesn't matter what type of fire it is, whether it's from vanilla fire/lava, or from modded fire like ice&fire/lycanites and it's common enough to where everyone on the server has experienced at least once or twice and it doesn't give any crash log. a solution to this would be much appreciated thank you!
    • It is 1.12.2 - I have no idea if there is a 1.12 pack
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.