Jump to content

Recommended Posts

Posted

What's going on with the BlockID assignment? It in no way takes my suggested block ID's into consideration, and 1 of which is determined to give my block an ID of 31743, obviously WAY out of bounds. I am acquiring this key when the properties gets the ID for the first time, but my default ID of 564 doesn't pursuade it away from giving a ridiculous ID. It only does it to me on a single block, and it extends BlockStair, if that matters.

 

I am currently using a work around that manually saves a sane BlockID, then the config loads and uses that ID fine.

 

Anyone know what is going on?

Posted

Are you sure you're calling Configuration.getBlock() and not getItem()?

There's an EAQ for a reason. Read it!

"Note that failure to read this will make you look idiotic. You don't want that do you?" -- luacs1998

 

First rule of bug reports: More information is always better.

Oh, and logs OR IT DIDN'T HAPPEN!!

Posted

Are you sure you're calling Configuration.getBlock() and not getItem()?

I worked it out, and yep, thats what I did xD I duped all the registration from one of my items and forgot to change that to getBlock xD I ended up just doing a manual get, then when looking at the config, I slapped myself when I saw my stairs block listed under items.

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



×
×
  • Create New...

Important Information

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