Подпишитесь, чтобы загрузить
Dimensions RePocketed

If you both want to upload your mod lists to pastebin, I can run them through a comparison and see what you have in common that might be relevant.

To put some information from myself out here:
I dont have the mod "Achtung", so i dont think it can be it or a combination with it.

I'm going to be releasing a patch for this mod soon...I will include a change to return an empty List object instead of null...that will prove whether it solves the problem or not.

@Gideon to answer your question, it happens only when I have one of my pawns selected, and right-click another living pawn. If the pawn I right-click is dead, it does not occur.

Thank you for checking this for me btw. Apparently Achtung has a Github, so I might see about making an account and posting the issue there and see if they can fix it

I think I found the cause.

RimWorld gracefully handles a null. Achtung! doesnt check for a null before it tries to reference properties. Essentially this is happening because if there are no relevant context menu entries, I don't waste RAM and CPU returning an empty List object, I just return null.

A simple check by Achtung! whether a variable is null or not would resolve.

Quick question....does the problem occur when you right-click on a pawn or when you right-click something other than a pawn while you have a pawn selected?

Most likely, given what Acthung! does, it's "taking over" handling of colonist behaviors...that's kinda what it does...so for Achtung! to assert that it's never Acthung! doing something is difficult to back up given that they essentially override references to RimWorld core code.

The thing that concerns me with this output...while it may be true that Achtung! doesn't modify context menu items themselves, the stack trace from your output indicates it very much did modify my method's behavior indirectly...my method has a signature that looks like this:

public override IEnumerable<FloatMenuOption> GetOptionsFor(Pawn target, FloatMenuContext context)

I take 2 inputs--Pawn and FloatMenuContext. Neither of these references AchtungMod.Colonist, which means somewhere within ActhungMod is a Harmony patch that's forcing my mod to dereference Pawn and instead get handled by ActhungMod.Colonist.

@Gideon yeah, I agree that saying "oh it's never my mod" is kind of an arrogant statement. Achtung even has comments disabled so I can't even reach out to the author there. However I've been using Achtung since 2017 so it's kind of hard for me to just drop it at this point.

Unfortunately I have 0 knowledge with modding so the best I can do is provide logs and hope someone can let me know where the issue is.

However since I've had 0 issues with Achtung until I installed Dimensions Repocketed (I've even used the original Pocket Dimensions mod for years, along with Achtung, with 0 issues), I'm assuming it's either an incompatibility between Dimensons Repocketed and Achtung, OR it's an incompatibility with Dimensons Repocketed and another mod I have, and Achtung is just reporting it.

Without knowing what other mod might have issues with Dimensions Repocketed, and Achtung not allowing comments, my only option is to post my issue here and hope someone can figure it out :(

Good morning. This mod does have a menu item generator (FloatMenuOptionProvider_CarryToPocket). I don't have Achtung! installed, and the context menu works fine for me without errors. I'm always wary of any modder claiming errors that reference their mod are "never my mod"--this kind of response tells me the modder doesn't want to put any effort into actually reviewing the content and isn't open to the idea that they, like everyone else in the community, are imperfect and can have bugs, too. This mod has had zero testing with Achtung!, so I can't give a compatibility statement with that mod.