Ginlea64 Posted December 7, 2021 Share Posted December 7, 2021 I went to load up my game this morning and get hit with this message. "Error:yaml-cpp:error at line 1, column 3: unknown escape character." I have no idea how this happened as it was working yesterday. Also, uninstall and reinstall did not work. Link to comment Share on other sites More sharing options...
Tannin42 Posted December 7, 2021 Share Posted December 7, 2021 You are providing way too little information, neither did you give use the entire error message nor did you even tell us which game you're talking about.So I have to guess: You're modding a bethesda game and this error message is generated by loot as it's trying to parse the masterlist or - more likely - the userlist.The reason this would happen is because either you manually messed around with these files, because you had a severe hardware outage that caused the files to get corrupted or there was a network error when vortex tried to fetch the loot masterlist. More generally: yaml is a file format that some tools, not Vortex itself though, use to store data or configuration settings. The error message says that such a yaml file is corrupted. Why, how and when the file got corrupted no one other than yourself has any chance of knowing. Link to comment Share on other sites More sharing options...
Ginlea64 Posted December 7, 2021 Author Share Posted December 7, 2021 This looks to be about right, so how do I find the corrupted file and fix it? Also, I actually don't like to go messing around in those files because I know that I very well could jack things up. So that is something I try to avoid unless I have really good instructions, which I don't , so, I don't mess with that stuff cuz I am not well versed in code. I wanted to copy the script message but it refused, and pen and paper are currently somewhere not here. Link to comment Share on other sites More sharing options...
Ginlea64 Posted December 7, 2021 Author Share Posted December 7, 2021 Found writing things.. Error: yaml-cpp: error at line 1, column 3: unknown escape character:at l.handleResponse (C:ProgramFiles\BlackTreeGamingLtd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:31:34813)at C:ProgramFiles\BlackTreeGamingLtd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:31:33289)at Array.forEach(<anonymous>)at Socket.<anonymous>(C:ProgramFiles\BlackTreeGamingLtd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:31:33273)at Socket.emit(events.js:315:20)at addChunk(_steam_readable.js:295:12)at readableAddChunk(_steam_readable.js:271:9)at Socket.Readable.push(_steam_readable.js:212:10)at Pipe.onStreamRead(internal/steam_base_commons.js:186:23) Link to comment Share on other sites More sharing options...
Ginlea64 Posted December 7, 2021 Author Share Posted December 7, 2021 I went to load up my game this morning and get hit with this message. "Error:yaml-cpp:error at line 1, column 3: unknown escape character." I have no idea how this happened as it was working yesterday. Also, uninstall and reinstall did not work. Found writing things.. Error: yaml-cpp: error at line 1, column 3: unknown escape character:at l.handleResponse (C:ProgramFiles\BlackTreeGamingLtd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:31:34813)at C:ProgramFiles\BlackTreeGamingLtd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:31:33289)at Array.forEach(<anonymous>)at Socket.<anonymous>(C:ProgramFiles\BlackTreeGamingLtd\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\index.js:31:33273)at Socket.emit(events.js:315:20)at addChunk(_steam_readable.js:295:12)at readableAddChunk(_steam_readable.js:271:9)at Socket.Readable.push(_steam_readable.js:212:10)at Pipe.onStreamRead(internal/steam_base_commons.js:186:23) Link to comment Share on other sites More sharing options...
showler Posted December 7, 2021 Share Posted December 7, 2021 He didn't "quit responding". He's in Germany and it's around 3am there right now. Link to comment Share on other sites More sharing options...
Ginlea64 Posted December 8, 2021 Author Share Posted December 8, 2021 ok then. that would have been nice to know, and now I sound like an ass.. Link to comment Share on other sites More sharing options...
Tannin42 Posted December 8, 2021 Share Posted December 8, 2021 Inside Vortex->Plugins there is an option to "Reset Masterlist", that would remove and re-fetch the masterlist.If that doesn't fix it, it's probably the userlist. That you can find at C:\Users\<userid>\AppData\Roaming\Vortex\<gameid>\userlist.yamluserid is your windows account name, gameid is something like skyrimse or fallout4, whatever the game you're playing is. Link to comment Share on other sites More sharing options...
Ginlea64 Posted December 8, 2021 Author Share Posted December 8, 2021 Now there is a new error message... LOOT userlist :C:users\ginle\AppData\Roaming\Vortex\fallout4\userlist.yaml can't be read. you should quit vortex now and repair the file. if (and only if!) you're certain you didn't modify the file yourself. please send in a bug report with file attached. Tries looking for the Vortex->Plugins on my rig to Reset Masterlist, and it refused to be found, and I have no idea where this file is that I am to attach to this bug report. Also, apologies for my ignorant asshattedness. One more thing. This is only coming up with Fallout 4 and not for New Vegas. Link to comment Share on other sites More sharing options...
Pickysaurus Posted December 9, 2021 Share Posted December 9, 2021 So the error seems pretty clear to me. The file at C:users\ginle\AppData\Roaming\Vortex\fallout4\userlist.yaml is corrupted in some way. You can either try and repair it or delete it. If you want you can copy the contents of that file into a reply and we'll see if we can see what is wrong with it. Deleting that file will reset all your custom plugin rules and groups for Fallout 4. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.