Draco18s

Grab a stack of notecards, write on three of them: JEI {JEI-API} FEI {FEI API} Now, using the before[] and after[] listed in that screenshot, sort them.

Hahahaha This is priceless. @SideOnly(Side.CLIENT) //make sure this method does not exist on a dedicated server public ItemStack onItemRightClick(ItemStack stack, World world, EntityPlayer player) { if(!world.isRemote) //if we're on the server thread... { //...then access the client side class! Minecraft.getMinecraft().displayGuiScreen(new GuiLivre1()); } return super.onItemRightClick(stack, world, player); }

I don't think your github is up to date with that crash. Line 30 where it's crashing is blank and backtracing through the call stack I don't see anything wrong.

You're trying to do something that isn't natively supported, so you're mostly on your own. Once your block gets larger than 1x1x1 you would, in effect, have a multiblock.

You should be looking at exactly 1 line of TileEntityHopper if I understood Choonster correctly, the line that says what interfaces it implements.

Hahahahaha, you can't client-side-only this. Not going to happen.

Light greater than 15 also requires fake blocks, but would be troublesome to manage properly.

You can't. End of story. You would need to have "fake" blocks occupying the surrounding area to provide collision.

Pretty sure you can't Item.getItemFromBlock() before you've registered the itemblock.

I'm at a loss. Null pointers are usually very easy to solve, but I can't locate ANYTHING in the method throwing the NPE that could be null.

You also should be using the code tag. Anyway. world.setBlockMetadataWithNotify(a, b, c, MathHelper.clamp_int(d, 0, 32), 2);[/quote] Two things: 1) That should be "x, y, z" as parameter names, not "a, b, c" 2) Metadata values only go up to 15. 3) You should probably use notify flag 3, not flag 2. [code] public static int returner(int a) { return a; } 4) This function does nothing but make your code harder to read. float max = j1 * 1f; 5) This line does actually nothing. You can cast from integer to float implicitly (although we'll come back to this in point 7): this.setBlockBounds(j1, j1, j1, -j1, -j1, -j1); 6) You have mixed up "min" and "max." this.setBlockBounds(-max, -max, -max, max, max, max); 7) Your size increase right now is 1 meta = 1 block of size. If you want it to be "a little bit" you need to multiply j1 by a smaller value. 1.0001 is still 1 block of size per meta: float max = j1 * 0.1f; //10 meta = 1 block-of-size

Please use spoiler and code tags or pastebin

Ugh. Rename those parameters. Highlight one, Source -> Refactor -> Rename

(You'll actually want to create a blank NBT tag, run it through, writeToNBT, then change the one value, then run it through readFromNBT: that makes sure that every other value doesn't get altered or throw errors)

Override getColorMultiplier if I am remembering the method name correctly. Look at the Leaves class for it.

And...its gone over my head. I do know that when compiled your files (in /src/resources) don't exist as "files" but as a virtual object inside a zip file, and it has to be referenced differently. But I can't tell what Sphinx4 is/isn't doing.

Look at the event class, there is probably a getter method.

Show the full class that contains updateCraftingMatrix ? Uh...ContainerFabTable.java

The leaves class has some field that does what you're doing, I just don't remember what it's name is and if its static. The point of doing this, though, has to do with: a) avoiding duplication b) avoiding errors c) avoiding inadvertently referencing Minecraft.getMinecraft() on a dedicated server.

You have this: @SideOnly(Side.CLIENT) public void setGraphicsLevel(boolean fancy) { this.isTransparent = fancy; Minecraft.getMinecraft().gameSettings.fancyGraphics = fancy; this.iconIndex = fancy ? 0 : 1; } You shouldn't need it. You should be referencing Blocks.leaves.isTransparent , not storing your own copy.

Then you're doing something seriously wrong. You need to debug things. I'm almost certain that the problem has to do with either the Slots you've set up, or the call to onCraftMatrixChanged in the constructor.

Don't copy the code from Blocks.leaves, just reference the code in Blocks.Leaves

The change you made makes it impossible for the "changes" to save back to the TileEntity in the world because you created a new one.

oh, sorry, I must have snipped out the "new" keyword by accident. You should have been able to fix that on your own.