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

Iron/Steel dust Dupe #391

Closed
Emiuna opened this issue Jul 8, 2023 · 6 comments
Closed

Iron/Steel dust Dupe #391

Emiuna opened this issue Jul 8, 2023 · 6 comments
Labels
bug Something isn't working. fixed-next-GTCEu This will be fixed in the next update of GTCEu.
Milestone

Comments

@Emiuna
Copy link

Emiuna commented Jul 8, 2023

Nomi CEu Version

1.6.1-beta-3a

Launcher

Prism

Configurations or Mods Changed

No response

Environment

Singleplayer

Mode

Both Modes

What Happened

By macerating iron doors, you can get more iron out than you put in. It's 6 ingots per 3 iron doors by default, so 2 ingots per door, but each door gives 37 tiny piles of iron (About 4 ingots) when macerated, as well as a tiny pile of steel.

Expected Behavior

You should get equal amounts of iron from macerating as you put in. The issue probably comes from that the vanilla iron door recipe (6 ingots) is enabled but the maceration step gives back the amount of resources that would be used if the hard iron door recipe was enabled (in GT config), so it could be fixed by properly enabling the hard door recipe or by changing the maceration step to just give 2 iron dust (Or 18 tiny piles or whatever).

Reproduction Steps

  1. Craft iron doors (6 iron for 3 doors)
  2. Macerate them (Gives 37 tiny piles of iron each and one tiny pile of steel)

Logs

No response

Additional Information

No response

@Emiuna Emiuna added the bug Something isn't working. label Jul 8, 2023
@Emiuna
Copy link
Author

Emiuna commented Jul 8, 2023

Also this is somewhat related to issue #365 so my guess is the regular door recipe that uses ingots is probably not meant to be enabled (At least in hard mode)

@IntegerLimit
Copy link
Member

Yep. I'll fix this later today.

@IntegerLimit IntegerLimit added this to the 1.7 milestone Jul 12, 2023
@IntegerLimit
Copy link
Member

Problem in GT. Please move this to there: https://github.com/GregTechCEu/GregTech/issues. Mention #365 in your issue there too.

Thanks! Hopefully will be fixed over there.

@IntegerLimit IntegerLimit added the GTCEu-problem This should be transferred to GTCEu. Replace this with fixed-next-GTCEu if problem is fixed. label Jul 24, 2023
@IntegerLimit IntegerLimit modified the milestones: 1.6.1, 1.7 Jul 24, 2023
@IntegerLimit
Copy link
Member

Temp Fix will be happening now, hopefully with a proper fix in gt 2.7.3. (aka 1.7 alphas, betas, or release).

@IntegerLimit IntegerLimit added fixed-next-GTCEu This will be fixed in the next update of GTCEu. and removed GTCEu-problem This should be transferred to GTCEu. Replace this with fixed-next-GTCEu if problem is fixed. labels Jul 25, 2023
@IntegerLimit
Copy link
Member

Ah, I accidentally put a closing keyword into that commit. Re-opening...

@IntegerLimit IntegerLimit reopened this Jul 25, 2023
@Folanlron
Copy link

Fixed via, #452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working. fixed-next-GTCEu This will be fixed in the next update of GTCEu.
Projects
None yet
Development

No branches or pull requests

3 participants