Jump to content

UN-TEXTURED UN-NAMED BLOCK. SIMPLE QUESTION?


Cookie160

Recommended Posts

After watching multiple outdated videos on making blocks, I managed to get myself and un-textured unnamed block. When I try using the updated format, it crashes with NullPointerException (I know what that means) despite the fact that almost nothing changed. I was wondering if someone could tell me the proper way to have the "int id, int texture, Material" thing in 1.6.4. I presume this isn't too complicatated, but is yet too much for a noob like me :P

Thank you

Link to comment
Share on other sites

public class BlockCompressedCobblestone extends Block{

public BlockCompressedCobblestone(int id, Material par2Material) {
	super(id, par2Material);
	this.setCreativeTab(furniturecraft.FCTab);
}
@SideOnly(Side.CLIENT)
public void registerIcons(IconRegister icon){
	this.blockIcon = icon.registerIcon(furniturecraft.modid + ":" + "CompressedCobblestone");
}
}

That is my block code for my mod, and it is 1.6.4, and...

public Block setBlockName(String string) {
    // TODO Auto-generated method stub
    return null;
}

...indeed, it should not be there.

 

Did I help? Gimme a thanks!

Link to comment
Share on other sites

This is for 1.6.4? Then, first off...

public void gameRegisters(){
                        GameRegistry.registerBlock(snowstormBlock);}    

                public void LanguageRegistry(){
                        LanguageRegistry.addName(snowstormBlock, "Blanket");
}

First, get rid of the "public void LanguageRegistry", "public void gameRegistry", "gameRegisters();", and the "languageRegisters();" but keep the "LanguageRegistry.addName(snowstormBlock, "Blanket");" and the

"GameRegistry.registerBlock(snowstormBlock);" there. Second, also in your main class file, "@Init" should be "@EventHandler" And third...

