Queries on CB modding - Unknown errors and dependencies

[Colossal_Elk]

Recently, I've been working on porting over various CBs, clearing out vanilla-specific religion, culture and title references. Unfortunately, I've run into a problem that causes random but fairly reliable CTDs, and I cannot figure out a way to correct the issue. There's two closely-related reasons for this. The first reason is that I cannot find any references to these errors anywhere. The second is that I do not know what files the 00_cb_types file is connected to, which files it depends on, and which files are dependent on it.

Here's a sample of the error logs, originally posted in the Quick Questions thread:

[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT
[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT
[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT
[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT
[effectimplementation.cpp:18321]: Assert failed for 'break_alliance': false && "Characters not allied in CBreakAllianceEffect"
[event.cpp:526]: Previous assert occured in Event 'ZE.8013'.
[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT
[effectimplementation.cpp:18321]: Assert failed for 'break_alliance': false && "Characters not allied in CBreakAllianceEffect"
[event.cpp:526]: Previous assert occured in Event 'ZE.8013'.
[effectimplementation.cpp:18321]: Assert failed for 'break_alliance': false && "Characters not allied in CBreakAllianceEffect"
[event.cpp:526]: Previous assert occured in Event 'ZE.8013'.
[effectimplementation.cpp:18321]: Assert failed for 'break_alliance': false && "Characters not allied in CBreakAllianceEffect"
[event.cpp:526]: Previous assert occured in Event 'ZE.8013'.
[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT
[messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT

The first of these messages, [messagehandler.cpp:423]: Failed to find message type: ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT, is the one that I'm really having the problems with. I've narrowed the problem down as being connected to the 00_cb_types file--deleting this file stops the error message from appearing in the error logs, and also prevents the game from crashing. With the file, the game will rarely last more than 100 years or so.

In order to correct this problem, I think there's two things I need to know:

1. What, specifically, does the error message in question refer to? Has anyone seen this before, and if so, what did you do to fix it?

2. What files in vanilla are 00_cb_types connected to?


My thanks to anyone who could help me correct this problem or provide me with some information so that I can correct it.

 

[Rylock]

Did you change the 00_cb_types file at all?

We can hardly assist you without knowing what you did. If I had to guess, I'd say you probably removed a cb which is supposed to be there.

 

[Colossal_Elk]

Did you change the 00_cb_types file at all?

We can hardly assist you without knowing what you did. If I had to guess, I'd say you probably removed a cb which is supposed to be there.

I did, yes. Should I post part or the entirety of the 00_cb_types file?

To your second point, that's why I wanted to know what the vanilla dependencies are. That way I don't merely know what not to do, I know why not to do it.

 

[Rylock]

ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT is one of the on_action types for the diplo actions -- so if there's a conflict with the cb_types file, then it's probably the game code looking for a standard cb that it expects to find in that file but currently doesn't. There's no direct correlation that I'm aware of, however.

The way to find the exact cause would be to make one change at a time to the vanilla cb_types file until you narrow down which one of your changes is causing the issue. Obviously it's something you did, and since you already narrowed it down to the file responsible it's easy enough to continue.

 

[Colossal_Elk]

ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT is one of the on_action types for the diplo actions -- so if there's a conflict with the cb_types file, then it's probably the game code looking for a standard cb that it expects to find in that file but currently doesn't. There's no direct correlation that I'm aware of, however.

The way to find the exact cause would be to make one change at a time to the vanilla cb_types file until you narrow down which one of your changes is causing the issue. Obviously it's something you did, and since you already narrowed it down to the file responsible it's easy enough to continue.

For what it's worth, plugging the vanilla 00_cb_types file in will also cause the error message to show up, and can cause crashes. I'm not sure if the crashes are because of the vanilla-specific (religion, culture, title) entries, but taking them out of the file doesn't seem to help me much.

That's why I'm not sure if it's actually the file itself or one of the files that 00_cb_types is connected to. Deleting it and thus removing CBs removes the issue, but using the vanilla file or attempting to clean up the CB file itself doesn't appear to do much to prevent the crashes.

 

[Rylock]

For what it's worth, plugging the vanilla 00_cb_types file in will also cause the error message to show up, and can cause crashes. I'm not sure if the crashes are because of the vanilla-specific (religion, culture, title) entries, but taking them out of the file doesn't seem to help me much.

That's why I'm not sure if it's actually the file itself or one of the files that 00_cb_types is connected to. Deleting it and thus removing CBs removes the issue, but using the vanilla file or attempting to clean up the CB file itself doesn't appear to do much to prevent the crashes.

I'm not sure I understand. If you delete your cb_types file, it should be using the vanilla file. Or are you modding the vanilla files directly?

If so, don't do that.

I would suggest starting by using the Validator, as it sounds like you haven't actually narrowed down what the cause of the issue is. Personally, I've been modding CK2 for quite some time, and I've never seen an error involving ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT -- especially considering it's not actually called anywhere in the files, it's something that's invoked via the defines.lua file. So whatever your issue is, it very likely goes a lot deeper than you think, and the ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT issue is only an indirect symptom.

 

[Colossal_Elk]

I'm not sure I understand. If you delete your cb_types file, it should be using the vanilla file. Or are you modding the vanilla files directly?

If so, don't do that.

I would suggest starting by using the Validator, as it sounds like you haven't actually narrowed down what the cause of the issue is. Personally, I've been modding CK2 for quite some time, and I've never seen an error involving ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT -- especially considering it's not actually called anywhere in the files, it's something that's invoked via the defines.lua file. So whatever your issue is, it very likely goes a lot deeper than you think, and the ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT issue is only an indirect symptom.

I have the .mod file set to replace_path for the CBs folder, and the file I'm using is 00_cb_types within the mod folders, as opposed to changing anything in vanilla directly (I know better than to do that. ). It's when I have no CBs whatsoever that the game runs fine.

I get the error messages and a CTD whether I'm using the vanilla version of the CBs file or I'm using our mod's version of it.

 

[Rylock]

I get the error messages and a CTD whether I'm using the vanilla version of the CBs file or I'm using our mod's version of it.

Then, like I said, your issue isn't the cb_types file, is it?

Start with the Validator. Track down your problem. I know you were probably hoping that your ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT log event would be some kind of smoking gun, but it's really not.

 

[Colossal_Elk]

Then, like I said, your issue isn't the cb_types file, is it?

Start with the Validator. Track down your problem. I know you were probably hoping that your ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT log event would be some kind of smoking gun, but it's really not.

That's why I'm trying to figure out what the dependencies are. I understand that the CB file is connected to other things but what those other things are, I do not know.

In the Validator, the only error messages I can find (other than localization keys, but localization doesn't use a replace_path so I don't know why that would be a problem) are all messages that appear when I validate the vanilla 00_cb_types file as well.

 

[Rylock]

That's why I'm trying to figure out what the dependencies are. I understand that the CB file is connected to other things but what those other things are, I do not know.

I don't know what you imagine a "dependency" is, but there are none that I know of.

In the Validator, the only error messages I can find (other than localization keys, but localization doesn't use a replace_path so I don't know why that would be a problem) are all messages that appear when I validate the vanilla 00_cb_types file as well.

Then you only have one alternative. Take things out of your mod, one small section at a time. After each removal, fire up the mod and check the log. The moment the warning disappears, you know your issue is in the part you just removed (and I would also check if the replace_path is your issue -- meaning take out the replace_path for the cb_types folder, putting in a blank file with the vanilla file if you truly have to, and see if that changes anything).

That kind of methodical approach will track down your bug, guaranteed. Failing that, you are SOL.

 

[Colossal_Elk]

I don't know what you imagine a "dependency" is, but there are none that I know of.



Then you only have one alternative. Take things out of your mod, one small section at a time. After each removal, fire up the mod and check the log. The moment the warning disappears, you know your issue is in the part you just removed (and I would also check if the replace_path is your issue -- meaning take out the replace_path for the cb_types folder, putting in a blank file with the vanilla file if you truly have to, and see if that changes anything).

That kind of methodical approach will track down your bug, guaranteed. Failing that, you are SOL.

I refer to the files that depend on 00_cb_types in some way, or that 00_cb_types depends on. Any sorts of file that the CB file is directly connected to, one way or the other. Since not having a CB file means no crash, then it'd almost certainly have to be something connected to the CB file if it isn't the CB file itself, wouldn't it?

 

[Divine]

Do you get anything in your exception log on your crashes? What I'm thinking is that one thing that CB's enable are conquests and that enables some large chunks of code being run to handle title transfers where things can go wrong if not set up correctly. So it doesn't have to be related to the CB's even if the CBs are necessary to create the CTD.

 

[Colossal_Elk]

Do you get anything in your exception log on your crashes? What I'm thinking is that one thing that CB's enable are conquests and that enables some large chunks of code being run to handle title transfers where things can go wrong if not set up correctly. So it doesn't have to be related to the CB's even if the CBs are necessary to create the CTD.

What steps should I follow to produce an exception log? I have -debug and -debugscripts enabled in the launch options, but I've never seen an exception log.

A little more information in case this helps narrow things down a bit. Just to test the CBs file, I've set up a mod where that's the only file included, and have it set to replace_path over Vanilla (so everything except the CBs are vanilla files). I've gotten a huge number of error messages including the familiar ASK_TO_DECLARE_WAR_INTERACTION_ACCEPT, however, the game is just 40 years shy of going for a 300 year duration without a single crash.

 

[richvh]

Exceptions, if generated, will be in Documents/Paradox Interactive/Crusader Kings II/logs/exceptions.log. They are also likely to produce a .dmp file in /dumps.

 

[Colossal_Elk]

Exceptions, if generated, will be in Documents/Paradox Interactive/Crusader Kings II/logs/exceptions.log. They are also likely to produce a .dmp file in /dumps.

Thanks. In this case, the game has generated no exception logs.