Static method registers and creates Item a bad idea?

[NecroTheif]

I was told that it was a bad idea to create a method like this in a class FakeIce that extends Item class and then call this method in the main class. Why would that be a bad idea?

 

 

    /**

    * Initializes, creates, and registers fake ice

    */

    public static void initialize(){

   

    /* Initialize, create, and register the ice */

    ice = new FakeIce();

    ice.setUnlocalizedName(Blocks.ice.getUnlocalizedName().substring(5));

    ice.setCreativeTab(CreativeTabs.tabAllSearch);

    ice.setHardness(0.5F);

    ice.setLightOpacity(3);

    ice.setStepSound(soundTypeGlass);

    GameRegistry.registerBlock(ice, Blocks.ice.getUnlocalizedName().substring(5));

   

    }

[deadrecon98]

Send the crash report and the entire class.

[Draco18s]

It's a bad idea because Forge hasn't hit the Pre-Init phase yet and it will not let you register blocks and items then.

[shadowfacts]

Should work fine if you call YourClass.initialize() from PreInit

[NecroTheif]

It does work, I am calling this static method in the PreInit method in my main class. I was just wondering why this would be a bad idea? I was told by a friend that it was a bad idea because of the way forge registers items but he didn't know any more than that. I was wondering why it's a bad idea?