The fact a .pdb for the main executable was ever included in any release of the game was probably the mistake here, not the fact that it's gone now. Generally no game (or commercial software of any kind) ships with debugging files precisely because they don't want people to be able to debug their code - it makes it much easier to reverse engineer. For example, in my entire steam apps folder CK2 is the only game that has any .pdb files.
That said, since Paradox doesn't use any copy protection they might be a special case. It's worth asking, but I expect it won't happen.
This has a ring of truth to it to be honest, so I'm not holding my breath and understand why if it doesn't come back. If not I'll try and deal with it but to be honest find the CTD errors from modding, especially in the case where your mod changes every time you run, to be extremely difficult to figure out.
Has it been there this whole time? Seems like a pretty big thing to miss if people could potentially gain access to their code for 5 years...
I guess you already are running with the -debug -debugscripts flags in the shortcut to the .exe right? That's enables a crapload or error logging, which might or might not be useful in detecting crashes
..
This may indicate that CKII was never intended to ship with the CKII.pdb, which is disappointing when the development of this tool requires it.
Well no idea if its been there the whole time but for a considerable chunk of ck2generator's development. That said IMO I don't think it's quite as dramatic as implied, it perhaps would be if it was a competitive online multiplayer game as it may make it easier for users of disassemblers to make cheats, so maybe that's the reason (tho I imagine in this case it'd more likely help make an OOS simpulator ;D), but I wouldn't imagine it'd be practical to take the pdb and use it to get the code to make their own CK2 competitor or something. Either way though it may be enough to be the reason I dunno.