Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
freem
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Openai/696e303b-9f9c-8001-b1df-6fcfc3f35a2c
(section)
Add languages
Page
Discussion
English
Read
Edit
Edit source
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
Edit source
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Assistant: Yep, this one’s very clear — and it actually confirms the Pawnmorpher / HAR removal fallout. === Yep, this one’s very clear — and it actually confirms the Pawnmorpher / HAR removal fallout. What’s happening, in human terms: Exception ticking Grave343351 RimWorld is trying to tick a specific grave every game tick. Graves tick because they may: * Contain a corpse * Track decay * Track ideology thoughts * Interact with rituals, memories, or comps added by mods Inside that grave is something that no longer exists as a valid object. Usually: * A corpse of a pawn whose race def is gone (HAR classic) * A corpse with Pawnmorpher hediffs that no longer resolve * A comp attached to the corpse that was defined by a removed mod So when the grave asks: “Hey, corpse, how are you decomposing today?” The corpse answers by not existing at all. Null reference. Every tick. Forever. This is not dangerous to the save structurally, but it will spam errors and can tank performance over time. Now the practical fix — and this one is mercifully simple. ===== Delete the offending grave. ===== Steps: # Enable Dev Mode # Open the debug actions menu # Use “Destroy” or “Destroy (force)” # Click the grave at (110, 0, 105) That instantly removes the ticking object and the error should stop immediately. Lore-wise: the colony quietly pretends they lost track of that burial. RimWorld shrugs and moves on. ===== If you want to preserve something: ===== * Open the grave * If possible, remove the corpse * Then destroy the corpse with dev tools * Leave the empty grave This sometimes works, sometimes the UI itself errors — depends how broken the corpse is. ===== If you start seeing: ===== Exception ticking GraveXXXXX over and over with different IDs, then you have multiple corrupted burials. At that point: * Use dev mode → “Destroy all graves” (if available), or * Manually delete the affected ones as they error Not pretty, but effective. ===== Just for understanding, not saying you must: ===== The corpse likely references a race like Alien_RaceDef_Something. Reinstalling HAR would make that reference valid again, so the grave can tick normally. You’ve chosen the purge-the-evidence route instead, which is totally valid. ===== - This error is localized (one object) ===== * It is not spreading * It is 100% consistent with removed mods * Fixing it does not require a new save Think of this save as haunted by a few unresolved ghosts. Exorcism works better than archaeology here. Go ahead and delete the grave, then feed me the next error log if anything else screams.
Summary:
Please note that all contributions to freem are considered to be released under the Creative Commons Attribution-ShareAlike 4.0 (see
Freem:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)