LegendLength

Firstly I apologize for initially posting in the wrong forum. I tried looking through the category code for forge, and also example configs, but couldn't find a way to do it apart from forcing the user to label each category with a unique name. For example if they want 8 pages in the book they would have to make 8 categories with unique names: category1: category2: ... category8: What I am after is a way for them to create an 'array' of categories where the name is not required. So: pages: { page 1 configuration data} { page 2 configuration data} ... { page 8 configuration data} In the latter case they can just rearrange the pages without the need to rename every category (which could get annoying for a 50 page book).

I have a mod that allows the user to specify images that will be loaded dynamically by the mod and used as textures. Currently I'm allowing them to put those textures anywhere within the minecraft folder tree and just reference them from the config file. e.g. "Image1 = "config/modName/image1.png" . Then when a mod pack author uses my mod they just get their installer to copy the image files to whatever folder they choose and also include the correct paths in the config file. But it doesn't feel right to put them into the config folder. Then again it doesn't seem right to create a new folder in the minecraft root directory just for this mod. Is there a more 'standard' place to put binary data like this? Just in case it wasn't clear, the images are supplied by the mod pack author, so I cannot include them in the mod as a java resource.

I'm creating a mod that allows a mod pack author to create a book in minecraft. The book can contain images which are specified by the mod pack author via a configuration file. The configuration has a list of pages, each page has an image file name and information like margin size and other layout properties. My problem is the standard forge configuration format doesn't seem to support arrays in this way. I realize you can still have nested configuration like: page.page1 page.page2 page.page3 But I would prefer a style of: pages { { [properties for page 1] } { [properties for page 2] } etc. } Where the user doesn't need to name each section explicitly using 'page1', 'page2' etc.. Just because it adds a burden to the user when they want to shift pages around. So i've implemented it in Json instead but I would prefer to use normal forge config files for 2 reasons: 1. Forge configuration style is standard across nearly all mods. 2. Json doesn't allow comments, incredibly. Let me know if that was too vague.