Jump to content

Does every single block/item create in our mod have to be a class on its own?


Recommended Posts

Hello forum people.

 

This is my first post, I still use minecraft release 1.5.2, just to be safe when modding, and I'm not that good at Java (I don't like to type that much) and I noticed that for registering textures for items or blocks to be able to be rendered in game, you need to override a method. That's not what minecraft itself does most of the time. Just a few blocks/items have their own classes but just because they have unique logic or they have to override other methods.

 

So there's really no way around this? deriving from a base class for each and every block/item I define in mod, even if it's just a dumb block with a different texture, is the only possible way to have a block/item rendered in game?

Link to comment
Share on other sites

wow... that's a shame. Minecraft seems to locate their textures by block/item unlocalizedName property and then just add ".png" to the end. Sad this is a problem people encounter so early. By the time they've mastered enough skills to solve it more elegantly than by inheritance, I think they just got used to it (i mean the forge developers and the rest of the community).

 

And there's also the strange requirement java has that every class must be define in it's own file... create 50 blocks/items and you have 50 files just for that, plus all the rest of your mod. Really a shame.

 

Edit: after reading your editing on your second post: I really don't think that's it. Although I don't think it would be worthless learning what that particular member does, if you can.

Link to comment
Share on other sites

Unless you declare your Item classes like this:

 

pacakge mypackage.item;

import net.minecraft.item.Item;

public class MyItemClasses {

    public static class ItemMyFirstItem extends Item {

        public ItemMyFirstItem(int par1) {
            super(par1);
        }
    };

    public static class ItemMySecondItem extends Item {

        public ItemMySecondItem(int par1) {
            super(par1);
        }
    };
    // etc., etc., etc..
}

 

Then it's your all your items in one file technically xD

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

You  can actually create items and blocks like that:

public static final Item itemOfYours = new Item(800);
public static final Block blockOfYours = new Block(503, Material.iron).setHardness(1.0F).setResistance(3F);

Check Block and Item classes to see details.

If i helped you, don't forget pressing "Thank You" button. Thanks for your time.

Link to comment
Share on other sites

@Naitenne yes, that would be really great. That's exactly what I wanted to do. But if I do it like that, it seems I have no way to render my blocks/items textures, because forge needs me to override some method to be able to find my textures. And that's only possible by inheritance

 

edit: to make it clearer, I CAN define blocks and items like that. But they won't be properly shown in game. they will appear as a cube (for blocks) or a little square thingy like a white tablet. Both with the words "texture not found" (or something like that) written all over them. So unless there's a way around this, people have to derive from either block or item to be able to override that special method forge needs to find my textures.

 

Link to comment
Share on other sites

Try messing with .setUnlozalizedName("yourMod:textureName") place it like .setResistance(3F). The texture should be located as MCP/src/mods/yourMod/textures/items/textureName.png for items and MCP/src/mods/yourMod/textures/blocks/textureName.png for blocks;

If i helped you, don't forget pressing "Thank You" button. Thanks for your time.

Link to comment
Share on other sites

Try messing with .setUnlozalizedName("yourMod:textureName") place it like .setResistance(3F). The texture should be located as MCP/src/mods/yourMod/textures/items/textureName.png for items and MCP/src/mods/yourMod/textures/blocks/textureName.png for blocks;

Have you tested that and had it work?

 

Because to my knowledge that is the reference to the VANILLA textures folder.

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

I hope it works for you in 1.6.*. Because if it doesn't, your screwed. And I am glad it works. I know that they said that it points there, but I also did say TO MY KNOWLEDGE, basically according to what I knew it pointed to the vanilla textures, not ones in a mod file. Now I have been proven wrong it seems I can update my knowledge :P

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

Mew, how can mods/yourMod/ point at vanilla textures?

 

And once again people aren't reading what I have said correctly...

 

What I was referring to was .setUnlocalizedName(). Before proven otherwise I thought it to be pointing to the Vanilla texture path. That is what I was meaning.

 

 

And as a side note, VERY NICE mod. Good ole' trains. Awesome :D

 

well the forge build for 1.6 may not be the recommended one for a while... but I sure hope it works for 1.6 or I'll start to think Mojang is sabotaging us modders >.<

 

Don't bother waiting for a recommended build of 1.6.1, there will NEVER be one. There is a recommended build for minecraft 1.6.2 though xD

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

.setUnlocalizedName

is for setting the name of your block that goes through the localization files so it can be displayed in the users current language (if provided)

 

for Blocks the function you want is .func_111022_d("yourMod:textureName")

by using it you set field_111026_f

 

registerIcons gets the icon from func_111023_E which in turn reads it from field_111026_f (the one you set)

 

 

Items go through a similar path but you use .func_111206_d("yourMod:textureName")

Link to comment
Share on other sites

.setUnlocalizedName

is for setting the name of your block that goes through the localization files so it can be displayed in the users current language (if provided)

 

for Blocks the function you want is .func_111022_d("yourMod:textureName")

by using it you set field_111026_f

 

registerIcons gets the icon from func_111023_E which in turn reads it from field_111026_f (the one you set)

 

 

Items go through a similar path but you use .func_111206_d("yourMod:textureName")

 

But is that 1.5.2? I don't think so. The OP was asking about this in relation to 1.5.2, but yes this is still relevant when it comes to moving to 1.6.*.

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

;D I missed the 1.5.2 part, noticed the suggestion of using setUnlocalizedName for textures and thought, oh no thats going to cause problems in the future.

 

There has already been several people who have ignored the new functions due to the names, just figured it was happening again :)

Link to comment
Share on other sites

That's not what minecraft itself does most of the time. Just a few blocks/items have their own classes but just because they have unique logic or they have to override other methods.

 

Actually all of Minecraft's blocks have their own class.  Some have overlaps (e.g. colored wool, stairs) some are split when they don't seem like they would need to be (redstone torches,* redstone lamps**).

 

But you're right, a lot of methods that vanilla doesn't override with their block classes ARE overriden by mod classes.

 

Icon registration is one of these, because mod textures are in a different location than vanilla textures.

 

*Two block IDs, same block class file

**Two actually different classes, if I recall correctly.

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

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 
  • Topics

×
×
  • Create New...

Important Information

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