I’ve run into a problem involving wrye mash, and potentially the TR patcher. Whenever I attempt to use the wrye mash updater window, I get an error message reading:
Traceback (most recent call last):
File "masher.pyo", line 6280, in Execute
File "masher.pyo", line 616, in __init__
File "masher.pyo", line 6216, in getItemList
File "mosh.pyo", line 3202, in getObjectMaps
File "mosh.pyo", line 3213, in loadObjectMaps
EOFError
This whole issue started a little over a month ago when I attempted to install the most recent TR update. I honestly have no clue what the message implies, and research has yielded very little helpful information. However, today I ran into this post on the nexus. (Scroll down till you reach the long error message)
Apparently, the author had used the TR patcher and got loads of error messages shortly afterwards. Though his errors are a bit different from my own, I also ran into issues shortly after using the patcher. I’m not at all knowledgable on this sort of stuff, so I’d appreciate some help/insight.
2014-03-16 17:45
1 year 4 months ago
Odd that, I don’t know how the TR patcher functions but can’t imagine that it would affect wryeMash itself.
Only way would be that patched files could be sending it for a loop (literally, judging by the length of that poster’s error message) due to edits to .esps it can’t parse? If so, the errors would disappear if you replace the patched files with non-patched versions (patcher creates them as .bak files, right?). Is that the case?
2015-12-29 23:49
11 months 2 days ago
Agreed that the file patcher would probably not affect wrye mash directly.
As for the reported errors on the nexus, your hypothesis makes sense to me. When it comes to my own situation, the updater window won’t work for any file, even the ones that have never been patched, unless I replace the entire Data Files folder with an older one. I’ve reinstalled wrye mash to no avail. So far, the best translating I can do with the error message is conclude that EOF stands for ‘end of file’. I’ll keep on experimenting and see what happens.
2015-12-29 23:49
11 months 2 days ago
Luckily, I’ve found the solution to my own problem – an unnoticed mash file somehow prevented a script from running. I’ve removed it from the data files and the updater window works again. At this point, I don’t think the problem was directly related to the patcher, but instead the mash file was likely placed there at roughly the same time and so I got things mixed up.
Other than that, I suppose we should keep our eyes open on the nexus report and see what happens there. At this point I suppose those errors were likely caused from a personal wrongdoing rather than a flaw from our patcher.
2014-03-16 17:45
1 year 4 months ago
Makes sense (if the nexus one gets cleared up maybe change the topic title here? so as not to confuse people :p )
2015-12-29 23:49
11 months 2 days ago
Yeah, I’ll do that.