RimWorld

RimWorld

RimTalk
NullReferenceException after latest update (FloatMenuMakerMap.GetOptions conflict)
Hi,
After the latest update, I started getting this error when right-clicking on the map:

Exception in RimWorld.Selector.HandleMapClicks: System.NullReferenceException: Object reference not set to an instance of an object
[Ref AF6CA0]
at RimWorld.FloatMenuMakerMap.GetProviderOptions (RimWorld.FloatMenuContext context, System.Collections.Generic.List`1[T] options) [0x00000] in <24d25868955f4df08b02c73b55f389fe>:0
- TRANSPILER net.pardeike.rimworld.lib.harmony: IEnumerable`1 VisualExceptions.ExceptionsAndActivatorHandler:Transpiler(IEnumerable`1 instructions, MethodBase original)
at RimWorld.FloatMenuMakerMap.GetOptions (System.Collections.Generic.List`1[T] selectedPawns, UnityEngine.Vector3 clickPos, RimWorld.FloatMenuContext& context) [0x0012e] in <24d25868955f4df08b02c73b55f389fe>:0
- POSTFIX co.uk.epicguru.meleeanimation: Void AM.Patches.Patch_FloatMenuMakerMap_GetOptions:Postfix(Vector3 clickPos, List`1 selectedPawns, List`1 __result)
- POSTFIX cj.rimtalk: Void RimTalk.Patch.FloatMenuPatch:Postfix(List`1 selectedPawns, Vector3 clickPos, FloatMenuContext context, List`1& __result)
at RimWorld.Selector.HandleMapClicks () [0x000b8] in <24d25868955f4df08b02c73b55f389fe>:0
- TRANSPILER net.pardeike.rimworld.lib.harmony: IEnumerable`1 VisualExceptions.ExceptionsAndActivatorHandler:Transpiler(IEnumerable`1 instructions, MethodBase original)
- PREFIX SmashPhil.VehicleFramework: Boolean Vehicles.Patch_Misc:MultiSelectFloatMenu(List`1 ___selected)

I already tested with a new save, and the issue still happens.
It seems to appear right after the latest mod update.
From the stack trace, it might be related to a missing null check for FloatMenuContext or selectedPawns inside the Postfix patch.

Could you please check if something changed in the FloatMenu handling recently?

Thanks!
< >
Showing 1-2 of 2 comments
Juicy  [developer] 2 hours ago 
Thanks for the report.

From the stack trace, it doesn’t look like the error is caused by RimTalk. The exception happens before RimTalk’s postfix runs. Could you try removing RimTalk and see if the issue still occurs?
< >
Showing 1-2 of 2 comments
Per page: 1530 50