Jump to content

[SOLVED]HOW DO TEXTURES WORK 1.6.2


d3thdrug

Recommended Posts

A. Don't shout. It hurt my ears...

B. I don't know about block, but for items, put

@SideOnly(Side.CLIENT)

public void registerIcons(IconRegister iconRegister)

{

this.itemIcon = iconRegister.registerIcon("YOUR LOWERCASE MODID HERE:YOUR LOWERCASE ITEM TEXTURE NAME HERE");

}

 

Make sure EVERYTHING including your modid and texture names, are lower case, else nothing will work. That means you should have to change a good amount of stuff if your modid was uppercase... make sure your .png files and all your folders are lowercase as well. Also, in the path to your textures, replace mods (or mod, whatever folder was before the one with your modid) with assets, so it should now look like:

assets/YOUR MODID IN LOWERCASE/textures/items/ALL YOUR ITEM TEXTURES IN LOWERCASE

 

If this helped you, make sure to press the 'thank you' or 'applaud' button!

Creator of Metroid Cubed! Power Suits, Beams, Hypermode and more!

width=174 height=100http://i.imgur.com/ghgWmA3.jpg[/img]

Link to comment
Share on other sites

If you don't want to create a new class for every single Block or Item, do it like this:

 

package mod.classes.basic;

import cpw.mods.fml.common.FMLLog;
import cpw.mods.fml.relauncher.Side;
import cpw.mods.fml.relauncher.SideOnly;
import mod.Main;
import net.minecraft.block.Block;
import net.minecraft.block.material.Material;
import net.minecraft.client.renderer.texture.IconRegister;

public class ModBlock extends Block {

public ModBlock(int par1, Material par2Material) {
	super(par1, par2Material);
}

public ModBlock(int ID){
	super(ID, Material.rock);
}

@Override
@SideOnly(Side.CLIENT)
public void registerIcons(IconRegister iconRegister) {
	this.blockIcon = iconRegister.registerIcon(Main.modID + ":" + (this.getUnlocalizedName().substring(5)));
}

}

 

(For this you need a static variable in your main Class, which contains the modID)

public static final String modID = "your mod ID";

 

To set a Block Texture, you now just use .setUnlocalizedName("PictureNameInLowercaseWithout.png");

You must put the Textures into the following folder:

../forge/mcp/src/minecraft/assets/ModidInLowecase/textures

Subfolders: blocks, items (, models)

 

 

Hope, I could help you.  ;)

 

Link to comment
Share on other sites

Thanks guys for your help, i didn't try it out yet but i know it should work. but how do i set up the texture folder path when i wanna test it out in mcp.. do i put it in the .jar?

 

Put it in mcp>src>minecraft>assets>(lowercase mod ID)>textures>items

Make new folders if they don't exists already.

Link to comment
Share on other sites

Thanks guys for your help, i didn't try it out yet but i know it should work. but how do i set up the texture folder path when i wanna test it out in mcp.. do i put it in the .jar?

 

Put it in mcp>src>minecraft>assets>(lowercase mod ID)>textures>items

Make new folders if they don't exists already.

 

nope not in the minecraft assets. nope nope nope.

just create a package called assets.*moddid*.textures.items and put Item textures in there, similarly for blocks. It hasn't changes at all since 1.5.2, other than "mods" was changes to "assets" so the old tutorials mostly still work.

Link to comment
Share on other sites

nope not in the minecraft assets. nope nope nope.

just create a package called assets.*moddid*.textures.items and put Item textures in there, similarly for blocks. It hasn't changes at all since 1.5.2, other than "mods" was changes to "assets" so the old tutorials mostly still work.

 

Just for future reference, would I put this in my package that I already  have for my mod, or would I make an entirely new package?

Link to comment
Share on other sites

It will be referenced as a resource location, which looks like the following:

private static final ResourceLocation backgroundLocation = new ResourceLocation("modid:path_to_texture_from_assets");

 

so say I had a mod called animals, and I had a crow texture. The path could be assets/animals/textures/entities/crow.png

 

the resource location would look something like:

private static final ResourceLocation crowSkin = new ResourceLocation("animals:textures/entities/crow.png");

 

hope I made that clear enough

Link to comment
Share on other sites

hehe this helped me actuly was wondering why it was so difrent from 1.5.1/1.5.2

i think forge aloud us to use the modId("name") to do a seperate map for the textures so you wont get confuses if you texture are in all of th mc textures :P

 

anny way thx iv updater my mod to 1.6.2 :D hehe

Link to comment
Share on other sites

Here's one of my GUIs you can use as a sample to figure this out. I would much rather you look through that and see if you can tell what is required, than just give you the answers and help you limp along. PLEASE DO NOT COPY AND PASTE CODE WITHOUT UNDERSTANDING IT FULLY, you will only be setting yourself up to fail.

Link to comment
Share on other sites

Can't get textures to work.

 

