Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EMI-Style recipe expansion using favourites #17589

Open
5 tasks done
ShadowTrolll opened this issue Oct 8, 2024 · 5 comments
Open
5 tasks done

EMI-Style recipe expansion using favourites #17589

ShadowTrolll opened this issue Oct 8, 2024 · 5 comments

Comments

@ShadowTrolll
Copy link

Your GTNH Discord Username

ShadowTrolll

Your Pack Version

2.6.1

Your Proposal

Add an EMI-style system for setting recipes as favorites for later crafting tree auto-expansion as seen here:
image
image

Your Goal

The NEI material cost calculation is very useful, but it gets quite tedious adding the same recipe chain to all crafting groups when you know that you "always" make the item a certain way. This feature eliminates the tedium while still being flexible. If you transfer to a new crafting process for an item, you simply favourite the new recipes instead of the old ones and all costs get calculated automatically.

Example:
I want to know how many resistors, capacitors and other materials I need for any machine I want to craft. I would start by favouriting my chosen recipes for circuits (lets say 2nd tier HV using SMD components), then favourite the component recipes and keep doing this until I have favorited the chain all the way I wanted to. Lets say down to ingots. Now any time I wish to show the costs to craft recipes containing HV circuits or other components I favorited NEI automatically calculates the circuits down to ingots.

Your Vision

Much easier and more comfortable calculation of recipe costs.

Final Checklist

  • I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying I like this feature please reconsider adding it will prompt us to investigate and reopen it once we confirm your report.
  • I believe there is nothing similar in the pack already, or the existing solution isn't good enough.
  • I understand this change request may not attract enough attention and thus not be implemented.
  • I understand this change request may be rejected due to other community members thinking it's inappropriate.
  • I believe this feature would make the pack better.
@ShadowTrolll ShadowTrolll added Status: Triage Issue awaiting triage. Remove once this issue is processed Suggestion labels Oct 8, 2024
@slprime
Copy link
Member

slprime commented Oct 8, 2024

@Dream-Master
Copy link
Member

can we port emi back to 1.7.10? looks cool.

@slprime
Copy link
Member

slprime commented Oct 10, 2024

can we port emi back to 1.7.10? looks cool.

I was thinking of doing something like this
GT_NewHorizons2 7 02024-10-1019-15-00-ezgif com-video-to-gif-converter

@ShadowTrolll
Copy link
Author

can we port emi back to 1.7.10? looks cool.

I was thinking of doing something like this GT_NewHorizons2 7 02024-10-1019-15-00-ezgif com-video-to-gif-converter GT_NewHorizons2 7 02024-10-1019-15-00-ezgif com-video-to-gif-converter

As long as I can set a recipe as "default" for a resultant item and there is a way to quickly use these favorites to compute component costs I am happy.

From your showcase I like the fact that (I suppose) I can manipulate the group normally afterward, meaning I can replace sub recipes without affecting my favourites, such as when I would be making a loop-specific setup I don't use normally.

@slprime
Copy link
Member

slprime commented Oct 10, 2024

From your showcase I like the fact that (I suppose) I can manipulate the group normally afterward, meaning I can replace sub recipes without affecting my favourites, such as when I would be making a loop-specific setup I don't use normally.

yes, you got it right. after creating a group you can edit it as you want

@Yamnasm Yamnasm added Type: Visual Mod: NEI Type: QoL and removed Status: Triage Issue awaiting triage. Remove once this issue is processed labels Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants