Jump to content

Recommended Posts

Posted

Other posts on this subject seem to be outdated, as mentioned methods no longer exist.

 

I feel like this should be very simple but I need a background for a slot in a custom GUI. I just can't seem to understand how to add an image file from my mod resources to a sprite location. I know sprites have to be within atlas textures and I elected to stitch it to the atlas blocks PNG which I know is publicly referenced in PlayerContainer. I've gone into a TextureStitchEvent.Pre subscriber method and run

if(!event.getMap().getTextureLocation().equals(PlayerContainer.LOCATION_BLOCKS_TEXTURE)) return;

event.addSprite(new ResourceLocation(MOD_ID,"item/empty_item_slot_sword"));

but, unfortunately, this doesn't seem to add the sprite to the map and I think this is because I never give it the proper file location of the image. Very hard to be sure it doesn't work though but it doesn't appear as a background to the slots in my custom GUI both when I use this.setBackground or override getBackground. I'm not sure where I'm supposed to assign a sprite an image file or even if I need to. Vanilla's way of doing this is a bit tricky to understand and I don't see any of the empty_armor_slot PNGs being referenced anywhere except the LegacyPackWrapper (which maps new IDs to old IDs, probably to help with resource packs).

 

Any help would be very cool :)

Posted
private static final ResourceLocation EMPTY_SWORD_TEXTURE = new ResourceLocation("item/empty_item_slot_sword");
@Override
public Pair<ResourceLocation, ResourceLocation> getBackground() {
    return Pair.of(PlayerContainer.LOCATION_BLOCKS_TEXTURE, EMPTY_SWORD_TEXTURE);
}

This is the relevant code for the background. The class itself extends SlotItemHandler which is a subclass of Slot. Not sure what else I have to do to make it work :(

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I haven't tested it but under https://minecraft.wiki/w/Items_model_definition it says now:   So I guess the resource location must have changed with 1.24.4, which means you need to move your models/item/ to the new source. But as I said I haven't tested this so it also may be that this wont work. Nevertheless give it a try      EDIT (important) So now I tested it and found out how it works   Let the model files (e.g. the .json from blockbench) within "assets/<your_mod_id>/models/item" In addition to that do the following: Every model you added will need a new file under "assets/<your_mod_id>/items" That file is also a JSON and looks like this: { "model": { "type": "minecraft:model", "model": "your_mod_id:item/custom_item" } } - "type" can be minecraft:model, minecraft:composite, minecraft:condition, minecraft:select, minecraft:range_dispatch, minecraft:empty, minecraft:bundle/selected_item or minecraft:special. (In most cases you would need minecraft:model) - "model" is the path to your actual model for this item. For example the value above would point to "assets/your_mod_id/models/item/custom_item"
    • On version 1.20.1 there is a build with the AE2 mod, and when opening the reference book for this mod inside Minecraft, it just freezes and closes
    • public ExampleMod(FMLJavaModLoadingContext context) { var modEventBus = context.getModEventBus(); } Refer to the javadocs and MDK for more pointers and examples.
    • Does it work without Cobblemon GTS?
    • I recently updated my mod from 1.21 to 1.21.4. Didn't change anything on the data generation code (even though methods are now marked as deprecated) and had to change the block and item registration to explicitly add the id to avoid the "null pointer exception no id supplied" error The problem is that the block models work fine, as they did before, textures and all, but not the item ones. Is it because of this registration change? Did something in the datapack structure change on minecraft itself?   Here is one of the registration lines im using as reference:   RegistryObject<Item> CUSTOMITEM = ITEMS.register("item", () -> new RawMaterial(new Item.Properties().useItemDescriptionPrefix().setId(ResourceKey.create(Registries.ITEM, ResourceLocation.fromNamespaceAndPath(MOD_ID, "item"))))));   and same for blocks:   private static <T extends Block> RegistryObject<Item> registerBlockItem(String name, RegistryObject<T> block) {     //T is the block type. It will register the block and the block item.     return ModItems.ITEMS.register(name, () -> new BlockItem(block.get(), new Item.Properties().useBlockDescriptionPrefix().setId(ResourceKey.create(Registries.ITEM, ResourceLocation.fromNamespaceAndPath(MOD_ID, name))))); } RegistryObject<Block> CUSTOMORE = registerBlock("ore", () -> new CustomOre(Block.Properties.ofFullCopy(Blocks.STONE).setId(ResourceKey.create(Registries.BLOCK, ResourceLocation.fromNamespaceAndPath(MOD_ID,"ore"))))));   Note that this made the translation keys i had pre 1.21.4 correctly show the translatable component, so im guessing that is okay, but just in case.  
  • Topics

×
×
  • Create New...

Important Information

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