public BlockSnowstormBlock(int id, int texture, Material mat) {
                super(texture, Material.cloth);
                this.setCreativeTab(CreativeTabs.tabBlock);

Change that to...

public BlockSnowstormBlock(int id, int texture, Material mat) {
                super(id, texture, Material.cloth);
                this.setCreativeTab(CreativeTabs.tabBlock);

Hope I helped

Did I help? Gimme a thanks!

Link to comment
Share on other sites

I figured it out(I hope)! Change this...

public BlockSnowstormBlock(int id, int texture, Material mat) {
                super(id, texture, Material.cloth);
                this.setCreativeTab(CreativeTabs.tabBlock);

To this!

public BlockSnowstormBlock(int id, int texture, Material mat) {
                super(id, texture, mat);
                this.setCreativeTab(CreativeTabs.tabBlock);

That should fix it...

EDIT: Wait, you should remove the "int texture" and the "texture" inside the "super(id, texture, mat);"

Should be like

public BlockSnowstormBlock(int id, Material mat) {
                super(id, mat);
                this.setCreativeTab(CreativeTabs.tabBlock);

You can register textures like

@SideOnly(Side.CLIENT)
public void registerIcons(IconRegister icon){
	this.blockIcon = icon.registerIcon(YourModHere.modid + ":" + "YourBlocksTextureFileNameHere");
}

Did I help? Gimme a thanks!

Link to comment
Share on other sites

Lets see... you do have a problem here...

 public void registerIcons(IconRegister icon);{

Remove the ";"

And if THAT doesn't work, then I think I know why. I am familiar with forge 916, which is what I use, but you are using 953.

EDIT: Almost forgot,

public static final String modid = "Snowstorm";

Put that in your main mod file. Also in your main mod file,

Block snowstormBlock;

Should be

public static Block snowstormBlock;

But once again, we are using different forge versions, so I am unsure

 

Did I help? Gimme a thanks!

Link to comment
Share on other sites

So, after applying your suggestions, I fooled around with the code, and got it down to one problem.

 

Error:

 

Caused by: java.lang.Error: Unresolved compilation problems:

2014-01-03 11:06:22 [iNFO] [sTDOUT] Syntax error on token "registerIcon", VariableDeclarator expected after this token

2014-01-03 11:06:22 [iNFO] [sTDOUT] registerIcon cannot be resolved to a type

2014-01-03 11:06:22 [iNFO] [sTDOUT] Illegal modifier for parameter $missing$; only final is permitted

2014-01-03 11:06:22 [iNFO] [sTDOUT]

 

 

Changed Code:

 

package snowstorm;

 

import cpw.mods.fml.common.Mod.Init;

import cpw.mods.fml.relauncher.Side;

import cpw.mods.fml.relauncher.SideOnly;

import net.minecraft.block.Block;

import net.minecraft.block.material.Material;

import net.minecraft.client.renderer.texture.IconRegister;

import net.minecraft.creativetab.CreativeTabs;

import net.minecraft.util.Icon;

import snowstorm.Snowstorm;

import snowstorm.ClientProxySnowstorm;

 

 

public class BlockSnowstormBlock<registerIcons> extends Block{

     

        public BlockSnowstormBlock(int id, Material mat) {

        super(id, mat);

        this.setCreativeTab(CreativeTabs.tabBlock);

       

       

 

public registerIcon;IconRegister icon;{

                this.blockIcon = icon.registerIcon("Snowstorm:blanket");

 

        }

       

        }

 

        }

 

Thanks!

Link to comment
Share on other sites

public registerIcon;IconRegister icon;{

                this.blockIcon = icon.registerIcon("Snowstorm:blanket");

 

 

@Override

public void registerIcons(IconRegister icon)

{

    this.blockIcon = icon.registerIcon("snowstorm:blanket");

}

 

Should have come up with an error in eclipse...

Link to comment
Share on other sites

The following should work

 

public class BlockSnowstormBlock extends Block{
       
        public BlockSnowstormBlock(int id, Material mat) {
        super(id, mat);
        this.setCreativeTab(CreativeTabs.tabBlock);
       }
       
      
      public registerIcon (IconRegister icon){
                this.blockIcon = icon.registerIcon("Snowstorm:blanket");
        }
}

Link to comment
Share on other sites

Change your registers to:

 

	GameRegistry.registerBlock(snowstormBlock, "snowstormBlock");
	LanguageRegistry.addName(snowstormBlock, "Blanket");

 

You should also give the block a unlocalized name

 

public BlockSnowstormBlock(int id, Material mat) {
        super(id, mat);
        this.setCreativeTab(CreativeTabs.tabBlock);
        this.setUnlocalizedName("snowtormBlock");
       }

Link to comment
Share on other sites

Change your registers to:

 

	GameRegistry.registerBlock(snowstormBlock, "snowstormBlock");
	LanguageRegistry.addName(snowstormBlock, "Blanket");

 

You should also give the block a unlocalized name

 

public BlockSnowstormBlock(int id, Material mat) {
        super(id, mat);
        this.setCreativeTab(CreativeTabs.tabBlock);
        this.setUnlocalizedName("snowtormBlock");
       }

Yeah, that should work... But if it doesn't, then idk the problem.

Did I help? Gimme a thanks!

Link to comment
Share on other sites

Change your registers to:

 

	GameRegistry.registerBlock(snowstormBlock, "snowstormBlock");
	LanguageRegistry.addName(snowstormBlock, "Blanket");

 

You should also give the block a unlocalized name

 

public BlockSnowstormBlock(int id, Material mat) {
        super(id, mat);
        this.setCreativeTab(CreativeTabs.tabBlock);
        this.setUnlocalizedName("snowtormBlock");
       }

Haha!!! It works!!! One last thing, though, is that it doesn't show up in the creative menu, I have to use /give Player*** 500. Thank you sooooooooo much for all of everyone's support!

 

Current code:

 

 

package snowstorm;

import cpw.mods.fml.common.Mod.Init;
import cpw.mods.fml.common.registry.GameRegistry;
import cpw.mods.fml.common.registry.LanguageRegistry;
import cpw.mods.fml.relauncher.Side;
import cpw.mods.fml.relauncher.SideOnly;
import net.minecraft.block.Block;
import net.minecraft.block.material.Material;
import net.minecraft.client.renderer.texture.IconRegister;
import net.minecraft.creativetab.CreativeTabs;
import net.minecraft.util.Icon;
import snowstorm.Snowstorm;
import snowstorm.ClientProxySnowstorm;


@BlockSnowstormBlock({id, Material, {
    this,(id. mat)
    this.setCreativeTab(CreativeTabs.tabBlock)
    this.setUnlocalizedName("blanket")
   
  
public class BlockSnowstormBlock (IconRegister)
            thisblockIcon =icon.registerIcon("Snowstorm:blanket")
            

 

 

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.