Jump to content

Textures and LanguageRegistry in preInit instead of Init


sorash67

Recommended Posts

  • Replies 93
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

that is odd! pm me and explain exactly what you did and how your files and the code look like and i will try to help you! :)

 

-sorash67 || Skorpio

Who is this directed to?

 

my bad, it was directed to the ones with texture problems!

 

-sorash67 || Skorpio

Link to comment
Share on other sites

Icon and textures on the wiki.

 

Funny.  Because I updated that tutorial for 1.5 and I can't get my existing code to work with 1.6

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Icon and textures on the wiki.

 

Funny.  Because I updated that tutorial for 1.5 and I can't get my existing code to work with 1.6

 

 

Make sure the names for your image's folder is lowercase in the directory and code. Worked for me

Link to comment
Share on other sites

Icon and textures on the wiki.

 

Funny.  Because I updated that tutorial for 1.5 and I can't get my existing code to work with 1.6

 

 

Make sure the names for your image's folder is lowercase in the directory and code. Worked for me

 

Did.  No dice.

 

2013-07-03 10:08:21 [sEVERE] [Minecraft-Client] Using missing texture, unable to load: traps:textures/blocks/iron_spikes.png

 

File is at:

mcp\src\minecraft\assets\traps\textures\blocks\iron_spikes.png

 

Register function:

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

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Icon and textures on the wiki.

 

Funny.  Because I updated that tutorial for 1.5 and I can't get my existing code to work with 1.6

 

 

Make sure the names for your image's folder is lowercase in the directory and code. Worked for me

 

Did.  No dice.

 

2013-07-03 10:08:21 [sEVERE] [Minecraft-Client] Using missing texture, unable to load: traps:textures/blocks/iron_spikes.png

 

File is at:

mcp\src\minecraft\assets\traps\textures\blocks\iron_spikes.png

 

Register function:

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

 

are you putting the .func111022_d() when you declare your block as well as this?

 

-sorash67 || Skorpio

Link to comment
Share on other sites

are you putting the .func111022_d() when you declare your block as well as this?

 

Good sir, this function has not been mentioned in any thread related to this topic.

 

How have you come to this conclusion and why has it not been mentioned heretofore?

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Everything worked for me!

 

 

My textures are in

 

MCP/src/minecraft/assets/{modid}/textures/items|blocks/.png files

 

The code i use

 

public void registerIcons(IconRegister iconRegister) {

 

itemIcon = iconRegister.registerIcon("modid:Texture");

 

}

 

 

I found that if you use Par1iconRegister it will not register the textures directory and will give you an error!

 

 

I am not putting anything inside the jar!

Check Out My Modding Tutorials For Minecraft Forge!

 

http://www.youtube.com/user/XxxXEclipse7XxxX

 

 

Check Out My Forums -

http://www.theaustralianmodder.com

Link to comment
Share on other sites

public void registerIcons(IconRegister iconRegister) {

 

itemIcon = iconRegister.registerIcon("modid:Texture");

 

}

 

I found that if you use Par1iconRegister it will not register the textures directory and will give you an error!

 

Duh.  Par1iconRegister isn't defined.  It shouldn't even compile.

 

However, it is defined here:

 

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

 

PRO-TIP: changing your variable names doesn't effect jack didly squat!

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

are you putting the .func111022_d() when you declare your block as well as this?

 

Good sir, this function has not been mentioned in any thread related to this topic.

 

How have you come to this conclusion and why has it not been mentioned heretofore?

 

i mentioned this because this is what minecraft uses to get the textures. and maybe if you looked at the changelog, you'd see that Lex made this function public rather than protected.

 

-sorash67 || Skorpio

Link to comment
Share on other sites

i mentioned this because this is what minecraft uses to get the textures. and maybe if you looked at the changelog, you'd see that Lex made this function public rather than protected.

 

You also haven't told me:

 

1) where I need to put this function

2) spelled it right (deobfuscated function names are func_[number] not func[number])

3) told me what class it is a part of

4) where to find an example

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

try looking in Block.class and you can find as many examples as you want! however Lex never said that this function is needed to put in for the textures to work!

 

and yes, people make mistakes, i forgot the "_".

 

-sorash67 || Skorpio

Link to comment
Share on other sites

I have my textures working in 758, and I don't have func_111022 in my block declaration. I simply put the textures where lex said to, then changed the declarations to preInitialization, as well as updating the registerIcon functions.

If you really want help, give that modder a thank you.

 

Modders LOVE thank yous.

Link to comment
Share on other sites

I have my textures working in 758, and I don't have func_111022 in my block declaration. I simply put the textures where lex said to, then changed the declarations to preInitialization, as well as updating the registerIcon functions.

 

pretty much what i did! but i didnt have to change anything in the icon registering!

 

-sorash67 || Skorpio

Link to comment
Share on other sites

try looking in Block.class and you can find as many examples as you want!

 

Finally.

 

Took a look.

 

No dice.

 

I have my textures working in 758, and I don't have func_111022 in my block declaration. I simply put the textures where lex said to, then changed the declarations to preInitialization, as well as updating the registerIcon functions.

 

I put my textures where Lex has said to and changed EVERYTHING to go in pre init.

 

No luck.

 

What's this "update to registerIcon function" change?

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

Also, when I put my language registry in the pre-unit I get an error that I can't use language registry in pre-init

 

you're probably putting languageregistry before you declare your block!

 

So far this topic has been no help at all because we are not get the full code changes to get textures working.

 

this topic was made to gather help and find the right code to solve the problem, not provide you with it.

 

-sorash67 || Skorpio

Link to comment
Share on other sites

Nothing, actually. I thought I did change something, but I can't find it after comparing my 1.5.2 code with 758. Also, put everything in preInit, but remember that preInit is no longer called that. Instead, it should be:

@EventHandler
public void load(FMLPreInitializationEvent event) {}

It is still the FMLPreInitializationEvent, but this goes inside @EventHandler.

If you really want help, give that modder a thank you.

 

Modders LOVE thank yous.

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

    • rp.crazyheal.xyz mods  
    • 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 
  • Topics

×
×
  • Create New...

Important Information

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