URKit v0.1.2

This release focuses on loader stability, launcher-based games, runtime detection, and safer mod activation.

Highlights

Reworked loader initialization and lifecycle management.
Improved compatibility with launcher-based Unity games.
Added safer process qualification and runtime discovery.
Improved IL2CPP and Mono runtime backend selection.
Hardened module loading against proxy/system DLL conflicts, including version.dll-related failures.
Prevented loader-wide crashes caused by individual mod or hook failures.
Added safer callback and lifecycle guards.
Improved native mod activation and failure reporting.
Added better runtime event handling and unload cleanup.
Preserved append-only SDK ABI compatibility for existing mods.
Added safer metadata and runtime API access checks.
Improved cursor and mouse-capture ownership handling.
Added stronger protection against invalid or corrupted metadata.
Improved diagnostics and logging for loader decisions and runtime initialization.

Existing URKit mods remain compatible with the append-only SDK changes.
Existing Mono and IL2CPP integrations are preserved.
Mods are now isolated more safely during activation and failure scenarios.
Launcher-based games receive more conservative runtime detection and initialization.

A failed mod no longer needs to terminate the entire loader.
Runtime initialization now validates backend availability before enabling hooks.
Native callbacks are guarded against invalid lifecycle states.
Module and runtime discovery failures provide clearer diagnostic logs.

This release changes loader initialization behavior to favor safety and explicit runtime validation.
Mods relying on undocumented internal loader timing may require verification.
Official URKit SDK-based mods should not require source changes.