Fix recycling recipes.

[tier940]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @tier940, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves an issue with recycling recipes by implementing a comprehensive refactor of their generation process. The changes ensure that all items, particularly those from various integration modules, have their recycling recipes correctly created and registered. This is achieved by transitioning material information loading to an event-based system and introducing dynamic recipe generation for items added during the lowest recipe registration phase, thereby enhancing the robustness and consistency of the recipe system.

Highlights

• Recycling Recipe Generation Refactor: The mechanism for generating recycling recipes has been refactored to ensure proper registration for all items, especially those introduced by integration modules. This includes moving material information loading to event-driven handlers.
• Module Material Info Loading: Material information loading for Applied Energistics 2 (AE2), Draconic Evolution & Draconic Additions (DEDA), and Ender IO (EIO) integration modules has been migrated to use a new MaterialInfoEvent handler, ensuring timely and correct processing.
• Dynamic Recycling Recipe Creation: The GTEModuleManager now dynamically generates recycling recipes for items that are newly registered during the registerRecipesLowest phase, addressing potential omissions from the previous static initialization.
• Removed Redundant Initialization: The explicit RecyclingRecipes.init() call has been removed from GTECoreModule as its functionality is now handled by the centralized module manager's dynamic generation logic.

Changelog

• CHANGELOG.md
  • Added 'Add BQu mixin [Add BQu mixin #359]'
  • Added 'Fix recycling recipes [Fix recycling recipes. #360]'

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