Some helpful tips for anyone having issues with quests and assaults. These worked for me.
1. Load conqueror as close to the bottom of your load order as possible. Conqueror's quests cover a lot of areas, and in doing so, will conflict with other mods. Example being the excavator power armor mod. If it's loaded after conqueror, a certain bounty quest won't properly fire at the quarry. The quad barrel shotgun is another mod that has a direct worldspace conflict with conqueror. There are plenty more. No biggy, just something to keep in mind.
2. Save before every single conqueror mission. Save after every single quest stage. Try reloading to one of those points if something goes weird with the quest. And chances are something is going to go wrong on at least one of the quests. Waiting and fast travel back and forth to quest points have never worked for me, only reloads have. This is especially true if you use mods that spawn more enemies or patrols in the game. Conqueror does not handle extra enemies during those prolonged point to point conversation missions very well at all. If the quest NPCs go off track it's time to reload because there is no fixing them. Especially the one around Diamond City and the Maul quest chain. The console command kah is very handy in these situations. Kill everything before it bugs out the quest. Otherwise the quest npcs are just going to wander off into oblivion.
3. I'm sure the ss team spent a lot of time bug testing, but it's impossible to test against every possible mod list. So know your quest console codes. After a quest is dropped into your pipboy, use sqt in your console, locate the conqueror quest (they are pretty obviously named), and make note of it. You may need to make use of quest console codes to set specific stage numbers. A google search will send you to what you need. sqt, getstage, setstage, sqs, sqo, and movetoqt being the most useful. Use these if the quest just isn't working for you or causing ctds as certain quest stages. Or if the quest npc wandered off or never showed up. Patience is not a virtue here, you're just wasting your time. Either reload to a previous save point and try again, or use the console codes to move the quest forward.
4. If conqueror scripts seem like they are taking a long time to fire (assaults are not working or assignments are taking forever, slow UI, etc), something is hogging your resources. Either you have a heavily scripted game, and you're going to have trouble no matter what (reduce the amount of script heavy mods you use), or you have soldiermanager script spam. The SS team says waiting indoors for a long time will help resolve this, but it never worked for me. Check your save in fallrim/resaver. If you see a ton of soldiermanager 5 frame zero instance scripts, terminate all or as many of them as you can that don't cause a ctd or infinite loading screen upon save load. Make backup saves, save often, etc. Chances are your game is going to start responding again. Report the soldiermanager script spam in the sim settlements forum.
These methods have helped me enjoy the conqueror mechanics for quite a while now. Some of the quests can be a headache to get through, but they are awesome when they function correctly. Especially the dialog stage points. Those are really cool when they work. And the entire raider system is the only reason why I still play this game after so many hours. Hope these tips help others.
So are you guys ever going to finish the Conqueror storyline? I'm kinda disappointed that it just abruptly ended and you moved on to the goody twoshoes story
what is the load order? i've installed it and simsettlements, simsettlements work I guess? (got no quests so who knows) No settlement I have visited has been built up in 13+hours on the save
Yes. 4.17/4.17a (SS 3 in 1 and Conqueror) definitely work, I'm not sure that any versions after that do though, as pancake game got updated and VR game did not.
No, only if you want to do the pre-built settlements mechanic, you can start this with a current game. While the pre-built settlements are great, I prefer starting with a blank canvas and building them myself, you can build them after you conquer vassal settlements too if you turn it in the options.
Do you think it's worthwhile in its abandoned state? I'm contemplating a raider playthrough and trying to decide if it's worth leaving Horizon to play Conqueror.
I recommend against using any mod of this scale that has been abandoned. Might be full of bugs that people dont even know about, and you'll have no support for them
Chapter 3 of Sim Settlements 2 will be bringing back a lot of the Conqueror mechanics with updates and improvements - so to directly answer the question, not currently, but it will.
As for whether Conqueror worth playing in its current state, I would say absolutely, if you really want the experience of playing as a raider right out of the vault. The team invested a lot of time and effort into making it as stable as they could, the game loop is a lot of fun, and the story as it exists is well written. It's unfortunate that their main writer was pulled away from the project due to real life events, but given that development on Conqueror and on Sim Settlements 2 was going on concurrently, it makes sense that they shifted their focus when that happened. If you do encounter any bugs, check out the Sim Settlements forums - the community there is full of skilled and knowledgeable people who can help with figuring out mod conflicts, identifying known issues, and offering workarounds.
SS2 has a same NPC with Conq, Aiden, Aiden is ConQ 's Jammer 's old friend and enemy.... in SS2 Aiden is stil the same character with CONq , but jammer did not appear in SS2......
4345 comments
-kinggath
Triangle Of Death
1. Load conqueror as close to the bottom of your load order as possible. Conqueror's quests cover a lot of areas, and in doing so, will conflict with other mods. Example being the excavator power armor mod. If it's loaded after conqueror, a certain bounty quest won't properly fire at the quarry. The quad barrel shotgun is another mod that has a direct worldspace conflict with conqueror. There are plenty more. No biggy, just something to keep in mind.
2. Save before every single conqueror mission. Save after every single quest stage. Try reloading to one of those points if something goes weird with the quest. And chances are something is going to go wrong on at least one of the quests. Waiting and fast travel back and forth to quest points have never worked for me, only reloads have. This is especially true if you use mods that spawn more enemies or patrols in the game. Conqueror does not handle extra enemies during those prolonged point to point conversation missions very well at all. If the quest NPCs go off track it's time to reload because there is no fixing them. Especially the one around Diamond City and the Maul quest chain. The console command kah is very handy in these situations. Kill everything before it bugs out the quest. Otherwise the quest npcs are just going to wander off into oblivion.
3. I'm sure the ss team spent a lot of time bug testing, but it's impossible to test against every possible mod list. So know your quest console codes. After a quest is dropped into your pipboy, use sqt in your console, locate the conqueror quest (they are pretty obviously named), and make note of it. You may need to make use of quest console codes to set specific stage numbers. A google search will send you to what you need. sqt, getstage, setstage, sqs, sqo, and movetoqt being the most useful. Use these if the quest just isn't working for you or causing ctds as certain quest stages. Or if the quest npc wandered off or never showed up. Patience is not a virtue here, you're just wasting your time. Either reload to a previous save point and try again, or use the console codes to move the quest forward.
4. If conqueror scripts seem like they are taking a long time to fire (assaults are not working or assignments are taking forever, slow UI, etc), something is hogging your resources. Either you have a heavily scripted game, and you're going to have trouble no matter what (reduce the amount of script heavy mods you use), or you have soldiermanager script spam. The SS team says waiting indoors for a long time will help resolve this, but it never worked for me. Check your save in fallrim/resaver. If you see a ton of soldiermanager 5 frame zero instance scripts, terminate all or as many of them as you can that don't cause a ctd or infinite loading screen upon save load. Make backup saves, save often, etc. Chances are your game is going to start responding again. Report the soldiermanager script spam in the sim settlements forum.
These methods have helped me enjoy the conqueror mechanics for quite a while now. Some of the quests can be a headache to get through, but they are awesome when they function correctly. Especially the dialog stage points. Those are really cool when they work. And the entire raider system is the only reason why I still play this game after so many hours. Hope these tips help others.
As for whether Conqueror worth playing in its current state, I would say absolutely, if you really want the experience of playing as a raider right out of the vault. The team invested a lot of time and effort into making it as stable as they could, the game loop is a lot of fun, and the story as it exists is well written. It's unfortunate that their main writer was pulled away from the project due to real life events, but given that development on Conqueror and on Sim Settlements 2 was going on concurrently, it makes sense that they shifted their focus when that happened. If you do encounter any bugs, check out the Sim Settlements forums - the community there is full of skilled and knowledgeable people who can help with figuring out mod conflicts, identifying known issues, and offering workarounds.