Summary: With 1.5.0, there have been many people noticing a drop in the number of available quests over time. This is possibly cause by a variable not being saved properly when quiting the game. The value of the variable "_additionalFrequencyScore" is set to 0.2 when a new game is created in the OnNewGameCreated method of the IssuesCampaignBehavior class. This variable partly controls the number of total quests that spawn over time.
However, upon reloading a save, the variable reverts to 0, so in the CalculateIssueScoreInternal method you can see that the threshold for a new quest to be created changes, making it harder for new quests to be created when old ones expire or are completed.
How to Reproduce: Create a new game. Set a breakpoint in the CalculateIssueScoreInternal method to see what the value of the _additionalFrequencyScore variable is. It should be 0.2. Let the game run for awhile and use the in-game console command "campaign.print_issue_statistics" to see how the number of issues changes over time. Once it has stablized, save the game and reload the save. Check the value of _additionalFrequencyScore again, and it should now be 0. By letting the game run some more, you can use the console command to see the number of available issues fall over time.
Media:
The _additionalFrequencyScore variable is initialized in the OnNewGameCreated method of the IssuesCampaignBehavior class:
The CalculateIssueScoreInternal method is where the variable is used to control the number of quests that spawn over time, shown below:
Version: 1.5.0
However, upon reloading a save, the variable reverts to 0, so in the CalculateIssueScoreInternal method you can see that the threshold for a new quest to be created changes, making it harder for new quests to be created when old ones expire or are completed.
How to Reproduce: Create a new game. Set a breakpoint in the CalculateIssueScoreInternal method to see what the value of the _additionalFrequencyScore variable is. It should be 0.2. Let the game run for awhile and use the in-game console command "campaign.print_issue_statistics" to see how the number of issues changes over time. Once it has stablized, save the game and reload the save. Check the value of _additionalFrequencyScore again, and it should now be 0. By letting the game run some more, you can use the console command to see the number of available issues fall over time.
Media:
The _additionalFrequencyScore variable is initialized in the OnNewGameCreated method of the IssuesCampaignBehavior class:
The CalculateIssueScoreInternal method is where the variable is used to control the number of quests that spawn over time, shown below:
Version: 1.5.0