Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem






That the interaction spots overlap was something i done, so that is fine.
Do you have any other mods that change how rituals work?
I've checked the logs (both normal and dev-mode verbose) and there's no errors or anything unusual relating to this mod, and nothing at all is logged when I start the ritual.
So have not testet it, so let me know if it works if you try it :)
Do it make errors? or do you have any other mods that to affect this?
I did change a lot in the code.
Exception filling window for RimWorld.Dialog_BeginRitual: System.NullReferenceException: Object reference not set to an instance of an object
[Ref 11F61CAF] Duplicate stacktrace, see ref for original
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Log.Error_Patch1 (string)
Verse.Window:InnerWindowOnGUI (int)
UnityEngine.GUI:CallWindowDelegate (UnityEngine.GUI/WindowFunction,int,int,UnityEngine.GUISkin,int,single,single,UnityEngine.GUIStyle)
You may see red errors first time after using the update. try delete the comm console and rebuild it.
A few larger fixes, allies that join you in drop pods no longer triggers the jammer and crash.
There was a bug before where you never failed the ritual, it works now, so you will now fail sometimes.
Fixes that some It should also stop Mechs from center drop now, unless its added by another mod.
✅ Conclusion:
The line in the log mentioning [Drop Pod Raid Jammer, UnityEngine.IMGUIModule.dll] is misleading. It only shows that Unity was drawing the debug window while your mod (and many others) were loaded. The actual null error comes from a different mod’s broken def. Your mod is not the cause.
But you do have some other bugs in the mod log also.
I click on do incident (map), sometimes it pops the debug log and sometimes it allows me to sumon incidents but its random.
And what event were you trying to make?
exception getting label for DebugActionNode: System.ArgumentNullException: Value cannot be null. Parameter name: type
Each button in the debug menu is a DebugActionNode. To display it, the game calls get_LabelNow().
One of those debug actions was registered with a null type, so when RimWorld tries to ask “what’s your label?” → boom, ArgumentNullException.
The stack trace shows:
LudeonTK.DebugActionNode — RimWorld’s internal debug system.
Drop Pod Raid Jammer mod shows up at the bottom → which suggests that this mod (or something it depends on) added a debug action incorrectly.