Leaderboard

I think "ext.mappingsChannel" refers to a potential "ext" property of "minecraft", and that you need to start with the project. Try mappings channel: stuffiesss.ext.mappingsChannel, version: stuffiesss.ext.mappingsVersion

Use a Code block (the <> symbol in the top bar when editing) to preserve formatting.

This has already been the de-facto standard for quite a while now, but figured it would be a good idea to properly formalise it and make it clear for everyone. TL;DR: You can ask and offer support for Forge on any MC version, as long as you're not demanding it from staff and can accept that older versions may receive less attention due to people moving on to newer, shinier things. Tiered support policyThere are now essentially three tiers of support: full, legacy and minimal. Full supportThis tier has dedicated channels for help on the Discord, gets priority for documentation, new features and bugfixes, and is generally considered the main focus for Forge development and support. Triage actively ports and backports things as needed for versions within this tier where time allows. The MC versions covered by this follows the existing "LTS" system. In other words, the latest MC version and select versions before it are covered by this tier. We recommend people consider using the newest version possible, as it's likely to be fully supported for longer. Exact versions covered under the full support tier can be found near the top of the FAQ. Legacy supportThis tier is for older versions of MC that are no longer covered by the full support tier. This tier gets less attention, but is still supported to some extent. To be clear, this is not a "no support" tier, but it is not the main focus. You're welcome to ask for help, submit PRs and help out, but please be aware that you may not get a response as quickly as these versions are generally not as popular anymore and may not have as many people around to help. Staff may still choose to work on these legacy versions and help people, but please don't demand it from them. Please note that due to the nature of the old toolchains used for building legacy versions, developing mods using the default MDK may not work. We also cannot easily publish updates to some of these old versions without your help - if you're interested in fixing this, please reach out to us. Minimal supportThis is rare and usually only applies to versions of MC where there's no legitimate reason to be using them. A real-world example of this is 1.20.3, which had a data loss bug that was fixed in 1.20.4 shortly after. All mods made for 1.20.3 work on 1.20.4, so there's no reason to use 1.20.3. We will help you update to the fixed version instead, but that's about it. Which versions are in minimal support?The latest patch version of a given major feature release is the one in full or legacy support, with versions before that in minimal. Some examples: 26.1 and 26.1.1 are minimal support because you should use 26.1.2 instead 1.16, 1.16.1, 1.16.2, 1.16.3 and 1.16.4 -> use 1.16.5 instead For 1.20.x and 1.21.x, Mojang released major feature updates on minor patch versions. The above logic still applies, and you can find out which are hotfixes and which are major feature updates based on Minecraft's release notes, but for convenience here's the versions that are in minimal support and what you should use instead: MC version with minimal support What you should use instead 1.20 1.20.1 1.20.3 1.20.4 1.20.5 1.20.6 1.21 1.21.1 1.21.2 1.21.3 1.21.6 and 1.21.7 1.21.8 1.21.9 1.21.10