Summary
After the KSA 2026.6.9.4750 update (which updated the bundled Brutal framework packages), the published KittenExtensions v0.4.0 build crashes the game at startup for anyone who has the mod enabled.
Symptom
StarMap aborts during mod load with:
MissingMethodException: Method not found: 'Void Brutal.Logging.LogCategory.Debug(System.String, System.String, System.String, Int32)'
(the stack ends in StarMap.GameSurveyer.RunGame). Because it is an unhandled exception during the mod survey, it takes down the whole startup, not just KittenExtensions.
Root cause
The new Brutal changed the LogCategory logging methods. The first parameter of Debug/Info/Warning/Error went from string to an interpolated-string-handler type (Brutal.Logging.Internal.LogString<T>):
// old
void Debug(string message, [CallerMemberName] string, [CallerFilePath] string, [CallerLineNumber] int)
// new
void Debug(LogString<Debug> message, [CallerMemberName] string, [CallerFilePath] string, [CallerLineNumber] int)
The v0.4.0 binary still calls the removed Debug(string, ...) overload, hence the MissingMethodException at JIT time.
Fix: just a rebuild
The current master (0665a04, == v0.4.0) compiles cleanly against the new game.
Since KittenExtensions.props resolves the references from the local install via $(KSADir)Brutal*.dll, a rebuild on an updated KSA should automatically link the new Brutal, and the call sites re-bind to the new Debug(LogString<T>, ...) overload (the implicit string conversion handles existing Log.Debug("...") calls).
Verified locally: rebuilding unchanged master against KSA 2026.6.9.4750 produces a DLL whose IL calls the new LogCategory::Debug(valuetype ...LogString...) overload, and the startup crash is gone.
Could you please cut a new release built against current KSA?
Thank you! :)
Summary
After the KSA 2026.6.9.4750 update (which updated the bundled Brutal framework packages), the published KittenExtensions v0.4.0 build crashes the game at startup for anyone who has the mod enabled.
Symptom
StarMap aborts during mod load with:
(the stack ends in StarMap.GameSurveyer.RunGame). Because it is an unhandled exception during the mod survey, it takes down the whole startup, not just KittenExtensions.
Root cause
The new Brutal changed the LogCategory logging methods. The first parameter of Debug/Info/Warning/Error went from
stringto an interpolated-string-handler type (Brutal.Logging.Internal.LogString<T>):The v0.4.0 binary still calls the removed
Debug(string, ...)overload, hence the MissingMethodException at JIT time.Fix: just a rebuild
The current
master(0665a04, == v0.4.0) compiles cleanly against the new game.Since
KittenExtensions.propsresolves the references from the local install via$(KSADir)Brutal*.dll, a rebuild on an updated KSA should automatically link the new Brutal, and the call sites re-bind to the newDebug(LogString<T>, ...)overload (the implicit string conversion handles existingLog.Debug("...")calls).Verified locally: rebuilding unchanged
masteragainst KSA 2026.6.9.4750 produces a DLL whose IL calls the newLogCategory::Debug(valuetype ...LogString...)overload, and the startup crash is gone.Could you please cut a new release built against current KSA?
Thank you! :)