DarkDominion Posted January 27, 2019 Share Posted January 27, 2019 This isn't the first time LOOT rules have been changed and now all of a sudden my load order isn't correct anymore ( which it was two days ago ).Something has changed inside the LOOT rules and now I get this : Error: yaml-cpp: error at line 238, column 7: bad conversion: set elements must be unique at c.handleResponse (D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1) at Socket.handleResponse (D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at Pipe.onread (net.js:594:20) With this "cyclic rules error" ( again worked perfectly two days ago ) SEE BELOW( and no , I can not changed my own rules , it wont let me ) Could you guys please make up your mind over at LOOT and decide on a rule set and stick with and and not change it every few weeks? It will save me a LOT of time SEE SECOND PICTURE : EDIT : now the cyclic rules seem to have disappeared ( I did nothing to make it so , just restarted Vortex ) and now I get this Link to comment Share on other sites More sharing options...
Zanderat Posted January 28, 2019 Share Posted January 28, 2019 I agree. Although I haven't had such issues, I would prefer that LOOT be kept separate from Vortex or at least not have enforced LOOT updates. Most of the complaints/issues here revolve around LOOT issues, not Vortex itself. Link to comment Share on other sites More sharing options...
DarkDominion Posted January 28, 2019 Author Share Posted January 28, 2019 Tannin42 ? anyone from staff? Link to comment Share on other sites More sharing options...
BigBizkit Posted January 29, 2019 Share Posted January 29, 2019 Hi, It appears that you have set some custom rules that are contradictory, which is causing the cyclic interaction. That explains the first message you are getting. The other message refers to a duplicate entry for elfxenhancer.esp. As the message explains, Vortex does not create entries like that. Could you tell me which version of Vortex you are on just to be sure? Link to comment Share on other sites More sharing options...
DarkDominion Posted January 31, 2019 Author Share Posted January 31, 2019 Hi, It appears that you have set some custom rules that are contradictory, which is causing the cyclic interaction. That explains the first message you are getting. The other message refers to a duplicate entry for elfxenhancer.esp. As the message explains, Vortex does not create entries like that. Could you tell me which version of Vortex you are on just to be sure?I set those rules and they were fine, I made a patch according to these rules and it was fine. Now LOOT has done a game changer rule again and all of a sudden it's NOT fine.All of a sudden I need to MANUALLY change the userlist.yaml to make things work again....I have set some rules that are contradictory ? How about you guys admit it was LOOT that effed up once again ? I'm running the latest version the experimental version...what 0.17 ? or something ? I'm just kind of fed up to have to MANUALLY rework my load order every time LOOT decides it should change something Hope you guys see my complaint for what it is... Link to comment Share on other sites More sharing options...
HadToRegister Posted January 31, 2019 Share Posted January 31, 2019 Hi, It appears that you have set some custom rules that are contradictory, which is causing the cyclic interaction. That explains the first message you are getting. The other message refers to a duplicate entry for elfxenhancer.esp. As the message explains, Vortex does not create entries like that. Could you tell me which version of Vortex you are on just to be sure?I set those rules and they were fine, I made a patch according to these rules and it was fine. Now LOOT has done a game changer rule again and all of a sudden it's NOT fine.All of a sudden I need to MANUALLY change the userlist.yaml to make things work again....I have set some rules that are contradictory ? How about you guys admit it was LOOT that effed up once again ? I'm running the latest version the experimental version...what 0.17 ? or something ? I'm just kind of fed up to have to MANUALLY rework my load order every time LOOT decides it should change something Hope you guys see my complaint for what it is... If you're getting that many Cyclic conflicts for your ESPs, then you're overdoing your load order rules, and you have far too many rules in your Plugins load order.You're working AGAINST Vortex. The important rules apply to MODs more than ESPs.Hopefully you're not following "load Order" guides from Reddit, or what-have-you, because those were written before Vortex and will result in Cyclic Rule problems. All you need to do is click on MANAGE RULES, and you can easily set which Mods load Before or After one another, but the easiest way is to put the mod into a group I had no end to cyclic rules when I first started using Vortex, because I kept insisting that Vortex sort the ESPs, MY way.Once I let Vortex do it, now I can focus on the Important sorting, the MODS. Link to comment Share on other sites More sharing options...
AugustaCalidia Posted January 31, 2019 Share Posted January 31, 2019 I set those rules and they were fine, I made a patch according to these rules and it was fine. Now LOOT has done a game changer rule again and all of a sudden it's NOT fine.All of a sudden I need to MANUALLY change the userlist.yaml to make things work again....I have set some rules that are contradictory ? How about you guys admit it was LOOT that effed up once again ? I'm running the latest version the experimental version...what 0.17 ? or something ? I'm just kind of fed up to have to MANUALLY rework my load order every time LOOT decides it should change something Hope you guys see my complaint for what it is... Do you run LOOT separately from Vortex? If you do, LOOT will usually override any load order changes you have made with Vortex. However, if you sort with Vortex, then Vortex will respect your rules. I've been using Vortex for almost a year now to manage a number of complex game setups. I sort my load order with Vortex exclusively, and I have never had the problems that you describe here. However, whether you use LOOT to sort or Vortex to sort, I suspect that your problems are not LOOT problems but those stated by BigBizkit. HadToRegister offers some good advice about load order. Most of the cyclic rules problems reported in this forum stem from people trying to micromanage their load orders. With Vortex that is unnecessary. Link to comment Share on other sites More sharing options...
DarkDominion Posted February 5, 2019 Author Share Posted February 5, 2019 both of you are jumping to conclusions, but thanks for trying Link to comment Share on other sites More sharing options...
FlameFury15 Posted February 6, 2019 Share Posted February 6, 2019 This isn't the first time LOOT rules have been changed and now all of a sudden my load order isn't correct anymore ( which it was two days ago ).Something has changed inside the LOOT rules and now I get this : Error: yaml-cpp: error at line 238, column 7: bad conversion: set elements must be unique at c.handleResponse (D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:167:1) at Socket.handleResponse (D:\Vortex\resources\app.asar.unpacked\bundledPlugins\gamebryo-plugin-management\webpack:\gamebryo-plugin-management\node_modules\loot\index.js:80:1) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) at Pipe.onread (net.js:594:20) With this "cyclic rules error" ( again worked perfectly two days ago ) SEE BELOW( and no , I can not changed my own rules , it wont let me ) Could you guys please make up your mind over at LOOT and decide on a rule set and stick with and and not change it every few weeks? It will save me a LOT of time SEE SECOND PICTURE : EDIT : now the cyclic rules seem to have disappeared ( I did nothing to make it so , just restarted Vortex ) and now I get this I would like to just point out in your first picture, the cyclic rule issue is VERY obvious if you actually cared to read it. Just look at the first mod shown in the error list and the last one.... it is being told to load after something whilst also being the first to load. you ahve a huge cycle set up there to do with the female eyebrows (I know women like to manually change their eyebrows often, but they usually know when to start and finsih them... usually) Link to comment Share on other sites More sharing options...
HadToRegister Posted February 6, 2019 Share Posted February 6, 2019 Your cyclic rule problem is being caused by the GROUPS you have the Plugins inThe groups are trying to force the load order to sort some mods AFTER other mods that they shouldn't Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.