c-of-time VS ctru-rs

I initially made this project to help with reverse engineering and research, and it's led to things like a damage calculator and a dungeon layout generator. But as the SkyTemple community can attest to, it's also proven very useful for ROM hacking. Whenever you want to make fundamental changes in a ROM hack that can't be done through more basic means, your only option is to directly modify the code yourself, and it turns out that having a big collection of debug info is super useful for that. People in the community frequently use it to write assembly patches, and we even have a way to write mods in C and Rust using the debug info! It's not quite a decompilation project, but it's probably a good step towards one.

That's really interesting. I've used a tools to write code on ds before, for injecting code in a game thanks to Rust Of Darkness, and I have to say it was quite pleasant (even thought it didn't totally avoided assembly, it was now just putting some calue in some register then call the Rust functions. Definitively better than just assembly. Or C.). Maybe your tool have some usefull stuff that'll interest the author. I'll share this with him (assuming he didn't found this yet). Also, here is the tools, in case you're curious. https://github.com/skytemple/c-of-time/tree/main/rust

Oh hey cool project! I'm working with some folks on Rust for the 3DS here: https://github.com/rust3ds/ctru-rs/

There are two crates which I would recommend. There is the official ctru-rs that is a safe wrapper around bindings for the C library libctru.

My contributions to rust3ds got me interviewed with microsoft, though I ultimately wasn't selected for the position. Then a few months later that same project got me in the door with a different company that did end up hiring me.