Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

ClientRecipeBook and RecipeBookCategories


ChampionAsh5357
 Share

Recommended Posts

Although there is support for recipes and recipe implementations, there seems to be relatively little when it comes to how its displayed in the recipe book. There are two main classes this occurs in: ClientRecipeBook and RecipeBookCategories.

 

Since RecipeBookCategories is an enum, it can be easily extended upon via IExtensibleEnum. However, ClientRecipeBook is a bit more tricky. There needs to be some references in newRecipeList, getCategory, and func_216769_b.

 

newRecipeList concatenates recipe book categories together. This is because the search categories include all the references from the same type categories (e.g. FURNACE_SEARCH will contain recipes listed in FURNACE_BLOCKS, FURNACE_FOOD, and FURNACE_MISC). This works in association with func_216767_a to put the subcategories into the search one.

 

getCategory associates a specific IRecipeType with a recipe book category.

 

func_216769_b associates a RecipeBookContainer (just an extension of Container) with a list of associated recipe book categories.

 

So there would need to be some sort of mapping that associates an IRecipeType with one or multiple RecipeBookCategories depending on the tab, a RecipeBookContainer with all corresponding RecipeBookCategories, and a search RecipeBookCategories to its subcategories.

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.

Guest
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.

 Share



×
×
  • Create New...

Important Information

By using this site, you agree to our Privacy Policy.