Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It looks like the WVC author is aware of the problem and planning to rework that option entirely later.
I did just try and create a new world with just Rimworld, all DLC, Harmony, and XML Extensions, and it seems to be working fine. Sorry for accidentally thinking it was directly this mod causing issues!
I think it might actually be an issue between WVC Tweaks and Patches and XML Extensions, since I've been using *just* WVC Tweaks and Patches lately and had no issues, but every time I've tried adding back in XML Extensions, something goes awry with the GravshipLaunch ritual in RitualBehaviors.xml breaking everything else. I'll report this to the WVC author!
The error you cited is from a file called Ritual_Behavoirs.xml, which is not a file in this mod. There is an error prior to that that references this mod, but it's just this mod reporting an issue with a PatchOperation from another mod, that being WVC Tweaks and Patches. And in fact, that exact error is literally the first comment reply on WVC Tweaks and Patches, incidentally.
And frankly, that's how nearly all errors that are attributed to this mod work: they aren't an error in this mod, they are an error in the mod that utilizes this one as a dependency.
Do you have a log from trying to generate a world where it's just this mod enabled?
I think it may be related to the following error I was seeing:
Exception loading def from file Ritual_Behaviors.xml: System.ArgumentException: Exception parsing Verse.IntRange from "-0.7" ---> System.FormatException: Input string was not in a correct format.
This led to the GravshipLaunch ritual missing and it caused a complete breakdown of the Ideology generator on my end, which broke faction generation.
That error was only showing up when I had XML Extensions enabled, removing it removed the error.
Below is my logs from when I was trying to diagnose my issue in case it helps (yes I know its a lot of mods, but it is stable enough for my purposes)
https://gist.github.com/HugsLibRecordKeeper/f5d5abf46545f2e90ef89fda377f5747
i did run xml by itself and the base game to see if there was some issue with another mod and the problem persisted.
all mods i'm using are updated jacstool is being run by someone else as jacs quit modding.
Could you explain what you mean by your factions disappeared? I am not sure what I am looking for. I'll try to replicate the steps you took.
the exact mod order using rimpy
harmony
core
royalty
ideo
biotech
anomaly
odyssey
huglib
Athena
community framwork
dubs proformance
fps stabilizer
frame rate controller
no debris
no job author
optimization leather
optimization meat
performance optimizer
psychic emanator effect off
graphic setting +
jecstools
and that all plus xml but since i got rid of it i don't know where it would be but this is the mods i had on when i found out it was xml sorry if it isn't what you wanted but it what i had left when searching for the issue
my best guess is that 1.6 is the cause as this mod worked fine in the past maybe 1.6 change something in the code that broke this mod?
This mod only provides patch operations and UI code for settings menus, it does not touch any game content. If it is somehow affecting the game, let me know.
and the thing is i know that this mod didn't used to do that in the past because it was one of my staple mod for years so it a fairly recent issue
Also, instead of checking one at a time, it is faster to do a binary search. You remove half of your mods and see if it fixes the problem. If not, then the offending mod is currently active; and if it did fix it, then you know the mod was in the removed list. You then load the list that contains the offending mod, and remove half of those again to determine which half contains the mod. Keep repeating until you find the mod.
But thanks for your answer. :)
If this mod were to have a bug, it would only happen while in a settings menu, or an error could be thrown as soon as the game boots up which will mention this mod's name.
Is this a thing that could be plausible?
This mod is simply a collection of patch operations, which means it doesn't actually run any code during the game. And the other mod is a collection of patches for power armor. Neither mod affects quests or caravans.
I have contacted the author of the armor mod to see if they might know more from their side. In the meanwhile you can keep troubleshooting without this mod or the TSIND mod to see if it still occurs. If so, then it is likely a different mod causing the issue. I would imagine it would be related to some quest mods you have installed.
in theory (and with a bit of luck), you can pinpoint which mod in about 8 attempts (but usually about 10 or so) :)
TLDR : split modlist in half (but keeping dependencies etc), and if issue goes away, conflicting mod(s) were in the batch you removed.
or, if mod conflict still persists, conflicting mod is most likely in the remaining modlist. etc)
Had two errors for System.Threading.ThreadAbortException. Full error log posted in bug reports.
Deleting this mod archive and resubscribing fixed it immediately. Could be Rocketman as well but updating this mod cleared it up instantly and allowed me to play again, praise be.
Thanks for your quick effort and continued support. Take care!
Unsubscribe, and manually delete the mod files, then subscribe again, that should fix it
I don't know why that error is happening, it should be fixed by now. The new RimWorld update is going to release soon. Let me know if it still occurs in that version.