• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

unmerged(54749)

Second Lieutenant
Mar 11, 2006
128
0
www.bang-europe.org
Hi, I was modding a file for a while, usually I write on paper the modifications, give a number ( like 0.863) and save the 6 files of the scenario.

Now I got a big problem, in my last modification session I forgot to write them down, today I loaded it and received a Database Mismatch (Critical Error says), them I "Ignore" and it load the game and everything is fine (seams).

Then to avoid the Database Mismatch message, I loaded the previous session 0.863, but again the same error, I went back to 0.81 with no luck.

I can't explain why a previously working scenario now gives an error.

I tried quitting CK and reloading but nothing :(

Now I'm restarting XP for another attempt.

If there is anyone who is willing to try the scenario to help me solve what I messed, the zipped file is only 194 kB large. I can email it or pm.

Thanks
 

unmerged(21937)

Your Industrial Friend
Nov 15, 2003
9.557
1
Database mismatch is generally a case of two objects having same ID number. So if you do know what you have added recently, you can check their IDs out and see that there ain't two identical IDs there. Commonly happens that you add two characters and forget to assign both a unique ID, so you get two guys with same number. The error message (IIRC) tells you on what line the error is though or the problem ID, so you can try finding it a bit easier with the help of that.
 

unmerged(54749)

Second Lieutenant
Mar 11, 2006
128
0
www.bang-europe.org
Usually the error message (IIRC) tells you on what line the error is though or the problem ID, but not this time.

DatabaseMismatchError.jpg


The problem is that I haven't kept a record of my latest mod update.
I'm sure I haven't added any new character, but I have changed some character sex from female to male because when the scenario start it creates too many women to fill courts (too few men I think), may be this the problem?

EDIT: I even get the same error when loading a saved game, so I the problem may not be in the 6 scenario files but something is the DB or Config folder files. :confused:
 
Last edited:
Oct 27, 2002
1.075
0
Visit site
How about events?
Did you add/modify any recently?

Oh, sex change of a character shouldn't give you any problems...
 

unmerged(54749)

Second Lieutenant
Mar 11, 2006
128
0
www.bang-europe.org
Yes,

claims_events.txt
provincial_conversion_events.txt
advances_discovery.txt
advances_spread.txt
realm_disruption_events.txt

and

advances.txt (ID checked, seams ok)

Also I changed those, but reverted without result

world_names.csv
province.csv

MAY BE this the PROBLEM? from provincial_conversion_events.txt

Code:
		# added by Tprovic from here
		modifier = {
			condition = {
				type = from
				condition = {
					type = owner
					condition = { 
						type = or
						condition = { type = title value = BYZA }
						condition = { type = title value = BYZA }
					}
				}
			}
			factor = 2
		}
		# added by Tprovic until here

EDIT:
Changed in the following way but still Database Mismatch error keeps popping

Code:
		# added by Tprovic from here
		modifier = {
			condition = {
				type = from
				condition = {
					type = owner
					# condition = { 				#to avoid possible database mismatch problem
					#	type = or
						condition = { type = title value = BYZA }
					#	condition = { type = title value = BYZA }
					#}
				}
			}
			factor = 2
		}
		# added by Tprovic until here
 
Last edited:

unmerged(54749)

Second Lieutenant
Mar 11, 2006
128
0
www.bang-europe.org
Last edited:
Oct 27, 2002
1.075
0
Visit site
When I mentioned events, I was thinking that there are two events with the same id. That happens to me quite often, cause I copy paste events and then modifiy them and forget to change the id.

If there was something wrong with conditions, modifiers or effects, you'd probably get lhs error. The same is with missing {}.

EDIT: Oh, you solved it before I posted. :cool: