Considereing isssues with Sedna to be fixed, can you use something like Architectury (for Forge and Fabric)?

[ajh123]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

It would be hard for you to maintain two separate branches for a Fabric and one for Forge. Since you need to update to newer Minecraft versions this is a good reason to switch to using Architectury.

Describe the solution you'd like A clear and concise description of what you want to happen.

Migrate to Architectury. Architectury allows you to have one loader independent "common folder" for code that is the same across versions and have multiple "folders" for each loader. Each loader specific "folder" will have code that will be used for starting up the mod. This means about 90% of the mod will be inside the "common folder" which will make it easier to maintain two separate versions because they are the same.

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Some people have problems with the Architectury API, however Architectury can be used without the Architectury API, for example you could use Registrate and Porting Lib instead (these are what Create uses and my own mod). https://github.com/Fabricators-of-Create/create-multiloader-addon-template/tree/1.20.1 is a template which shows you how to do this.

Additional context Add any other context or screenshots about the feature request here.

https://github.com/fnuecke/sedna/pull/19 looks like good progress.