-
Notifications
You must be signed in to change notification settings - Fork 790
General FAQ
This FAQ is for general questions related to SlimeKnight's mods. For questions about Tinkers' Construct 3 gameplay, see Tinkers' Construct 3 FAQ. For questions related to Tinkers' Construct 2, see Tinkers' Construct 2 FAQ.
This FAQ is up to date. If it has not been updated in awhile, that means nothing has changed. Asking a question that is on here because "it has not been updated in awhile" is a violation of our rules and is grounds for banning.
Some questions have discord commands. This is for the sake of others asking the same question, it has identical information to this FAQ so there is no need to run it for yourself.
Discord command
!support
We currently are primarily focused on 1.19.2, which was recently marked as stable. We still have some API improvements and new features planned, but no major breaking changes so its a good time to port addons. We plan to release a new update to 1.18.2 in the near future to deal with bugs discovered during the 1.19 port, though it is end of life meaning no new major features are planned (just bug fixes or minor features). Anything before 1.18.2 is no longer supported.
1.20 will come after we are satisfied with content on 1.19.2. 1.19.4 will likely not get a release. It is undecided which 1.20.x version we will support; it depends entirely on what we feel is the best version to support given the Forge and NeoForge split.
If you want help with gameplay, you are free to ask on our discord, though note help with 1.7.10 or 1.12 may be limited due to how old those versions are (its been years, details are forgotten). Additionally, anything older than 1.7.10 and any version between 1.8 and 1.11 are entirely unsupported. Make sure to mention what version you are talking about if asking about any version other than 1.19.2, as otherwise we will answer for 1.19.2.
In general, none of us see much point in porting the mod to another mod loader, as Forge has served us well enough for years and contains many systems we rely upon. Porting to another platform would require significant work, which none of us have time for.
A few notable platforms:
- Fabric is missing many systems that we rely upon, including models, events, Forge's fluid API, and the capability system. Replacing any of these or migrating to a Fabric version of the API (once added) would take significant effort for very little gain.
- Bedrock we do not believe has a mature enough addon system for us to make something that is properly Tinkers' Construct. This is only proven by the two ports on Bedrock we have seen.
While we do not have time to make such ports, there are several ports and alternatives to Tinkers' Construct that already exist, which are described by this spreadsheet.
If its a future version, we are already aware that version exists and are considering the porting in the future, see the above FAQ entry. If Tinkers' Construct skipped a Minecraft version, we have no plans to backport to it, so don't ask. We additionally have no plans to backport features from newer versions of Tinkers' Construct to older versions.
Note for 1.16.4 and 1.18.1 specifically, we require features from some of the latest Forge builds, which are only on newer minor versions. There is no reason you should still be on the earlier version as most mods have ported by this time. If you wish to still use 1.18.1 specifically, we have builds there, just accept that there are bugs. For 1.17, we opted to skip to 1.18 as we would rather not port the mod to 1.17 then immediately abandon it leaving users with potential bugs, we do not have time to maintain the mod for 3 versions (even 2 is a lot).
We do not give permission to port Tinkers' Construct to any other Minecraft edition on Minecraft Java for Forge or NeoForge as long as the mod is still actively being developed. Actively being developed can be loosely defined as any activity on the mod's GitHub or Discord by the authors, including just commenting on GitHub issues. If in doubt, feel free to reach out on discord. The reason for this blanket "no permission" statement is if the mod is not currently ported, that means we have a reason it is not ported. This is often related to wanting to stabilize older versions before moving onto newer versions, along with time constraints. You are free to reach out to ask how you can help with the port, but we are not interested in people making their own forks that are not under the official project. We currently are undecided on how we will handle the Forge and NeoForge split on 1.20.1+; once we decide we may add Forge post 1.20.1 to the list of platforms we do not support that others may fork into.
You are free to fork the mod if you wish to port to a platform we do not support, such as Fabric, Bedrock, or alike. If you do so however, we require you to name the project something other than "Tinkers' Construct" to prevent confusion for the end users expecting it to be the same project. Existing projects with the name "Tinkers' Construct" that are not made by SlimeKnights received permission before this policy was made or otherwise have an exception due to personally knowing one of the devs. You may reuse code and assets from Tinkers' Construct to make such a fork happen, as those are under the MIT license. Additionally, if you have a public release or a code repository with significant progress, feel free to post about it on our discord and I will add it to the spreadsheet.
Discord command
!cfbuilds
CurseForge is not great about displaying alpha builds on CurseForge. To ensure you don't miss the file, instead of looking at the sidebar, click "Files" then "View all". There is also a dropdown on the "View all" page to filter by version.
Start by updating your mods to the latest version, as your bug is possibly fixed in a later version. Also try testing with just Tinkers' Construct installed to determine if its a mod conflict, as that can be valuable information for fixing the issue.
If the bug still happens in an up to date pack, you can try searching our issue tracker to see if its a known issue, then ask on our discord for help debugging it.
If you are certain it is a bug in the latest version and it is not already reported it, you can create a new issue on our issue tracker.
If you want to make a suggestion, the preferred place to do so is our discord. Note that we expect suggestions to be thought out. Do not tell us to add your random idea, tell us exactly what you want us to add and why you think it belongs in the mod. A good rule of thumb is new features should have 3 distinct uses.
Posting your suggestion does not mean we will accept it, and in many cases we will critique your idea, so do not make suggestions if you are not open to criticism. Remember that you are asking us to take time out of our plans to work on your idea, coming up with a well thought out suggestion will make us a lot more likely to consider it. Also remember that suggestions can be a good source of addons, you could always learn to create mods by trying to create your idea.
When it comes to mod support, it typically must meet one of three criteria to be added:
- Support that works for many mods is preferred over support for a specific mod. For example, adding support for melting tin or alloying bronze supports several mods adding those ores and alloys, but support for knightmetal only helps Twilight Forest.
- One exception is trivial support, for example support that only requires a couple JSON files and has no balance considerations.
- If I personally play a mod, I am a lot more likely to add support than if I never use the mod.
- If someone else pull requests support, it will typically be added as long as it does not require significant maintenance. Please talk to the devs before making the pull request to prevent wasted work.
Note that these criteria are just guidelines, just because something meets these guidelines does not mean it will definitely be added. A notable case of this is support for a mod that we do not feel can be added without breaking the balance of the mod.
The only official wikis are those on the GitHub repositories. The other wikis are not made by our team. As a result, they may be a mix of multiple versions, or simply inaccurate.
Configs are located either in .minecraft/config as before, or in the world folder.
If you do not see an option to configure the feature in either place, note many of our features are also configurable via datapacks, and in the future we plan to continue to move configuration to data packs. For instance, nearly all our recipes can be changed or disabled via datapacks, and removing recipes can also be used to effectively remove features.
Feel free to use the mod in any modpacks. You are allowed to use it, you do not need to ask for permission. When using the mod, please use the CurseForge or GitHub download and do not rehost the files if possible. If you need to rehost the mod, link the CurseForge or GitHub page in your modpack description. Never use builds from places besides Curse, CurseForge, or Github releases.
Any modpack using Tinkers' Construct is expected to handle user support queries, specifically related to mod interactions. If you discover the issue is in fact caused by Tinkers' Construct and not just modpack config changing recipes, feel free to report it to us.
We have no plans to maintain a public server for our mods. There are many other public servers that exist that contain our mods, or private servers you can join. Note that our discord server should not be used to seek a server to join or to advertise Minecraft servers.