Kepping Forge 1.20.1 support

We can't support that many version with development resources we have unfortunately

I can understand your decision; the update to Neoforge is certainly beneficial for newer mods. However, it presents a major issue for developers who started their projects on Forge. Many older projects can no longer be continued because Neoforge no longer supports certain features, like removing crafting recipes and some other mechanics.

Please consider finding a way to support both versions—Neoforge and Forge. Alternatively, you could develop a solution to import MDK files from newer Forge versions into Neoforge.

It’s incredibly frustrating to have to rewrite the entire code, as many of us still rely on Forge, especially for Forge 1.21. An update should ideally ensure that older versions remain supported. If this isn’t possible, the update should not have been carried out in this way.

This is my opinion, and I hope you can come up with a viable solution for this.

Alternatively, you could develop a solution to import MDK files from newer Forge versions into Neoforge

I don't think you understand that supporting two modding APIs is not just matter of changing MDK files, but affects most of the files in generator and is enormous project.

If you are interested, you are welcome to develop plugin for Forge version you need, however!

My Current Problem with NeoForge

Currently, I have an issue with NeoForge as it is no longer possible to remove crafting recipes. This is an essential feature for many mods. I urge you to consider reintroducing this functionality or implementing a mechanism that allows crafting recipes to be removed.

In the future, it would be desirable for such fundamental changes to take into account their impact on the community. Many developers and users who are still using Forge might encounter similar problems.

If NeoForge aims to be a long-term solution, I believe it should either:

1. Provide clear instructions on how such functions can be implemented, or
2. Offer alternatives to help developers migrate their mods.

I hope you can take these points into account in future decisions to improve collaboration and compatibility within the modding community.

Feedback on NeoForge and Forge Compatibility

Hello,
I’d like to share an important concern. It’s about the support and development of NeoForge and Forge. In my view, it’s problematic if both mod loaders cannot be kept up to date simultaneously or if no import options between them are provided.

If you cannot ensure that both NeoForge and Forge remain up to date, it would have been better to stick with one system rather than supporting both in parallel. This would avoid unnecessarily complicating things for many mod developers who originally worked with Forge.

It is important that you either:

1. Actively support both platforms (Forge and NeoForge), or
2. Provide options to import projects from Forge to NeoForge to make the transition easier.

Without this support, many mod developers will struggle to continue their projects, leading to frustration in the community—something that could have been avoided.

Provide options to import projects from Forge to NeoForge 

You can switch from one to another in workspace settings ;)