I have 0 idea if this is even doable, but, certain things in CK2 should match certain things in CK3
For example. Province 69 in CK2 might be province 420 in CK3. You guys (paradox) would know this, and so, could build a converter that converts all mentions of Province 69 in a CK2 mod, to Province 420 in a CK3 mod.
The same is true for various character IDs. Beyond that, many of the various triggers and scopes and general 'things' a mod may wish to reference, are also likely to have a name in CK3 if they had a name in CK2. Maybe some of them are the same; if so, great! Maybe they are different, if so, you can easily automate a converter to fix it.
The objective of this converter would not be to render flawless working CK3 mods when you plug a CK2 mod in.
It would be to produce a CK3 mod file, that still requires work, but, has all the boring annoying repetitive busy work done for you.
Not sure exactly how you'd pull it off, but the general idea of building an automated thingy to convert CK2 programming mod syntax into CK3 programming mod syntax, I think, has merit, and is doable.
To be super duper clear: you would not be able to take a CK2 mod, put it in one end of the converter, and have a CK3 mod pop out. You'd put a CK2 mod in one end, and have a "work in progress CK3 mod you need to finish" pop out.
For example. Province 69 in CK2 might be province 420 in CK3. You guys (paradox) would know this, and so, could build a converter that converts all mentions of Province 69 in a CK2 mod, to Province 420 in a CK3 mod.
The same is true for various character IDs. Beyond that, many of the various triggers and scopes and general 'things' a mod may wish to reference, are also likely to have a name in CK3 if they had a name in CK2. Maybe some of them are the same; if so, great! Maybe they are different, if so, you can easily automate a converter to fix it.
The objective of this converter would not be to render flawless working CK3 mods when you plug a CK2 mod in.
It would be to produce a CK3 mod file, that still requires work, but, has all the boring annoying repetitive busy work done for you.
Not sure exactly how you'd pull it off, but the general idea of building an automated thingy to convert CK2 programming mod syntax into CK3 programming mod syntax, I think, has merit, and is doable.
To be super duper clear: you would not be able to take a CK2 mod, put it in one end of the converter, and have a CK3 mod pop out. You'd put a CK2 mod in one end, and have a "work in progress CK3 mod you need to finish" pop out.
- 6
- 1