Dev mode issues since update

[Son of Jaws]

love the new content and keep up the good work. however iv noticed that the developer mode and the spawning tools seem to be acting up for me since the update. debug log is as follows

Exception filling window for Verse.Dialog_DebugActionsMenu: System.NullReferenceException: Object reference not set to an instance of an object
at Verse.DebugThingPlaceHelper.IsDebugSpawnable (Verse.ThingDef def, System.Boolean allowPlayerBuildable) [0x00067] in

and

Mouse position stack is not empty. There were more calls to BeginScrollView than EndScrollView. Fixing.

I use rimworld and the devmode as a map maker for some RPG stuff and kinda need the dev modes spawn function to make some stuff. Im assuming this is mod related but before i start turning things off 1 by 1 to see what fixes it i figured id check and see if anyone else has had a similar issue.

cheers and have a good day.

[Night]

i also had the same issue as i tried removing version mismatched mods re-downloading my entire mod list and the game itself so far nothing worked now i need to find out whats bad by removing mods 1 by 1 the same as you

[Riven Caith]

If any of you find the culprit, would you please share your knowledge? I have the same issue :'D

[Night]

it's the DiceOfDestiny mod

[Riven Caith]

Originally posted by Night:

it's the DiceOfDestiny mod

Uh-oh. In that case there are more mods that generate this error since I've never even heart of the Dice of Destiny mod : /

Maybe I'm using a mod that does something similar, thus generating the same errors.

---- edit ----

After careful examination I came to the conclusion that I'm not using mods that do anything like the Dice of Destiny mod, at ALL. I'm more confused than before now.

[Night]

the dice of destiny mod messed up trying to open the dev mode now i have the place spawn item problem

[Riven Caith]

Originally posted by Night:

the dice of destiny mod messed up trying to open the dev mode now i have the place spawn item problem

So you still get the same errors as stated in Son of Jaw's post whenever you try to place something via dev mode? Are we sure that it's a mod problem and not something the latest patch caused? I can't check because I'm not at home at the moment.

[Night]

its some mod as base game its fine

[Riven Caith]

Found the faulty mod. After disabling "VGP Garden Fabrics" the error messages preventing me from placing items via dev mode disappeared. As well as some startup errors mentioning Blizzarisk silk (so alpha animals is involved in it too to some extend but does not do anything shifty after Garden Fabric was disabled)

--- edit ---

Alpha animals creator is aware of that incompatibility with VGP and will upload a new version soon.

[Night]

there seems to be other mods as well as i don't have VGP Garden Fabrics so maybe more incompatibility's

[Son of Jaws]

yeah so in the end it was the practice target mod. Im running a few mismatched ones but usually they run fine. practice target was the only mod that even when working, was still missing textures n such.

[Black Starkitten]

So I am having the same issues but do not have any of the mods you all said

[Jatts]

I am also having the same issue, and do not have any of the mods mentioned here

[Son of Jaws]

id probably just start going over your mods and grouping them. my usual trouble shoot method takes a bit but it tends to help.
Going over mods that come in groups like the vanilla expanded stuff. assume they function as they are usualy up to date and are developed well.
then id go over any other major game play changing mods but are stand alone. some times people make the mods and dont update them for latter and it can cause issues. older mods that might say they support the game might not actually or just collide with other mods.
then id probably turn off all cosmetic and small changing mods. usualy its not cosmetic stuff but a missing file or texture can cause the issue.
Id go over your mods and turn them off in these 3 groups and once the problem is gone, you can narrow it down to which group of mods is causing the issue. from there its not to hard to go over most reliable to least reliable. again dividing that group into 3 separate groups and turning them on and off until you find the error occurring. eventually you can narrow it down to like 2 or 3 mods that might be giving you ♥♥♥♥ but at that point its an easy fix. disappointingly you might have to can the mod thats causing the issue. but lucky for you the rimworld community is really good at pumping out good ideas in mod form so take a look and see if you cant find a similar or more up to date version of the mod your trying to kill once you have found it. good luck