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

Suggestion: Increase Indium yield from IsaMill chain #15686

Closed
4 tasks done
norbby42 opened this issue Mar 10, 2024 · 6 comments
Closed
4 tasks done

Suggestion: Increase Indium yield from IsaMill chain #15686

norbby42 opened this issue Mar 10, 2024 · 6 comments

Comments

@norbby42
Copy link
Contributor

norbby42 commented Mar 10, 2024

Your GTNH Discord Username

Quackers#6418

Your Pack Version

2.5.1

Your Proposal

Increase the yield of Indium Dust from the IsaMill/Flotation Cell/Vacuum Furnace chain from 1 per 8 Crushed Sphalerite.

The LCR method, for comparison, yields 1 Indium Dust per 9 Purified Sphalerite.

Your Goal

The milling chain should be worth the investment.

Said chain has expensive multiblocks, including one (the Flotation Cell) which permanently locks to its recipe once used. It also requires additional infrastructure to support it (Pine Oil, Sodium Ethyl Xanthate Dust).

Its exceptionally slow speed (especially when compared to a LCR doing the Indium Concentrate recipe), high power drain, and additional upfront costs do not merit the current benefit of not consuming Aluminium Dust or yielding Copper/Iron/Cadmium.
Keep in mind, this chain unlocks at ZPM, at which point most players will already have enormous stockpiles of all 4 of these dusts, thus making them a non-factor in the chain's value.

Your Vision

Processing chains should reward based on the investment required to create them. A great example of this is the Thorium 232 chain. The easy way produces significantly less output than the hard way, matching the needed investment and chain complexity:

  • The easy way is doable entirely in a multiblock you already have. It uses 2 recipes.
  • The hard way is 9 recipes spread across 5 machine types.

The two Indium chains have a similar architecture, and should have proportionally improved yield.

Final Checklist

  • I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying I like this change please reconsider adding it will prompt us to investigate and reopen it once we confirm your report.
  • 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 think it's inappropriate.
  • I believe this feature would make the pack better.
@norbby42 norbby42 added Status: Triage Issue awaiting triage. Remove once this issue is processed Suggestion labels Mar 10, 2024
@Reflex18
Copy link
Contributor

Indiumzpmlcr
Indiumisamill float

I used the GTNH-flow tool to create a graph of two of the indium processes at ZPM age which is when the IsaMill chain is unlocked.

The parameters were that there is a limit of one Floattion Cell machine in the IsaMill chain and a limit of one LCR in the LCR chain.

Scale up as needed, but it should showcase just how slow the Milling chain is.

@chochem chochem added Mod: GT++ Type: Recipe and removed Status: Triage Issue awaiting triage. Remove once this issue is processed labels Mar 11, 2024
@Steelux8
Copy link
Contributor

I personally did not want to rebalance this multi chain, and instead wanted to rework it with new mechanics because stuff like "permanently locks to its recipe once used" is not what I'd like to reinforce with this special oreproc. However, new multi development is currently not encouraged.

Someone else might want to fix this, though, so thank you for coming forward with the information.

Copy link
Contributor

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Jun 11, 2024
@Dream-Master Dream-Master removed the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Jun 11, 2024
Copy link
Contributor

github-actions bot commented Sep 9, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 3 days

@github-actions github-actions bot added the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Sep 9, 2024
@chochem
Copy link
Member

chochem commented Sep 9, 2024

x3 increase with bees done in GTNewHorizons/NewHorizonsCoreMod#967

@chochem chochem closed this as completed Sep 9, 2024
@Ableytner
Copy link

It should be noted that the 3x increase with bees was also added to the LCR method, making this suggestion still valid.

@github-actions github-actions bot removed the Status: Stale Automatically close this issue in 2 weeks if there are no new responses label Nov 20, 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

6 participants