สมัครสมาชิกเพื่อดาวน์โหลด
Combat always collides

That makes sense, thank you for the explanation

Mute,

In current testing state it's remains unclear for me how it will influence my game experience. I just finished 15 days of reactor charging with everyday 2-3 raids engaging. And I can say that "easy" raids more interesting with vanilla collide script. "Hard" raids when half of pawns injured and I need to hold in killbox are in need of your collide script.

As an intermediate conclusion for myself, I realized that in the normal game mode I will use the standard collide script, and in the final phase of the game I will include your collide script.

Idea of toggle is not a necessity in my case. It's just a wish.

Hi Protok,

Runtime patching/unpatching is pretty complex (and the mod doesn't currently have a settings menu), so I'm not sure if I'll be adding such a feature, at least in the near future.

What kind of situation has you looking for a toggle?

Thanks for mod. It would be convenient to have an on/off option in the mod settings. To change the vanilla and modified script on the fly, without restarting.

Updated, thanks for the reports

I'll just chime in and say I'm seeing the same error as of today. The errors in my log are identical to the log that mathan posted.

Can confirm, there's an error on startup now: https://gist.github.com/HugsLibRecordKeeper/90319460a4fec4d659cf5fd7403f1364

yes, it now gives

Error in static constructor of nopawnstacking.Main: System.TypeInitializationException: The type initializer for 'nopawnstacking.Main' threw an exception. ---> HarmonyLib.HarmonyException: Ambiguous match for HarmonyMethod[(class=Verse.AI.Pawn_MindState, methodname=Reset, type=Normal, args=undefined)] ---> System.Reflection.AmbiguousMatchException: Ambiguous match found.

on startup. starting today

Seems to have started giving off a new red error on startup after the latest rimworld update even with just harmony and this loaded.

Thanks so much for the update! Looking forward to trying it out