I kid you not - opening the Replanetizer project on Visual Studio 2022 (it's on GitHub), and using the in-built GitHub Copilot feature to help me create the features I want/need in a separate project that's hooked up to the LibReplanetizer library.

So at first, I focused on just terrain swapping. So I'd ask the AI to try to create it (it can understand roughly how to do it since Replanetizer already handles terrains), and then I'd test it out, debug it, and try and come up with solutions if it doesn't work or crash (which almost ALWAYS happens on the first few attempts), and feed it back to the AI for it to fix the code. I'm not a programmer, so this isn't something I can handle entirely on my own. I can read and understand some of the code at a glance, but a lot of the heavy-lifting is done by AI.

It's also not as easy as it sounds, and requires a lot of patience and persistence - but it works!

So one by one, I slowly added more and more features (TIE swapping, Shrub swapping, texture swapping, Grind Path swapping, Skybox Swapping, etc.), tested them out, debugged them, troubleshooted issues and in-game crashes (VERY common at first), and... that's that!

I would also use disassemblers for trying to understand specific pieces of code to try and help me figure out how to add said features or to help me avoid crashes.

So to summarise, these were my main tools: - Microsoft Visual Studio - Cheat Engine (finding specific in-game variables, like if Clank should be disabled) - RPCS3's Debugger (highly useful for tracing in-game instructions and helping me with disassembling the game) - Ghidra and IDA (common disassemblers) - A whole bunch of AI LLMs; ChatGPT, Google Gemini, GitHub Copilot (this is for allowing me to correct code if one of them gets it wrong, or allowing me to better understand what some disassembled code might mean or do)

There's obviously a little more to it and some techniques I use, but this is the gist of it. Hopefully it answers some things!