The missions.ini has a lot of lines that each define the pods on that mission schedule and where they spawn. Here's an example for how such a mission schedule looks like:

+MissionSchedules=(ScheduleID="Guerilla_D1_Standard_3", MinRequiredAlertLevel=1, MaxRequiredAlertLevel=1, MinRequiredForceLevel=18, MaxRequiredForcelevel=99, IdealXComSpawnDistance=32, MinXComSpawnDistance=28, EncounterZonePatrolDepth=4.0, PrePlacedEncounters[0]=(EncounterID="OPNx2_Standard_2", EncounterZoneOffsetAlongLOP=7.0), PrePlacedEncounters[1]=(EncounterID="LIST_BOSSx2_Standard_2", EncounterZoneOffsetAlongLOP=-7.0, EncounterZoneWidth=6.0), PrePlacedEncounters[2]=(EncounterID="DKVx1_Chryssalid", EncounterZoneOffsetAlongLOP=-11.0, EncounterZoneWidth=10.0, EncounterZoneDepthOverride=36.0, EncounterZoneOffsetFromLOP=0.0, IncludeTacticalTag="DarkEvent_InfiltratorChryssalid"), PrePlacedEncounters[3]=(EncounterID="DKVx2_FacelessAndCivilians", EncounterZoneOffsetAlongLOP=5.0, IncludeTacticalTag="DarkEvent_Infiltrator"), )


Each of these mission schedules lists the PrePlacedEncounters. These are the pods. Or, like in the example, there can be placeholders for Dark Event pods. Mission schedules for terror missions also have the civvies in there. To modify pod count, you'd have to delete one of the PrePlacedEncounters, then make sure that their numbering is still correct.

To be perfectly honest, this is a huge chore to do and you can easily mess up and create non-functional mission schedules here. Those would lead to a crash. There are already a lot of mission schedules in vanilla and ABA straight up quadruples them. You'd literally be looking at spending a couple of hours for a few days on editing these lines.

I don't suggest messing with these, so proceed at your own risk.

Originally posted by DerBK:

The missions.ini has a lot of lines that each define the pods on that mission schedule and where they spawn. Here's an example for how such a mission schedule looks like:

+MissionSchedules=(ScheduleID="Guerilla_D1_Standard_3", MinRequiredAlertLevel=1, MaxRequiredAlertLevel=1, MinRequiredForceLevel=18, MaxRequiredForcelevel=99, IdealXComSpawnDistance=32, MinXComSpawnDistance=28, EncounterZonePatrolDepth=4.0, PrePlacedEncounters[0]=(EncounterID="OPNx2_Standard_2", EncounterZoneOffsetAlongLOP=7.0), PrePlacedEncounters[1]=(EncounterID="LIST_BOSSx2_Standard_2", EncounterZoneOffsetAlongLOP=-7.0, EncounterZoneWidth=6.0), PrePlacedEncounters[2]=(EncounterID="DKVx1_Chryssalid", EncounterZoneOffsetAlongLOP=-11.0, EncounterZoneWidth=10.0, EncounterZoneDepthOverride=36.0, EncounterZoneOffsetFromLOP=0.0, IncludeTacticalTag="DarkEvent_InfiltratorChryssalid"), PrePlacedEncounters[3]=(EncounterID="DKVx2_FacelessAndCivilians", EncounterZoneOffsetAlongLOP=5.0, IncludeTacticalTag="DarkEvent_Infiltrator"), )


Each of these mission schedules lists the PrePlacedEncounters. These are the pods. Or, like in the example, there can be placeholders for Dark Event pods. Mission schedules for terror missions also have the civvies in there. To modify pod count, you'd have to delete one of the PrePlacedEncounters, then make sure that their numbering is still correct.

To be perfectly honest, this is a huge chore to do and you can easily mess up and create non-functional mission schedules here. Those would lead to a crash. There are already a lot of mission schedules in vanilla and ABA straight up quadruples them. You'd literally be looking at spending a couple of hours for a few days on editing these lines.

I don't suggest messing with these, so proceed at your own risk.

I see, that's quite a lot of risk. I think I'll do my own INI edits to the experience rate to fix this problem. Thanks for the quick reply!