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

Minimal Tetra compatibility #25

Open
moonfather1 opened this issue Jun 17, 2022 · 4 comments
Open

Minimal Tetra compatibility #25

moonfather1 opened this issue Jun 17, 2022 · 4 comments
Labels
enhancement New feature or request stale Used for issues that don't have a reply or resolution that can be closed due to being "stale".

Comments

@moonfather1
Copy link

Describe the Addition

  • No not about using gems in a workstation -
    (that's a bit advanced and requires a bunch of json files; also i don't feel the need)

Issue:
MM tools do not qualify as tools when creating something at tetra worktable.
Example: I want a new pickaxe to have a spruce wood handle; for that I need a tier 1 axe in my inventory or hanging on a rack nearby; a simple stone axe is enough in my inventory to click the button and give my tool a wooden handle. But - none of the MM axes qualify.

Screenshots and Videos

No response

Additional Context

No response

@moonfather1 moonfather1 added the enhancement New feature or request label Jun 17, 2022
@Dariensg
Copy link
Contributor

Could you clarify what version this is for? I've just looked at 1.16.5 and the Mining Master tools seem to be backed by the ToolType that Tetra requires to detect that, since they all extend the Vanilla tool items.

@moonfather1
Copy link
Author

MM 3.0.4, Tetra 3.20

@Noobulus
Copy link

Noobulus commented Sep 8, 2022

If memory serves, Tetra uses replacement files (such as this one for diamond tools) to determine tool level for use in the workbench. Is the 1.18 version of Mining Master still being maintained for me to write a PR for this?

@Dariensg
Copy link
Contributor

Dariensg commented Sep 8, 2022

Yes! 1.18 is still being maintained and a PR would be much appreciated for this!

@Dariensg Dariensg added the stale Used for issues that don't have a reply or resolution that can be closed due to being "stale". label Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Used for issues that don't have a reply or resolution that can be closed due to being "stale".
Projects
None yet
Development

No branches or pull requests

3 participants