RimWorld

RimWorld

Moody
Bug - Moody may causing title to fail?
I had twice issue where game has failed somewhere horribly - it cause visible screen bleed and afterward UI become unresponsive. It required loading previous save state to continue.

In the game log I can find the following:
[Ref CEB0AEF5] Duplicate stacktrace, see ref for original
Root level exception in OnGUI(): System.NullReferenceException: Object reference not set to an instance of an object
[Ref F36E69B] Duplicate stacktrace, see ref for original
Exception filling window for Moody.MoodyWindow: System.NullReferenceException: Object reference not set to an instance of an object
[Ref CEB0AEF5] Duplicate stacktrace, see ref for original
Root level exception in Update(): System.NullReferenceException: Object reference not set to an instance of an object

Video with the issue:
https://youtu.be/MC3aYDhC1MA

Has anyone seen anything like that or got more coding knowledge to help with resolving?
< >
Showing 1-8 of 8 comments
Giant Space Hamster  [developer] 15 Jul @ 3:27pm 
Do you have any more of the log file or steps to reproduce the error? Unfortunately, without either of those things there is not much I can do. The piece of the error log you posted is not really useful.
Papart 15 Jul @ 11:31pm 
I have full log, but it's hefty so even paste bin is not able to get it - if you can let me know where it be best to upload if for you.

Sadly so far no repro steps - I was trying to reproduce with same actions but to no avail. I do wonder if it might have with game upkeep, as I do think it was after a longer game session (3+ hours).
Giant Space Hamster  [developer] 15 Jul @ 11:45pm 
Google drive and dropbox are a couple options that have larger file size sharing limits. They would both require an account.
Giant Space Hamster  [developer] 16 Jul @ 4:58pm 
Thanks, that is helpful. It looks like there's another error right before the Moody one. It looks like that error occurred while processing a colonist's job. From what I can tell, a new job is being started and an old job is being told to stop. Do you happen to recall if the issue occurred right after manually telling a colonist to do some task that would have interrupted an existing task?

I see Vanilla Traits Expanded referenced in the error stack, as well as Pick Up And Haul, but that doesn't necessarily mean those are the cause. Unfortunately the logs don't include what the job is. I suspect this put something in a bad state that then triggered the Moody error as a side-effect.

I will look at Moody's general error handlers and see where this is getting through. I should be able to at least prevent this from causing Moody to exacerbate the problem. I might not get to it immediately, but I should be back in RimWorld soon.
Papart 18 Jul @ 1:15am 
Cheers, that is lot of info. I don't think that log from this occurence was when I was doing any manual action for pawns and looking at the video, I just let them go - however I have a feeling that I changed some of the storages settings mid-job so I will try to see if I be able to reproduce it or if I encounter it again, I get longer video and analyze what was happening with the pawns.
I have the same problem...
I'm using perma mode, so I don't have the original safe file where the problem happened. Since the game saves everytime I close...

Everything worked fine yesterday and Moody was one of the few modes that had an update today.
Sorry I don't have a logfile, but thought one person more saying I have the problem might be worth something.


For me it happened after I added disable mechanics in a workbench.
Giant Space Hamster  [developer] 19 Jul @ 3:15pm 
Can you provide the game log please?

The update yesterday should have reduced any impact to the row in moody for whichever pawn is triggering the error from not displaying rather than causing additional side-effects. Are you seeing one (or more) rows not display? Or is the issue causing additional side-effects?
Last edited by Giant Space Hamster; 19 Jul @ 3:18pm
< >
Showing 1-8 of 8 comments
Per page: 1530 50