Updating to 1.8

[killerjdog51]

Im sorry for being a noob. but i still dont understand 1.8 one bit (1.7 was simple compared to 1.8 for me) i mean, i have my metadata block made, but it wont render the texture. please help me.

 

 

 

package com.stonemod.Main;

 

import net.minecraft.block.Block;

import net.minecraft.block.material.Material;

import net.minecraft.client.Minecraft;

import net.minecraft.client.resources.model.ModelBakery;

import net.minecraft.client.resources.model.ModelResourceLocation;

import net.minecraft.item.Item;

import net.minecraftforge.fml.common.Mod;

import net.minecraftforge.fml.common.Mod.EventHandler;

import net.minecraftforge.fml.common.event.FMLInitializationEvent;

import net.minecraftforge.fml.common.registry.GameRegistry;

 

@Mod(modid = MainRegistry.MODID, version = MainRegistry.VERSION)

public class MainRegistry

{

    public static final String MODID = "stonemod";

    public static final String VERSION = "1.0";

   

   

    public static Block Andesite;

    public static Block Diorite;

    public static Block Granite;

   

    @EventHandler

    public void init(FMLInitializationEvent event)

    {

Andesite = new BlockAndesite(Material.rock).setHardness(1.5F).setResistance(10.0F).setStepSound(Block.soundTypePiston).setUnlocalizedName("andesite");

GameRegistry.registerBlock(Andesite, "andesite");

Minecraft.getMinecraft().getRenderItem().getItemModelMesher().register(Andesite, 0, new ModelResourceLocation("stonemod:chiseled_andesite", "inventory"));

Minecraft.getMinecraft().getRenderItem().getItemModelMesher().register(Andesite, 1, new ModelResourceLocation("stonemod:andesite_column", "inventory"));

ModelBakery.addVariantName(Andesite, new String[]{"stonemod:chiseled_andesite", "stonemod:andesite_column"});

 

    }

}

 

[Failender]

First of all, if you run this on a server this will crash it.

Registering Renderer should ONLY happen on client side, thats why you should use proxies to do so.

Show your folder structure in assets with the files please

[tiffit]

No need for proxies. Just check if the event is on the client side. Much easier.

[coolAlias]

There are lots of examples, hints, guides, and troubleshooting steps that have been put together by TGG.

 

Not a bad place to start your foray into 1.8 if you're feeling lost.

[jabelar]

No need for proxies. Just check if the event is on the client side. Much easier.

 

That's wrong but is a common misunderstanding.

 

If any code you reference has a class or method that is @SideOnly then you MUST use a proxy to manage your code.

 

This is because an @SideOnly is not even loaded into Java on the other side and will therefore crash Java.

 

The world.isRemote check can be used when your code is running (or at least allowed to run) on both sides.