Jump to content

[1.7.2] Inherited Abstract, getBlockBrightness, setLightValue, etc :(


Recommended Posts

Posted

Okay, this is just a Java thing, not really specific to modding.  You probably need to learn more about Java.  But here is an explanation.

 

You have extended BlockContainer class which (if you look at the source for that class) implements the interface ITileEntityProvider.  But BlockContainer doesn't fully implement that interface, which means that BlockContainer has to be declared as "abstract".  Therefore it is up to your class to finish the implementation of the interface.

 

What you need to do is to follow Eclipse's suggested fix -- if you hover over the red-underlined error part of your code Eclipse will usually suggest a fix.  In this case it should suggest to add the unimplemented methods to your class.  When you do that several methods will be added to the end of your class code, but the bodies of these methods will be empty (except a comment marking these as TODO).

 

You then need to look at each method and put in your code that is relevant to your class.

 

In this case, the only method that needs to be implemented is the createNewTileEntity() method.  So of course in that method you should create and return the tile entity that is appropriate to your container.

 

Hope that makes some sense...

Check out my tutorials here: http://jabelarminecraft.blogspot.com/

Posted

Just to clarify you dont create the tile in that method the tile needs to be its own separate class that extends TileEntity. In that class you simply have to return a new instance of your tile entity e.g.

@Override
public TileEntity createNewTileEntity(World var1, int var2)
{
return new TileEntityCampfireLog();
}

looking at your code it looks like you are missing a variable in your createNewTileEntity method.

 

Whenever you override a method you should add the @Override annotation as shown in example above that will give an error if you do something wrong such as miss a variable. 

I am the author of Draconic Evolution

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.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • "I want to understand how complex mods with ASM transformation and coremods work, such as Xray or AntiXray. Why do they break when you simply rename packages? What features of their architecture make refactoring difficult? And what techniques are used to protect these mods? I am interested in technical aspects in order to better understand the bytecode and Forge loader system."
    • I can't figure out if you're looking for help trying to steal someone elses work, or cheat at the game....
    • Title: Why Is It So Hard to Rename and Restructure Mods Like Xray or AntiXray? 🤔 Post text: Hey everyone! I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice. Here’s the issue: When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward. But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart. Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function. So my question is — why is this so much harder with cheat mods like Xray? Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features? I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing. Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals? Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it. Thanks in advance for any help or discussion. ✌️
    • just started making cinamatic contect check it out on my channel or check out my facebook page    Humbug City Minecraft Youtube https://www.youtube.com/watch?v=v2N6OveKwno https://www.facebook.com/profile.php?id=61575866982337  
    • Where did you get the schematic? Source/Link? And do use an own modpack or a pre-configured from curseforge? If yes, which one On a later time, I can make some tests on my own - but I need the schematic and the modpack name
  • Topics

  • Who's Online (See full list)

    • There are no registered users currently online
×
×
  • Create New...

Important Information

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