Here's the code for my simplest block:

 

package fleshwerxx;

import net.minecraft.block.Block;
import net.minecraft.block.material.Material;
import net.minecraft.creativetab.CreativeTabs;
import net.minecraft.client.renderer.texture.IconRegister;

public class BlockOpenEarth extends Block
{
    public BlockOpenEarth(int id)
    {
        super(id, Material.ground);
        this.setCreativeTab(Fleshwerxx.tabFW);
    }

public void registerIcons(IconRegister par1IconRegister)
{
	this.blockIcon = par1IconRegister.registerIcon("fleshwerxx:openearth");
}
}

 

But I can't figure out where to put the textures. I don't use Eclipse btw.

 

I understand why all these resource changes have occurred, but I'm getting rreeeal sick of textures being problematic every time I update my damn mod...

Link to comment
Share on other sites

A. Don't shout. It hurt my ears...

B. I don't know about block, but for items, put

@SideOnly(Side.CLIENT)

public void registerIcons(IconRegister iconRegister)

{

this.itemIcon = iconRegister.registerIcon("YOUR LOWERCASE MODID HERE:YOUR LOWERCASE ITEM TEXTURE NAME HERE");

}

 

Make sure EVERYTHING including your modid and texture names, are lower case, else nothing will work. That means you should have to change a good amount of stuff if your modid was uppercase... make sure your .png files and all your folders are lowercase as well. Also, in the path to your textures, replace mods (or mod, whatever folder was before the one with your modid) with assets, so it should now look like:

assets/YOUR MODID IN LOWERCASE/textures/items/ALL YOUR ITEM TEXTURES IN LOWERCASE

 

If this helped you, make sure to press the 'thank you' or 'applaud' button!

 

 

 

 

Please Help me ive been googling all day and its what they all say im on minecraftforge 1.6.2 and it says void is an invalid for variable registerIcons

Link to comment
Share on other sites

package inventory_Upgrades;

import net.minecraft.block.Block;
import net.minecraft.client.renderer.texture.IconRegister;
import net.minecraft.item.Item;

public class CobaltIngot extends Item {

        public CobaltIngot(int id) {
                super(id);
        
                
                {
                	@SideOnly(Side.CLIENT)
                	public void registerIcons IconRegister iconRegister;
                    this.itemIcon = iconRegister.registerIcon("inven:CobaltIngot");
                	
                }
     }
       
}

Link to comment
Share on other sites

package inventory_Upgrades;

import net.minecraft.block.Block;
import net.minecraft.client.renderer.texture.IconRegister;
import net.minecraft.item.Item;

public class CobaltIngot extends Item {

        public CobaltIngot(int id) {
                super(id);
     }

             @SideOnly(Side.CLIENT)
     public void registerIcons(IconRegister iconRegister) {
                    this.itemIcon = iconRegister.registerIcon("inven:CobaltIngot");
             }
       
}

 

Try that...

I am Mew. The Legendary Psychic. I behave oddly and am always playing practical jokes.

 

I have also found that I really love making extremely long and extremely but sometimes not so descriptive variables. Sort of like what I just did there xD

