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

Catalyst in alloying #5135

Open
MiyaPixai opened this issue May 27, 2023 · 0 comments
Open

Catalyst in alloying #5135

MiyaPixai opened this issue May 27, 2023 · 0 comments
Labels
1.18 Issue affects 1.18 1.19 Issue affects 1.19 Confirmed Issue has been verified as being caused by Tinkers, or an enhancement is planned to be added Enhancement Issue or pull request addresses a change to an existing functional feature

Comments

@MiyaPixai
Copy link

Minecraft Version

1.18.2

Forge Version

40.2.2

Mantle Version

1.9.45

Tinkers' Construct Version

3.6.4.113

Problem description

It's not possible for alloy to either have two product, or keep one of the alloying ingredient intact during the process.
For example, requiring a high value material to unlock a recipe without needing to consume said material.

Suggested solution

Allow one of the ingredients of an alloying recipe to be a catalyst; required for, but not being consumed by, the process.

Alternatives considered

Apart from by-products, which aren't support by the alloying process, my current solution is to use the catalyst as a reusable cast in a casting table.
This makes the process mildly convoluted as the material needs to be re-melted to be used in the smeltery.

Additional context

My current use case requires a nether star to craft an end game Create ingot. The nether star isn't consumed by the process.

Searched for existing enhancement?

Used the search bar, Checked the FAQ

@MiyaPixai MiyaPixai added 1.18 Issue affects 1.18 Enhancement Issue or pull request addresses a change to an existing functional feature Unreviewed Issue is new and is awaiting the team to review it labels May 27, 2023
@KnightMiner KnightMiner added Confirmed Issue has been verified as being caused by Tinkers, or an enhancement is planned to be added and removed Unreviewed Issue is new and is awaiting the team to review it labels May 28, 2023
@KnightMiner KnightMiner added the 1.19 Issue affects 1.19 label Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.18 Issue affects 1.18 1.19 Issue affects 1.19 Confirmed Issue has been verified as being caused by Tinkers, or an enhancement is planned to be added Enhancement Issue or pull request addresses a change to an existing functional feature
Projects
None yet
Development

No branches or pull requests

2 participants