Presence Footsteps [Forge] for Minecraft

I've ported various small-ish Fabric mods to Forge for personal use in the past, with each port learning more efficient methods along the way.

With Presence Footsteps, I did the following procedure:
1. Clone the repo of the Fabric mod to port
2. Get the Forge MDK, setup Mixin configs and Yarn2MCP's Yarn mappings
3. Use the updateMappings ForgeGradle command to convert Yarn to MCP
By this point a decent chunk of the work was already done!
4. Use the Linkie Discord bot to manually translate the remaining Yarn classnames to MCP classnames, along with translating some Mixin stuff
5. Manually translate Fabric-specific APIs and practices to Forge-equivalents (e.g. separate event systems, separate ways of initialising the mod, etc...)

Notes regarding the port:
- Next time I'll might try using MojMap as the intermediary translation mappings instead of Yarn2MCP, to reduce setup time and allow for flexibility between using either ForgeGradle's updateMappings or Loom's migrateMappings commands. I didn't use them this time because last time I checked, Linkie didn't support translating between MojMap and MCP but this seems to have been resolved now.
- I did try running the code in Yarn2MCP's Yarn mappings directly before conversion to MCP, however due to a mapping error this was unfortunately not possible.
- The mod makes use of some Fabric-only mod libs so I had to also port over the parts that were used. I had a bit of trouble with one particular function in the lib having the same name as an MCP method name causing a compile error due to ambiguity over which method the code was referring to (it was to do with tooltip rendering for buttons in the GUI lib iirc). For now, I've just disabled that one method call as a workaround.
- I recall the dev saying that they didn't like MCP mappings, but funnily enough I found various instances of variable names matching the MCP classnames rather than Yarn ones. Maybe it was just reused code from the LiteLoader days? Who knows...
- It's not my most elegant solution - I was bored so I still did some of it manually by copying over the lib stuff after the updateMappings automation.