Connector VS architectury-api

Minecraft Version: 1.20.1 Minecraft Version ID: 1.20.1 Operating System: Windows 10 (amd64) version 10.0 Java Version: 17.0.8, Microsoft Java VM Version: OpenJDK 64-Bit Server VM (mixed mode), Microsoft Memory: 255441640 bytes (243 MiB) / 952107008 bytes (908 MiB) up to 6408896512 bytes (6112 MiB) CPUs: 12 Processor Vendor: AuthenticAMD Processor Name: AMD Ryzen 5 3600 6-Core Processor Identifier: AuthenticAMD Family 23 Model 113 Stepping 0 Microarchitecture: Zen 2 Frequency (GHz): 3.60 Number of physical packages: 1 Number of physical CPUs: 6 Number of logical CPUs: 12 Graphics card #0 name: NVIDIA GeForce GTX 1660 SUPER Graphics card #0 vendor: NVIDIA (0x10de) Graphics card #0 VRAM (MB): 4095.00 Graphics card #0 deviceId: 0x21c4 Graphics card #0 versionInfo: DriverVersion=31.0.15.3758 Memory slot #0 capacity (MB): 8192.00 Memory slot #0 clockSpeed (GHz): 2.13 Memory slot #0 type: DDR4 Memory slot #1 capacity (MB): 8192.00 Memory slot #1 clockSpeed (GHz): 2.13 Memory slot #1 type: DDR4 Virtual memory max (MB): 31181.12 Virtual memory used (MB): 10109.26 Swap memory total (MB): 14848.00 Swap memory used (MB): 0.00 JVM Flags: 4 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance\_javaw.exe\_minecraft.exe.heapdump -Xss1M -Xmx6112m -Xms256m Launched Version: forge-47.2.6 Backend library: LWJGL version 3.3.1 build 7 Backend API: Unknown Window size: GL Caps: Using framebuffer using OpenGL 3.2 GL debug messages: Using VBOs: Yes Is Modded: Definitely; Client brand changed to 'forge' Type: Client (map\_client.txt) CPU: Sinytra Connector: 1.0.0-beta.27+1.20.1 SINYTRA CONNECTOR IS PRESENT! Please verify issues are not caused by Connector before reporting them to mod authors. If you're unsure, file a report on Connector's issue tracker. Connector's issue tracker can be found at [https://github.com/Sinytra/Connector/issues](https://github.com/Sinytra/Connector/issues).

Architectury, an API for Multiplatform mod support. Needed for Identity.

Using Architectury is likely the easiest method

Okay, with that out of the way, here's what I believe to be true: There is no such thing as a one-size-fits-all code "translator" or "bridge" that can translate regular Fabric code into something that runs on Forge, or vice-versa, and something like this isn't possible in the way I think you're imagining it. Forge and Fabric work very differently from one another under the hood. There is no library that allows you to write Fabric code that works on Forge, and there probably never will be. However, there are some projects out there that aim to lessen the impact of this problem. Architectury is one of these projects. Architectury can translate some parts of a mod between the two loaders, but the mod still has to be built around it. You can't just add it to a Fabric mod and expect it to run on Forge (or vice-versa). Instead, the mod has to be created with it in mind all the way through. Mods can not be converted between Forge<->Fabric automatically. Manual porting is possible, and mods can be built to run on both loaders, but it is not possible to make a universally applicable "converter".

It has been in pre-Alpha for over a year. It won't be happening any time soon, and will behave like Architectury, but with significantly more abstraction for the modder, if / when completed.