Messages

I added a check for both Fog of Torment and Disabling Shot, both of these abilities add vomit in the hediff they add.
Oh, zombies will now get healed inside the fog of torment, just like undead.

Thanks!

Mod compatibility bug report:
I am playing with this mod and Zombieland which works pretty well except for a Projectile_FogOfTorment seems to have made a zombie vomit. And as zombies are stripped down pawns they don't have needs and therefore the default vomit job fails when adding more hunger to the zombie.

Could you add a check for if the target pawn has the hunger need (or any needs at all) before adding the vomit job?
More debug info can be found on my initial bug report to zombieland

I encountered one of the errors you have regarding ZombieLand. The error is that something has caused a zombie to become sick and wants to vomit and in doing so default rimworld behavior is to make pawns 4% more hungry each vomit. But zombies don't have hunger and therefore fails. If you simply delete the vomiting zombie (the vomit is created before the error) the error goes away.

In my case it is A Rimworld Of Magic that caused the vomiting and I am currently in the process of working out a bug report with a fix.

I uploaded the files to restore the old raid sound on steam workshop http://steamcommunity.com/sharedfiles/filedetails/?id=1220235375 .

That could work. Better yet go after your current tech level. Neolithic etc.

Anyone know how to restore the previous raid sound?

-Edit a few hours later-
Well i think i solved it now using the information from here https://www.reddit.com/r/elderscrollslegends/comments/62jv73/guide_extract_all_picturesaudio_files_from/ and looked at the file structure from http://steamcommunity.com/sharedfiles/filedetails/?id=1127520441 to extract the old sound from a17.

To remove everything just seems like a dick move to me. It takes more effort to remove the mod from the internet than to just let it remain on github and for someone else to keep working on it.

Really stupid in my opinion, but then again I have never understood people who actively work against letting others continue using it as open source.

I was using two mods that conflicted and found an issue which I think should have been caught on mod loading.

The problem seems to boil down to the fact that one apparel had <commonality>0.0</commonality>.
And that lead to an error, on generating apparel for a mechanoid unit in another mod.
From what I understand the modder should have removed the commonality row instead of having it as zero.

My suggestion is to look for this on apparel loading and output a warning or error if an item has a commonality of 0 to help avoid this issue.