There are two files for dilemmas: “data_dilemmasRandom.json” and “data_dilemmasGatherings.json”.
Modding for both files is pretty much the same. The only thing you should keep in mind is that Dilemmas included in “data_dilemmasGatherings.json” will only be used when interacting with actors, directors and studios during Gatherings (aka. Events, Invitations, etc.). Whereas Dilemmas included in “data_dilemmasRandom.json” can be randomly triggered at the start of every turn.
You can experiment with Dilemmas, but there are 4 main “structures” we will be covering in this tutorial:
There are pre-design conditions and actions that can be used in Dilemmas. You can find the list of all conditions here and the list with all actions here.
CONDITIONS
Conditions are things that are checked about actors, directors, studios or the player in order for the Dilemma to be available. All selected options must be true in order for the Dilemma to be triggered.
ACTIONS
Actions are targeted at a specific actor, director, studio or the player and will modify their state in one way or another. You can execute the same action more than once if you like.
Dilemmas can have only 1 or 2 options. You can think of Dilemmas with 1 option simply as random events where you have no choice (simply a notification of an event).
Each option will trigger a set of Actions. You, as a Modder, will be able to determine what these Actions are.
If a Dilemma has 2 options, it can lead the player to 2 different results.
Targets are actors, directors, studios or the player itself. Each “Option” can have 1 Target only. Therefore, all Actions assigned to that Option will only affect one given Target.
DOUBLE TARGET
You will need to assign Target 1 to Option 1 and Target 2 to Option 2.
SINGLE TARGET
You will need to assign Target 1 to Option 1. Target 2 will simply be “same”.
NO OPTIONS
You will need to assign Target 1 to Option 1. Option 2 will be left blank.