CK2ToEU4, 1.0Capet

We've been holding on for 1.30 release, so the list of updates grew quite large. Here are the most important ones:

Conversion Features and Fixes

Sunset can now be toggled as an option during conversion.
Sunset has been reworked from ground up. High Americans have an already reformed religion, will be able to build ships, and will most certainly be able to spawn institutions. Expect them to be quite a challenge, unless Incas and Mayans die in mutual clashes, seeing how they are historical rivals (and they have no one else to rival anyway).

You can now provide a targeted list of empires to be shattered in shatter_empires.txt and enable it in the converter options. This is highly advised in case your CK2 game ended in a bunch of megablobs.

Instead of tying dynasty names for countries to religion, we've remapped it to use cultures instead, with a handful of exceptions. In case of a Christian Turkish Capet ruler of Persia (actual example from saves), expect to see "Capet" nation, with probably a few "Capet Arabia" or "Capet Egypt" countries as PUs.
When several countries shared the same name (d_bohemia separate from k_bohemia), we now generate new names to differentiate them - Greater Bohemia, Lesser Bohemia, etc. Up to 5 variations for the same name are supported.

Cultures have been painstakingly checked and tweaked. Specifically German and Italian culture are better differentiated outside their home regions. Rome will remain Umbrian.
Turkish and other asian cultures have received tweaks and differentiation.
Roman culture will now correctly break apart across the continent (and outside of Europe).
Tartars, Jews, Africans, cultures all across the board have been polished.
Wrongly mapped ex-burman cultures have been correctly moved into tibetan group.

All religions have reformed and unreformed variants.
Unreformed pagans can reform by taking a decision once they control all 5 Holy Sites, even in EU4 timeline.
Tengri from far east (outside CK2 scope) will unreform, regardless of the state of Tengri in CK2 scope.
The bug with countries and rulers defaulting to their historical dynasty religion has been corrected.
Buddhism (Theravada) has been split into Theravada and Vajrayana along geopolitical lines.

Instead of choosing electors at random, converter will now attempt to assign electorate seats to CK2 electors, if at all possible.
Bug where free cities could become electors has been fixed.

A large amount of effort has been invested so that countries, according to their laws, rulers, geographical position, culture, religion and features, would start with an appropriate starting government reform. However, these reforms do not include the new ones introduced with 1.30 patch.

Converter now offers an option to retain EU4 vanilla development, which is quite necessary for very early conversions where entire world will otherwise be a swamp.
Development has been eased from 12 to 10 buildings per dev point. Baronies themselves are still worth 0.3 dev each.

We missed a few of the provinces introduced post Holy Fury and have now mapped all CK2 3.3 and EU4 1.30 provinces.

We now distribute dead cores of primary cultural nations, unless those exist as extant countries. For example, if Scandinavia eats France, you can expect to see French cores in french provinces, so the country may be released during EU4 timeframe.

Converter will no longer purge those Siberian tribes with more than 5 provinces as they are no longer insignificant.
Saharan passes are now sterilized to separate african primitives from predatory countries of northern africa. This gives them time to develop and prevents immediate blobbing into subsaharan africa.
Passes will not be cleared if a nation already holds both ends of a pass.

The old Frontend program has been replaced with a brand new one, called Fronter, which does everything the old one did as well as display conversion progress. Yay, a technological leap! Backwards! From C# to C++!

Aside for these, many minor under-the-hood fixes and patches were implemented, as always.

The windows_development_build supersedes this release and is built whenever a feature is added, dynamically. You can get it here.