Jump to content

Recommended Posts

Posted

Which block are you having a problem with?

Are there any errors in the console?

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted
5 hours ago, Draco18s said:

Which block are you having a problem with?

Are there any errors in the console?

PencilBlock renders as a pink and black cube,
The console gives an error for literally every block state (facing=up,down, east,west etc.)
However, I'm pretty sure I got everything right in the class itself, and I thought i had stuff right in the json file (now I removed some)

Posted (edited)
6 hours ago, diesieben07 said:

How is it invalid? I'd check myself but my computer broke yesterday (motherboard died).

Thanks for all the comments though, I wouldn't catch a lot of those things by myself.

Edited by Poseidon5001
Posted

Similarly, your asset files need to be all lower case as well.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Posted
On 5/21/2017 at 1:48 PM, Jay Avery said:

Your "facing" variant should not be an array (surrounded by square brackets). Also, model names must be entirely lowercase so "testmod:tilePencil" will not work.

 

On 5/21/2017 at 4:11 PM, Draco18s said:

Similarly, your asset files need to be all lower case as well.

So I've changed these things, but am still having trouble.
I don't know if I've made other mistakes along the way or something, but it seems the entire blockstate file isn't working, since it doesn't seem to have the particle texture either.

Posted (edited)
1 minute ago, Jay Avery said:

Your blockstates file itself still has capital letters in the name.

 

If that doesn't solve the issue, post the latest error logs.

Wait so no blockstate files are supposed to have capital letters? how come all my other blocks render fine, then?
And isn't the blockstate file name supposed to be identical to the registry and unlocalized names?
I havent changed the blockstate file name and it was working fine before i added the variants.

Edited by Poseidon5001

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello all. I'm currently grappling with the updateShape method in a custom class extending Block.  My code currently looks like this: The conditionals in CheckState are there to switch blockstate properties, which is working fine, as it functions correctly every time in getStateForPlacement.  The problem I'm running into is that when I update a state, the blocks seem to call CheckState with the position of the block which was changed updated last.  If I build a wall I can see the same change propagate across. My question thus is this: is updateShape sending its return to the neighbouring block?  Is each block not independently executing the updateShape method, thus inserting its own current position?  The first statement appears to be true, and the second false (each block is not independently executing the method). I have tried to fix this by saving the block's own position to a variable myPos at inception, and then feeding this in as CheckState(myPos) but this causes a worse outcome, where all blocks take the update of the first modified block, rather than just their neighbour.  This raises more questions than it answers, obviously: how is a different instance's variable propagating here?  I also tried changing it so that CheckState did not take a BlockPos, but had myPos built into the body - same problem. I have previously looked at neighbourUpdate and onNeighbourUpdate, but could not find a way to get this to work at all.  One post on here about updatePostPlacement and other methods has proven itself long superceded.  All other sources on the net seem to be out of date. Many thanks in advance for any help you might offer me, it's been several days now of trying to get this work and several weeks of generally trying to get round this roadblock.  - Sandermall
    • sorry, I might be stupid, but how do I open it? because the only options I have are too X out, copy it, which doesn't work and send crash report, which doesn't show it to me, also, sorry for taking so long.
    • Can you reproduce this with version 55.0.21? A whole lot of plant placement issues were just fixed in this PR.
    • Necro'ing that thread to ask if you found a solution ? I'm encountering the same crash on loading the world. I created the world in Creative to test my MP, went into survival to test combat, died, crashed on respawn and since then crash on loading the world. Deactivating Oculus isn't fixing it either, and I don't have Optifine (Twilight forest is incompatible)
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.