Animefan8888

No when it says instance there it doesn't mean your mods modid, it means an instance of your main mod class which you get from putting @Instance(MODID) public static MAINMODCLASS instance; in your Main mod class.

No need for the caps. When it says instance it means @Instance(MODID) public static MAINMODCLASS instance;

What is Ref.MODID? It is asking for the mods instance.

Is there anything in the log. His Entity extends EntityMob

Did you register this Entity? Also you should try to debug these issues yourself instead of coming straight to the forum.

That is fine, though I'm not sure if Diesieben will lock it or not (I can't do that). Though I will tell you that it will be unlikely that someone can answer your problem without your Error log.

There isn't one. As he said there is no reason to not update. Please update. It has been said that 1.7.10 is no longer supported.

You should update to 1.10 then check out BiomeDecorator

Post the error log again.

First thing is first update to 1.10.

Well I have no Idea why that piece of code was needed, but I guess it was necessary. But that piece of code only makes it spawn at light levels 8 and lower. There was no need to change that I think do you want it to spawn at high light levels or low light levels like mobs? If so that was fine, but since you want it to only spawn underground you need to add worldObj.canBlockSeeSky(blockPos) to the getCanSpawnHere() method

What is with this.rand.nextInt(32) You should also check to see if the entities pos can see sunlight using worldObj.canBlockSeeSky(blockPos)

Well as long as the class path extends EntityLiving you should be able to use getCanSpawnHere() and could you show me how you edited it.

You mean your Entity is a passive entity?

In your Entity class you need to override this method public boolean getCanSpawnHere() { return this.worldObj.getDifficulty() != EnumDifficulty.PEACEFUL && this.isValidLightLevel() && super.getCanSpawnHere(); } To add the entity to spawn just loop through all the biomes from BiomeGenBase use EntityRegistry.addSpawn()

It is weird, but I think it may have something to do with this 1. Creates a new NBTTagCompound 2. The new NBTTagCompound is equal to tileEntity.writeToNBT(the new NBTTagCompound) 3. NBTTagCompound is saved to disk. I think that is how it works and don't know why they changed it. Diesieben or someone if you know why they changed it and/or how it works feel free to post or pm me about it.

The one that was passed in.

They changed the methods return type instead of void it's NBTTagCompound.

Well since you copied them...I doubt you know what they do.... But now you need to make new Slot classes one for Output and one for FuelInput unless you are using the Normal Furnaces Fuel.

Container Furnace and GuiFurnace Do not make them exact copies there need to be changes if you want to use your own custom recipes.

{ "parent": "block/orientable", "textures": { "top": "modid:blocks/texture_top", "front": "modid:blocks/texture_front_off", "side": "modid:blocks/texture_side" } }

First a suggestion instead of public static void setState(boolean active, World worldIn, BlockPos pos) { BlockMachine.setState(active, worldIn, pos, ModBlocks.FLUXGRINDERWORKING, ModBlocks.FLUXGRINDER); } Use public static void setState(boolean active, World worldIn, BlockPos pos) { super.setState(active, worldIn, pos, activeBlock, nonActiveBlock); } But back on topic did you look at the JSON aswell?

So the problem you are having is that when you place it, it faces the complete opposite way?

You should update to 1.10 aswell