Jump to content

Making config IDs for metadata, biomes


Cyan

Recommended Posts

Hello,

 

Is there a proper way to make IDs for metadata? Naturally the it can't be done the way a normal block or item is done, and I haven't seen anything suggesting it can be done. Although I'm sure there is a way. I saw one of the tutorials on the wiki has a "chaining configurations" section, but Im not sure that exactly applies(although it could, since that portion didn't offer much explanation).

 

Same question for biomes. Adding configurable IDs only allows one custom biome to generate(if there are multiple registered under the config). This one I'm not sure can be done, but I figured I would ask anyway.

 

Thanks in advanced!

Link to comment
Share on other sites

Configurable Biomes ids ? of course, like any block or item...put an int into your config file.  :P

 

I don't see the point for metadata actually. You'll need to initialize all of your block versions, and check that none overlap...

Even worse for items, you don't have any limitation if you use item damage.

Link to comment
Share on other sites

Well..Like I said in the initial post, if you have more than one biome ID in your config file, it appears to only generate the last biome added to the config.

 

The point of metadata is to keep the clutter down. I find it  much cleaner to create one item file for 15 similar items than to make them all separate.

 

 

 

Link to comment
Share on other sites

Well..Like I said in the initial post, if you have more than one biome ID in your config file, it appears to only generate the last biome added to the config.

You could store anything in your configFile, it doesnt have to be a biome/block ID it can be any int.

So it should work to add the biome ID's as well.

Have you seen this http://www.minecraftforge.net/wiki/How_to_make_an_advanced_configuration_file ?

Especially the third option is handy I think:

int someInteger = Integer.parseInt(config.getOrCreateProperty("SomeInteger", Configuration.CATEGORY_GENERAL, ""+100).value);

Check it out ;)

 

The point of metadata is to keep the clutter down. I find it  much cleaner to create one item file for 15 similar items than to make them all separate.

 

Metadata is nice for blocks yeah, but why do you need it saved in the config?

if blockA has ID 280 and it's metadata 280:1 is a white version, then if blockA has a different ID like 530 then it's white version would still be the metadata value 1.

 

So why would you need your own config for them? :)

 

If you guys dont get it.. then well ya.. try harder...

Link to comment
Share on other sites

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.