[1.7.10][SOLVED] setFireInfo using Deprecated functions?

[weckar]

Hi there,

I was just trying to make a wood variant, and wanted to have it be burnable.

By the new standards, I went and used Blocks.fire.setFireInfo.

Unfortunately, rather than making an instance of FireInfo, it tries to use the getIdFromBlock array approach (which is even indicated as deprecated, but there is no check to skip to the newer implementation).

Because of this, I get an ArrayIndexOutOfBounds as the getIdFromBlock of course returns -1.

Am I just overlooking some detail here? All help is appreciated.

[weckar]

You mean through GameRegistry.registerBlock? I do that... Unless I'm also supposed to register it elsewhere?

[weckar]

THAT.... is an awfully good point. A post-registration init method instead of the constructor.

 

I feel silly now...

 

Thanks!

[Draco18s]

THAT.... is an awfully good point. A post-registration init method instead of the constructor.

 

Or you could call the fire info in your main mod class....

[weckar]

I prefer to keep things encapsulated where they belong as much as possible. Thanks for the idea though.

[jeffryfisher]

THAT.... is an awfully good point. A post-registration init method instead of the constructor.

Or you could try it from the block's constructor after the constructor calls registration. I recommend leaving a comment on the call to explain the necessity of the ordering.

[weckar]

Possible. Centralized registration does allow for easier referencing later, I find. It's a balancing act, to be sure...

[jeffryfisher]

Maybe centralized declaration could get you the easy referencing while self-registration can still fit into encapsulation... and allow some classes to perform registration before finishing construction. But I suppose each modder's structure is a matter of taste and what's comfortable.