Skip to content

Why?

I’ve been modding games for a long time, and there’s a pattern I keep running into. Every new project starts with rewriting the same plumbing. A hooking library, a signature scanner, a way into the game’s present call, an overlay that doesn’t fall over when the game resizes, input that doesn’t leak through to the game while you’re typing in a text box…

And it’s not like the pieces don’t exist. There’s a hooking library here, an ImGui backend there, an injector somewhere else, each with its own ideas about threads, lifetimes and who owns what. Getting them to work together, and to unload cleanly, ends up being most of the work.

Or you skip all that by building on a game-specific ecosystem like Dalamud, SKSE or BG3SE. That’s great right up until you want to mod a different game.

A lot of the best tools for this have gone commercial, with the useful parts behind a paywall or a subscription. That’s their call to make, but it means learning how games work, or making a small mod for one you love, costs money it shouldn’t.

I’d rather the basics were free and open, for anyone, and that the tools you learn on are ones you can read the source of.

Ratatoskr is my attempt to stop doing all that.

  • Tuft is the generic toolkit underneath. Everything you need to get inside a game and do things there, none of it tied to a particular one.
  • Salamander is how the pieces talk. One schema format for game types and APIs, shared by every language.
  • Wraith is the framework on top. The loader, the overlay, the Workbench, tweaks and plugins in whatever language suits you, and the app that puts it in your games.

All of it is open source. See Commercial use for how the licenses work.

Made with ♥ by Asgard