Help creating a tool?

[sfxworks]

Trying to make a tool (not a mod. Sorry if this is in the wrong category) that will dive through any jar file I give it.  It should be able to retrieve any new items/blocks added by the mod as well as any recipes and images related to said items/blocks.

 

Want to make some sort of modpack creator/server lister/mod detailer/super awesome thing in the future and this is a key component.

 

Any clue as to where I would start? Just diving through Tinker's Construct with WinRar points me to a bunch of classes with unreadable text..

[sfxworks]

This is not easily possible at all. If anything this would be doable as a mod that runs alongside any other mods you want to analyze.

 

So something like Idfix http://www.minecraftforum.net/forums/mapping-and-modding/minecraft-mods/1291014-idfix-and-idfix-minus-mods-for-resolving-id where it pulls the mod items and changes their item ids? (The part where it pulls the items & recipes being the part I want)

 

Any idea on how to start using a method like that?

 

I guess I'd have a server that would start & stop and generate reports based on the mods loaded..

[Draco18s]

Just diving through Tinker's Construct with WinRar points me to a bunch of classes with unreadable text..

 

That's because you're looking at the raw bytecode for the mod, not the source code.

If you wanted to read .class files as code, you'd need to decompile it first (fortunately Java is an open source format, albeit complicated).

 

Or you can write it as a mod, as diesieben suggests.

[sfxworks]

Just diving through Tinker's Construct with WinRar points me to a bunch of classes with unreadable text..

 

That's because you're looking at the raw bytecode for the mod, not the source code.

If you wanted to read .class files as code, you'd need to decompile it first (fortunately Java is an open source format, albeit complicated).

 

Or you can write it as a mod, as diesieben suggests.

 

Decompiling sounds interesting (but another learning curve). Making a mod sounds a bit more interesting. Only made one unlaunched bukkit mod before so playing with forge sounds like a cool new hobby.

 

You would write a mod like normal. Then when the game has loaded you'd go through the registries of the stuff that you want and print out whatever info you need.

 

 

Now we're talking. Is there some sort of get all items and blocks from the registry function? I can see that I can search for one as of now. Miiiight not be a good idea to cycle through all possible a-z0-9 variations.

 

[Choonster]

The

ForgeRegistries

class exposes each registry (blocks, items, etc.) as an

IForgeRegistry

. This extends

Iterable

, so you can iterate through the registry's values with a for-each/enhanced for loop.

 

You can also use

IForgeRegistry#getEntries

to get the entries (keys and values).

[sfxworks]

The

ForgeRegistries

class exposes each registry (blocks, items, etc.) as an

IForgeRegistry

. This extends

Iterable

, so you can iterate through the registry's values with a for-each/enhanced for loop.

 

You can also use

IForgeRegistry#getEntries

to get the entries (keys and values).

 

Heh, this is pretty fun.

 

 

I see a lot of properties I can take advantage of. The only ones I can't find are a default recipe and an image representing the item/block. Where would I find said properties?

 

 

[Choonster]

You don't need to use an

Iterator

to iterate through an

Iterable

, just use an enhanced for loop.

 

Blocks don't have a single recipe or image. There are many recipes, some of which may output a specified block. Each block can have a model per state, each model can use multiple textures.

 

CraftingManager#getRecipeList

returns the recipe list,

IRecipe#getRecipeOutput

returns the recipe's default output (may be

null

). Recipes can change their actual output based on the contents of the crafting grid, so the default output may not be what the player actually gets when they craft it.

 

BlockModelShapes#getModelForState

returns the model for the specified block state.

IBakedModel#getParticleTexture

returns the model's particle texture (could be used as the default texture).

IBakedModel#getQuads

returns a list of

BakedQuad

s,

BakedQuad#getSprite

returns the quad's texture.

[Draco18s]

Mind there's also Smelting recipes (Furnace.getSmelting() iirc) and brewing recipes.

Mods then may add their own recipes devices (grinders, sifters, macerators, crushers, extractors, compressers, canners, electrolyzers, injectors, washers, mixers...).

[sfxworks]

Mind there's also Smelting recipes (Furnace.getSmelting() iirc) and brewing recipes.

Mods then may add their own recipes devices (grinders, sifters, macerators, crushers, extractors, compressers, canners, electrolyzers, injectors, washers, mixers...).

 

Is there a sort of official registry for said types of recipes or would I have to try to work with each mod individually?

[Draco18s]

Is there a sort of official registry for said types of recipes or would I have to try to work with each mod individually?

 

There is not. You would need to handle every mod individually.

[sfxworks]

Is there a sort of official registry for said types of recipes or would I have to try to work with each mod individually?

 

There is not. You would need to handle every mod individually.

 

Does Too Many Items and Not Enough Items go through the trouble of doing this? I would figure they would have some sort of way to bring up different crafting styles automatically.

 

Is there a sort of default property inside a Mod that stories it's custom recipes along with some detail on it's crafting mechanics?

[Choonster]

Does Too Many Items and Not Enough Items go through the trouble of doing this? I would figure they would have some sort of way to bring up different crafting styles automatically.

 

Is there a sort of default property inside a Mod that stories it's custom recipes along with some detail on it's crafting mechanics?

 

They have an API that allows mods to register handlers for their custom recipe types, there's no way to automatically handle every recipe type.

[Draco18s]

For example:

https://github.com/Draco18s/HarderStuff/blob/master/src/main/java/com/draco18s/ores/recipes/NEIIntegration.java