Incompatibility issue with Phoenotopia: Awakening causes crash

[Amphyros]

Hi, since version 0.28 there has been an issue with loading UMM in Phoenotopia: Awakening. This is the error from the output file we get after launching the game:

[Manager] Injection...
[Manager] Initialize.
[Manager] Version: 0.30.1.0.
[Manager] OS: Microsoft Windows NT 10.0.19045.0 x86.
[Manager] Net Framework: 2.0.50727.1433.
[Manager] Unity Engine: 5.6.51.
Platform assembly: E:\SteamLibrary\steamapps\common\Phoenotopia Awakening\PhoenotopiaAwakening_Data\Managed\System.Xml.dll (this message is harmless)
[Manager] Game: Phoenotopia Awakening.
[Manager] IsSupportOnSessionStart: False.
[Manager] IsSupportOnSessionStop: False.
[Manager] Mods path: E:\SteamLibrary\steamapps\common\Phoenotopia Awakening\Mods.
TypeLoadException: Could not load type 'MonoMod.Logs.DebugLog' from assembly '0Harmony, Version=2.3.1.1, Culture=neutral, PublicKeyToken=null'.
  at MonoMod.<027f1d0e-6e0b-4adc-bc2b-a5d0603c6ea8>MMDbgLog.Log (LogLevel level, System.String message) [0x00000] in <filename unknown>:0 
  at MonoMod.<027f1d0e-6e0b-4adc-bc2b-a5d0603c6ea8>MMDbgLog.Info (System.String message) [0x00000] in <filename unknown>:0 
  at MonoMod.<027f1d0e-6e0b-4adc-bc2b-a5d0603c6ea8>MMDbgLog.LogVersion () [0x00000] in <filename unknown>:0 
  at <Module>..cctor () [0x00000] in <filename unknown>:0 
Rethrow as TypeInitializationException: An exception was thrown by the type initializer for <Module>
  at UnityModManagerNet.Fixes.Apply () [0x00000] in <filename unknown>:0 
  at UnityModManagerNet.Injector._Run (Boolean doorstop) [0x00000] in <filename unknown>:0 
  at UnityModManagerNet.Injector.Run (Boolean doorstop) [0x00000] in <filename unknown>:0 
UnityEngine.DebugLogHandler:Internal_LogException(Exception, Object)
UnityEngine.DebugLogHandler:LogException(Exception, Object)
UnityEngine.Logger:LogException(Exception, Object)
UnityEngine.Debug:LogException(Exception)
UnityModManagerNet.Injector:Run(Boolean)
UnityModManagerNet.UnityModManager:OnLoad(Object, AssemblyLoadEventArgs)
System.AppDomain:DoAssemblyLoad(Assembly)

Downgrading to v0.27.9b is the workaround for now as it seems that the error starts appearing at v28 and above.

[newman55]

Fixed in 0.30.1a