RimWorld

RimWorld

245 betyg
Log After Def Error (Continued)
2
2
   
Utmärkelse
Favorit
Favoritmarkerad
Avfavoritmarkerad
Mod, 1.5, 1.6
Filstorlek
Lades upp
302.466 KB
17 aug @ 11:27
1 ändringsnotis ( visa )

Abonnera för att ladda ner
Log After Def Error (Continued)

I 2 samlingar av Mlie
Mlie's resurrected mods
969 artiklar
My Collection
10 artiklar
Beskrivning

Update of ordpuss mod https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3291238448



[discord.gg]
[github.com]


Haha, look familiar? Parsed xxx as int are happening all over the rimworld, right now!
Unless you make the most import decision in your life.🫰
Prove to yourself that you have the strength of courage to be bugfree. ⛑️
Join... the LADE👍

Print the details of the def if there is error logged during parsing xml into c# objects, extremely helpful to locate xml errors as it only gives very specific parsing exception in vanilla.

The Info structure is [Def Error] defName:modName/pathToXml/xmlFile.xml

log file "Player.log" should be at parent folder of your save folder. Follow https://rimworldwiki.com/wiki/Save_file to find it.

Or you can just post Hugslib log, instruction is here https://gtm.steamproxy.vip/workshop/filedetails/?id=818773962


  • See if the error persists if you just have this mod and its requirements active.
  • If not, try adding your other mods until it happens again.
  • Always post your log using the Log Uploader
  • For best support, please use the Discord-channel for error-reporting.
  • Do not report errors by making a discussion-thread, I get no notification of that.
  • If you have the solution for a problem, please post it to the GitHub repository.
  • Use RimSort[github.com] to sort your mods
22 kommentarer
Iopy 17 timmar sedan 
Hey Mlie, I have a bunch of the parsed (number) as int errors. And thanks to this mod I can see what they're pointing at. But most of them are pointing at the Storytellers, base game and modded ones. I cant work out what is causing them to throw these error. I dont have much experience with understanding these errors, I was wondering whether you or someone here in the comments could help me understand what is causing this? Error log below.

https://gist.github.com/HugsLibRecordKeeper/37a19772fded2ed0228a758746280ef7

If there is a better place to seek assistance, please let me know. Thank you!
Ryuuoo_ 23 aug @ 16:40 
Found the mod it was NOD armor mod, that was using wrong stat terms.
Changed them by myself and error did go away.
Learned new way to find errors, open mod folder and check through the text files.
If you know what are you looking for.
Mlie  [skapare] 23 aug @ 14:41 
@Ryuuoo_ It is an unupdated mod, so you will have to find that one and replace it
Aleksey 23 aug @ 7:32 
Yeah, that seems about right.
Mlie  [skapare] 22 aug @ 22:37 
@Aleksey So sort of a combination of this mod and the Mod Error Checker mod
Aleksey 22 aug @ 17:11 
Better Stacktraces (mod developer here) does catch XML errors, but it also gives a better stacktrace with assembly and mod names to help you identify errors. I'd like for it to catch more code-related errors, but it's been quite the challenge.
Mlie  [skapare] 22 aug @ 14:17 
@тетеря, блин Possibly, they do not show their source so cannot say
Mlie  [skapare] 22 aug @ 10:29 
@Dümbük Enişte If the mod tells users what mod has an error in their xml, I dont really see how that would be an unrelated error?
Dümbük Enişte 22 aug @ 10:25 
I love this one but unfortunately, it will probably make more people pestering mod authors for unrelated errors.