So I had some trouble getting my map to start in-game because the work I made on the map started pre-RoI and the 2.1.1 patch did make some changes that I did not notice until Korbah pointed them out for me (thanks Korbah!). I thought of sharing this so others who may have the same problem can know this, especially since nowhere else was this mentioned.
Specifically the changes 2.1.1 made are in the default.map file.
Normally when making a custom map you have to add a "sea_start = x" line near the top, where 'x' is the province number of the first sea province you have. Because of this, you had to order provinces in definitions.csv as land > sea.
PDS changed things because I believe it has to do with having groups of sea provinces that are separated (like the Indian Ocean separated from the Mediterranean).
Now you have to remove the "sea_start = x" line and instead use something like this in default.map:
Sea_zones are now organized as ranges. It's sort of like "sea_zones = { x y }" where x is the first sea province number and y is the last; this defines a single range. As you can see, you no longer have to have your provinces in definitions.csv organized as land > sea; you can have it land > sea > land > sea or whatever other combination you want, so long as the sea provinces are defined in sea_zone ranges in default.map.
Ocean_regions are groupings of sea_zone ranges organized for the AI to consider as a single group. So as an example, if the range sea_zones = { 51 100 } is x and the range sea_zones = { 101 150 } is y, then the first ocean_region can be organized as ocean_region = { x y } or ocean_region = { 1 2 } if those are the first 2 sea_zone ranges. I believe this is PDS's way of organizing the sea provinces of Europe as a separate super-group from the sea provinces of India so the AI doesn't get messed up like it did pre-2.1.1.
What I did for simplicity's sake, is organize only a single huge sea_zones range that encompasses all sea provinces with a single ocean_group defined. As an example, it looks something like this:
If you have 2 groups of sea provinces that are completely separated by land like the Indian Ocean and the Mediterranean in vanilla, then you'd probably have to have multiple ocean_groups defining those sea_zone ranges separately. If all your sea provinces are contiguous, then you can do what I did above and define only a single sea_zone range with a single ocean_group.
It's also worth mentioning how you no longer have to define portages, straits and major_rivers in adjacencies.csv.
Hope this helps!
Specifically the changes 2.1.1 made are in the default.map file.
Normally when making a custom map you have to add a "sea_start = x" line near the top, where 'x' is the province number of the first sea province you have. Because of this, you had to order provinces in definitions.csv as land > sea.
PDS changed things because I believe it has to do with having groups of sea provinces that are separated (like the Indian Ocean separated from the Mediterranean).
Now you have to remove the "sea_start = x" line and instead use something like this in default.map:
Code:
# European Seas
sea_zones = { 936 1012 }
sea_zones = { 1014 1111 }
sea_zones = { 1305 1305 }
# Indian Seas
sea_zones = { 1307 1317 }
sea_zones = { 1382 1407 }
sea_zones = { 1409 1412 }
sea_zones = { 1293 1293 }
ocean_region = { # European Ocean
sea_zones = { 1 2 3 }
}
ocean_region = { # Indian Ocean
sea_zones = { 4 5 6 7 }
}Sea_zones are now organized as ranges. It's sort of like "sea_zones = { x y }" where x is the first sea province number and y is the last; this defines a single range. As you can see, you no longer have to have your provinces in definitions.csv organized as land > sea; you can have it land > sea > land > sea or whatever other combination you want, so long as the sea provinces are defined in sea_zone ranges in default.map.
Ocean_regions are groupings of sea_zone ranges organized for the AI to consider as a single group. So as an example, if the range sea_zones = { 51 100 } is x and the range sea_zones = { 101 150 } is y, then the first ocean_region can be organized as ocean_region = { x y } or ocean_region = { 1 2 } if those are the first 2 sea_zone ranges. I believe this is PDS's way of organizing the sea provinces of Europe as a separate super-group from the sea provinces of India so the AI doesn't get messed up like it did pre-2.1.1.
What I did for simplicity's sake, is organize only a single huge sea_zones range that encompasses all sea provinces with a single ocean_group defined. As an example, it looks something like this:
Code:
#Example Seas
sea_zones = { 51 150}
#Example Ocean
ocean_group = { 1 }If you have 2 groups of sea provinces that are completely separated by land like the Indian Ocean and the Mediterranean in vanilla, then you'd probably have to have multiple ocean_groups defining those sea_zone ranges separately. If all your sea provinces are contiguous, then you can do what I did above and define only a single sea_zone range with a single ocean_group.
It's also worth mentioning how you no longer have to define portages, straits and major_rivers in adjacencies.csv.
Hope this helps!
Last edited:
