Oxidizer

A mod loader for Kitten Space Agency, written in Rust. Mods can be written in Rust (cdylib) or as Rhai scripts.

KSA is a .NET 10 game, so the loader:

1. loads the game's own hostfxr.dll and starts its runtime with KSA.dll,
2. injects bridge/ (a small C# DLL plus Harmony), which hooks Program.OnFrame, Program.OnDrawUiViewports and the game's menu bar, and gives mods reflection access to game objects,
3. loads the mods, then runs the game's Main.

In game, Mods > Oxidizer in the menu bar opens a window that lists the loaded mods, their errors and the log.

Install

1. Download Oxidizer-vX.Y.Z.zip from Releases and unzip it anywhere.
2. Run oxidizer.exe. If KSA isn't installed at the default path, set game_path in the oxidizer.toml it creates next to the exe.
3. To try the examples, copy the folders from example-mods/ into Documents/My Games/Kitten Space Agency/mods/.

Build

dotnet build bridge -c Release -o target/bridge
cargo build --release --workspace

Run

target/release/oxidizer.exe [--game "<KSA folder>"] [-InstancePath "<folder>"] [game args...]

On first run without --game, the loader creates oxidizer.toml next to the exe (game_path = '...'). It defaults to C:\Program Files\Ahwoo\Games\Kitten Space Agency.

-InstancePath, or the OXIDIZER_INSTANCE_PATH environment variable, makes the game use that folder instead of Documents/My Games/Kitten Space Agency for mods, saves and settings. Mod managers such as Borea use it for separate game profiles.

Mods

A mod is a folder in Documents/My Games/Kitten Space Agency/mods/<id>/ whose mod.toml has a [oxidizer] section:

name = "my_mod"

[oxidizer]
dll = "my_mod.dll"      # Rust mod
script = "main.rhai"    # and/or Rhai script

Mods set enabled = false in KSA's manifest.toml are skipped. See examples/ for working mods. To install one, copy its folder into mods/; for a Rust mod, also copy in the built .dll.

Rust

The crate is a cdylib that depends on oxidizer_api. Mod has init, frame, gui, menu (entries in the game's Mods menu) and unload; all but init are optional.

use oxidizer_api::{Mod, Obj, imgui};
struct M;
impl Mod for M {
    fn init() -> Self { M }
    fn gui(&mut self, _dt: f64) {
        if imgui::begin("My mod") {
            let v = Obj::static_get("KSA.Program, KSA", "ControlledVehicle");
            imgui::text(&v.get("Id").to_string());
        }
        imgui::end();
    }
}
oxidizer_api::oxidizer_mod!(M);

Rhai

A script can define init(), frame(t, dt), gui(dt), menu() (entries in the game's Mods menu) and unload(). Keep state in this (an object map).

Scripts reload while the game runs: save the file and the new code takes over within a second. this is kept, init() doesn't run again, and reload() runs if the script defines it. If the new version doesn't compile, the old one keeps running and the error shows in the Oxidizer window.

Notes and limits

• Members are looked up by name through reflection. Type names can be assembly-qualified ("KSA.Universe, KSA"), which works even before the game has loaded that type.
• call picks the first overload with a matching argument count and converts arguments to the parameter types.
• Patching uses the first overload of the method. Hooks receive __instance and __args, but not __result.
• A Rhai script that throws an error stops until its file is saved again, so the same error isn't logged every frame. Errors from reflection calls are logged once each.
• ref struct members (for example ReadOnlySpan properties such as Program.VehiclesInFrame) can't be read through reflection.