Link to comment
Share on other sites

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.



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • I'm developing a dimension, but it's kinda resource intensive so some times during player teleporting it lags behind making the player phase down into the void, so im trying to implement some kind of pregeneration to force the game loading a small set of chunks in the are the player will teleport to. Some of the things i've tried like using ServerLevel and ServerChunkCache methods like getChunk() dont actually trigger chunk generation if the chunk isn't already on persistent storage (already generated) or placing tickets, but that doesn't work either. Ideally i should be able to check when the task has ended too. I've peeked around some pregen engines, but they're too complex for my current understanding of the system of which I have just a basic understanding (how ServerLevel ,ServerChunkCache  and ChunkMap work) of. Any tips or other classes I should be looking into to understand how to do this correctly?
    • https://mclo.gs/4UC49Ao
    • Way back in the Forge 1.17 days, work started for adding JPMS (Java Platform Module Support) to ModLauncher and ForgeModLoader. This has been used internally by Forge and some libraries for a while now, but mods (those with mods.toml specifically) have not been able to take advantage of it. As of Forge 1.21.1 and 1.21.3, this is now possible!   What is JPMS and what does it mean for modders? JPMS is the Java Platform Module System, introduced in Java 9. It allows you to define modules, which are collections of packages and resources that can be exported or hidden from other modules. This allows for much more fine-tuned control over visibility, cleaner syntax for service declarations and support for sealed types across packages. For example, you might have a mod with a module called `com.example.mod` that exports `com.example.mod.api` and `com.example.mod.impl` to other mods, but hides `com.example.mod.internal` from them. This would allow you to have a clean API for other mods to use, while keeping your internal implementation details hidden from IDE hints, helping prevent accidental usage of internals that might break without prior notice. This is particularly useful if you'd like to use public records with module-private constructors or partially module-private record components, as you can create a sealed interface that only your record implements, having the interface be exported and the record hidden. It's also nice for declaring and using services, as you'll get compile-time errors from the Java compiler for typos and the like, rather than deferring to runtime errors. In more advanced cases, you can also have public methods that are only accessible to specific other modules -- handy if you want internal interactions between multiple of your own mods.   How do I bypass it? We understand there may be drama in implementing a system that prevents mods from accessing each other's internals when necessary (like when a mod is abandoned or you need to fix a compat issue) -- after all, we are already modding a game that doesn't have explicit support for Java mods yet. We have already thought of this and are offering APIs from day one to selectively bypass module restrictions. Let me be clear: Forge mods are not required to use JPMS. If you don't want to use it, you don't have to. The default behaviour is to have fully open, fully exported automatic modules. In Java, you can use the `Add-Opens` and `Add-Exports` manifest attributes to selectively bypass module restrictions of other mods at launch time, and we've added explicit support for these when loading your Forge mods. At compile-time, you can use existing solutions such as the extra-java-module-info Gradle plugin to deal with non-modular dependencies and add extra opens and exports to other modules. Here's an example on how to make the internal package `com.example.examplemod.internal` open to your mod in your build.gradle: tasks.named('jar', Jar) { manifest { attributes([ 'Add-Opens' : 'com.example.examplemod/com.example.examplemod.internal' 'Specification-Title' : mod_id, 'Specification-Vendor' : mod_authors // (...) ]) } } With the above in your mod's jar manifest, you can now reflectively access the classes inside that internal package. Multiple entries are separated with a space, as per Java's official spec. You can also use Add-Exports to directly call without reflection, however you'd need to use the Gradle plugin mentioned earlier to be able to compile. The syntax for Add-Exports is the same as Add-Opens, and instructions for the compile-time step with the Gradle plugin are detailed later in this post. Remember to prefer the opens and exports keywords inside module-info.java for sources you control. The Add-Opens/Add-Exports attributes are only intended for forcing open other mods.   What else is new with module support? Previously, the runtime module name was always forced to the first mod ID in your `mods.toml` file and all packages were forced fully open and exported. Module names are now distinguished from mod IDs, meaning the module name in your module-info.java can be different from the mod ID in your `mods.toml`. This allows you to have a more descriptive module name that doesn't have to be the same as your mod ID, however we strongly recommend including your mod ID as part of your module name to aid troubleshooting. The `Automatic-Module-Name` manifest attribute is now also honoured, allowing you to specify a module name for your mod without needing to create a `module-info.java` file. This is particularly useful for mods that don't care about JPMS features but want to have a more descriptive module name and easier integration with other mods that do use JPMS.   How do I use it? The first step is to create a `module-info.java` file in your mod's source directory. This file should be in the same package as your main mod class, and should look something like this: open module com.example.examplemod { requires net.minecraftforge.eventbus; requires net.minecraftforge.fmlcore; requires net.minecraftforge.forge; requires net.minecraftforge.javafmlmod; requires net.minecraftforge.mergetool.api; requires org.slf4j; requires logging; } For now, we're leaving the whole module open to reflection, which is a good starting point. When we know we want to close something off, we can remove the open modifier from the module and open or export individual packages instead. Remember that you need to be open to Forge (module name net.minecraftforge.forge), otherwise it can't call your mod's constructor. Next is fixing modules in Gradle. While Forge and Java support modules properly, Gradle does not put automatic modules on the module path by default, meaning that the logging module (from com.mojang:logging) is not found. To fix this, add the Gradle plugin and add a compile-time module definition for that Mojang library: plugins { // (...) id 'org.gradlex.extra-java-module-info' version "1.9" } // (...) extraJavaModuleInfo { failOnMissingModuleInfo = false automaticModule("com.mojang:logging", "logging") } The automatic module override specified in your build.gradle should match the runtime one to avoid errors. You can do the same for any library or mod dependency that is missing either a module-info or explicit Automatic-Module-Name, however be aware that you may need to update your mod once said library adds one. That's all you need to get started with module support in your mods. You can learn more about modules and how to use them at dev.java.
    • Faire la mise à jour grâce à ce lien m'a aider personnellement, merci à @Paint_Ninja. https://www.amd.com/en/support 
    • When I came across the 'Exit Code: I got a 1 error in my Minecraft mods, so I decided to figure out what was wrong. First, I took a look at the logs. In the mods folder (usually where you'd find logs or crash reports), I found the latest.log file or the corresponding crash report. I read it through carefully, looking for any lines with errors or warnings. Then I checked the Minecraft Forge support site, where you can often find info on what causes errors and how to fix them. I then disabled half of my mods and tried running the game. If the error disappeared, it meant that the problem was with the disabled mod. I repeated this several times to find the problem mod.
  • Topics

×
×
  • Create New...

Important Information

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