The Validator - Find errors quickly and with minimal pain!

[theStormWeaver]

So it definitely works? There was a comment here: https://forum.paradoxplaza.com/foru...ith-minimal-pain.597480/page-92#post-19717214

that for province it may not work, at least in the past.

It's used in the Widukind rebellion events, if those weren't working, I think we'd hear about it.
But I'll try to test it tomorrow morning to be certain.

 

[theStormWeaver]

Yeah, this doesn't work.
I took a second look at the Widukind event this happens in, and it's a *province* event, so ROOT is a province scope.
My bad! Sorry for wasting your time

 

[zeress]

Here's something that the validator seems to not be checking for; If you have a title history for a title that does not exist at all in /common/landed_titles/ you will have various strange issues in-game.
For example:

Say I had the history file
/history/titles/d_nonexistant
but "d_nonexistant" does not exist in /common/landed_titles/. If I were to try to search for anything beginning with a "D" it will cause the game to CTD

To re-iterate, having history files present for titles that don't exist in /landed_titles/ causes issues and this applies to b_, c_, d_, k_ and e_ equally.

 

[Jamie550]

Here's something that the validator seems to not be checking for; If you have a title history for a title that does not exist at all in /common/landed_titles/ you will have various strange issues in-game.
For example:

Say I had the history file
/history/titles/d_nonexistant
but "d_nonexistant" does not exist in /common/landed_titles/. If I were to try to search for anything beginning with a "D" it will cause the game to CTD

To re-iterate, having history files present for titles that don't exist in /landed_titles/ causes issues and this applies to b_, c_, d_, k_ and e_ equally.

Do you mean that when the file is named d_nonexistant, it needs a warning? If it is named d_nonexistant.txt, it should already get a warning similar to the following:

--- Error 1 of 1 ---
Invalid file
Invalid title file (name in wrong format or title does not exist): history\titles\b_aaa.txt

 

[zeress]

Yup, you're right sorry about that. It was mixed in a sea of other issues

 

[IoannesBarbarus]

Do you mean that when the file is named d_nonexistant, it needs a warning? If it is named d_nonexistant.txt, it should already get a warning similar to the following:

--- Error 1 of 1 ---
Invalid file
Invalid title file (name in wrong format or title does not exist): history\titles\b_aaa.txt

Could this be amended to not generate an error if the file in question is blank? This comes about when you remove a vanilla title, but don't use replace_paths for history for any of several reasons (e.g. you only want to override some of vanilla history): you need to override its vanilla history with a blank file. SWMH has this issue. For this use case there is no possible solution which doesn't presently cause Validator errors.

 

[allocater]

Anybody working on adding Stellaris?

 

[Jamie550]

Anybody working on adding Stellaris?

Not that I know of

 

[Jamie550]

v1.15.2: https://www.dropbox.com/s/q1i05aq5dbxqz6y/Audax.Validator v1.15.2.zip?dl=0

 

[allocater]

Not that I know of

I tried around a little and stumbled on the thing that stellaris uses:

@standardEdictCost = 150

to declare 'global' variables. The Validator says:

--- Error 1 of 1 ---
Parse Failure
Path: common\edicts\01_planetary_edicts.txt
Approximate location: Line 17, column 1
Error: Invalid character "@" at line 17, column 1

Is there a way to validate this, or is the "@" a hard-coded no-go symbol in the validator engine?

 

[Jamie550]

I tried around a little and stumbled on the thing that stellaris uses:

@standardEdictCost = 150

to declare 'global' variables. The Validator says:

--- Error 1 of 1 ---
Parse Failure
Path: common\edicts\01_planetary_edicts.txt
Approximate location: Line 17, column 1
Error: Invalid character "@" at line 17, column 1

Is there a way to validate this, or is the "@" a hard-coded no-go symbol in the validator engine?

The Validator supports many different formats (pdo, csv, yaml, fakeyaml, etc). The pdo format does not allow "@" at this time. If "@" gets added to Eu4 or Ck2 then "@" will be made to work in the pdo format. Otherwise you can write your own format similar to pdo which does allow "@". In theory all you have to do is drop a dll with the appropriate code into Extension\Bin and it should work.

 

[vyshan]

I keep getting issues like: finnish.109 is not a valid CharEventId.

Thing is the events work fine IG.

 

[Jamie550]

I keep getting issues like: finnish.109 is not a valid CharEventId.

Thing is the events work fine IG.

Do you have a download link?

 

[vyshan]

Here is the current version, it doesn't have the finnish events added yet. But I was encountering similar issues with 0.1 as well.

 

[vyshan]

Do you have a download link?

nvm I solved it. Turns out it was just minor issues, misnumbering and the like. I feel silly for asking.

The validator is really helpful btw.

 

[klee96]

Hello Jamie550,

for which version of Crusader Kings II is the Validator updated?

Thanks Klemens

 

[Jamie550]

Hello Jamie550,

for which version of Crusader Kings II is the Validator updated?

Thanks Klemens

It is supposed to be currently compatible with the 2.5.x series. I suspect 2.5.2 as it was released a few months ago and people have filed bugs since then.

 

[Colossal_Elk]

I'm not sure if it has been mentioned before, but there seem to be some problems with setting an age minimum for Validator's age errors. Even with very high age settings (say, 5000 years) it'll still report people under that age as being too old.

 

[Jamie550]

I'm not sure if it has been mentioned before, but there seem to be some problems with setting an age minimum for Validator's age errors. Even with very high age settings (say, 5000 years) it'll still report people under that age as being too old.

Can you post a settings file that doesn't work and specify which line(s) are problematic, as well as copy the actual error messages in? Also do any of the other settings work?

 

[Colossal_Elk]

Can you post a settings file that doesn't work and specify which line(s) are problematic, as well as copy the actual error messages in? Also do any of the other settings work?

Sure, I can post some of what's going on. Here's an example from the ValidatorSettings.txt file, which is the only thing I changed within the file. It's within the mod/ folder where all the game mod folders are located:

###########################################
# CHARACTER HISTORY
###########################################

# Disables checks that dates are in chronological order, and that there are no duplicates within groups of dates.
#AddFlag = CharacterHistory.NoComplexDateChecks
# Disables checks that all other events are between the single birth and death date.
#AddFlag = CharacterHistory.NoBirthDeathCheck
# Sets the minimum age of marriage
(SetVar CharacterHistory.MinAgeOfMarriage) = 16
# Sets the minimum age of being a parent
(SetVar CharacterHistory.MinAgeOfParent) = 16
# Sets the minimum age of being a guardian
(SetVar CharacterHistory.MinAgeOfGuardian) = 16
# Sets the maximum age of someone needing a guardian
(SetVar CharacterHistory.MaxAgeNeedingGuardian) = 15
# Sets the maximum age of someone
(SetVar CharacterHistory.MaxAge) = 500
# Sets the most days that the father can be dead before a child is born
(SetVar CharacterHistory.MaxDaysFatherDeadBeforeChild) = 300
# Disables twin check
#AddFlag = CharacterHistory.NoTwinCheck
# Disables bastard check
AddFlag = CharacterHistory.NoBastardCheck
# Don't enforce characters needing a death date
#AddFlag = CharacterHistory.NoDeathDateNeeded
# Don't do disconnected dynasty checks
#AddFlag = CharacterHistory.NoDisconnectedDynastyChecks

# These flags disable the corresponding checks for history, but only if the solution
# would make the birth date before year 1. What this means is say character X is married
# on 2.1.1. Then to be at the age of marriage, they would need to be born in year -14.1.1
# which isn't possible. So in that case errors are suppressed.
# 
# These flags are probably useful for early-year mods, which may have characters that should
# be born in BC years but can't due to engine limitations.
#AddFlag = CharacterHistory.NoMinAgeOfMarriageIfEarly
#AddFlag = CharacterHistory.NoMinAgeOfParentIfEarly
#AddFlag = CharacterHistory.NoMinAgeOfGuardianIfEarly

And then here's examples of the age minimum and the bastard checks still showing up:

--- Error 1 of 28 ---
At history\characters\altmer.txt [37727\2743.1.1\birth] (Line 4401, column 15):
This character is 261 years old. Check to make sure it is not an error.
--- Error 2 of 28 ---
At history\characters\altmer.txt [37726\2651.1.1\birth] (Line 4389, column 15):
This character is 329 years old. Check to make sure it is not an error.
--- Error 3 of 28 ---
At history\characters\altmer.txt [37725\2526.1.1\birth] (Line 4377, column 15):
This character is 258 years old. Check to make sure it is not an error.
--- Error 4 of 28 ---
At history\characters\altmer.txt [37724\2406.1.1\birth] (Line 4366, column 15):
This character is 274 years old. Check to make sure it is not an error.
--- Error 5 of 28 ---
At history\characters\altmer.txt [37723\2301.1.1\birth] (Line 4355, column 15):
This character is 272 years old. Check to make sure it is not an error.
--- Error 6 of 28 ---
At history\characters\altmer.txt [37722\2240.1.1\birth] (Line 4344, column 15):
This character is 248 years old. Check to make sure it is not an error.
--- Error 7 of 28 ---
At history\characters\altmer.txt [37721\2176.1.1\birth] (Line 4332, column 15):
This character is 121 years old. Check to make sure it is not an error.
--- Error 8 of 28 ---
At history\characters\altmer.txt [37720\2044.1.1\birth] (Line 4321, column 15):
This character is 317 years old. Check to make sure it is not an error.
--- Error 9 of 28 ---
At history\characters\altmer.txt [37719\1980.1.1\birth] (Line 4310, column 15):
This character is 335 years old. Check to make sure it is not an error.
--- Error 10 of 28 ---
At history\characters\altmer.txt [37718\1857.1.1\birth] (Line 4298, column 15):
This character is 375 years old. Check to make sure it is not an error.
--- Error 11 of 28 ---
At history\characters\altmer.txt [37717\1782.1.1\birth] (Line 4286, column 15):
This character is 264 years old. Check to make sure it is not an error.
--- Error 12 of 28 ---
At history\characters\altmer.txt [37716\1673.1.1\birth] (Line 4275, column 15):
This character is 257 years old. Check to make sure it is not an error.
--- Error 13 of 28 ---
At history\characters\altmer.txt [37715\1597.1.1\birth] (Line 4264, column 15):
This character is 212 years old. Check to make sure it is not an error.
--- Error 14 of 28 ---
At history\characters\altmer.txt [37714\1520.1.1\birth] (Line 4252, column 15):
This character is 237 years old. Check to make sure it is not an error.
--- Error 15 of 28 ---
At history\characters\altmer.txt [37713\1451.1.1\birth] (Line 4241, column 15):
This character is 271 years old. Check to make sure it is not an error.
--- Error 16 of 28 ---
At history\characters\altmer.txt [37712\1374.1.1\birth] (Line 4229, column 15):
This character is 267 years old. Check to make sure it is not an error.
--- Error 17 of 28 ---
At history\characters\altmer.txt [37711\1285.1.1\birth] (Line 4218, column 15):
This character is 217 years old. Check to make sure it is not an error.
--- Error 18 of 28 ---
At history\characters\altmer.txt [37710\1232.1.1\birth] (Line 4206, column 15):
This character is 258 years old. Check to make sure it is not an error.
--- Error 19 of 28 ---
At history\characters\altmer.txt [37709\1163.1.1\birth] (Line 4195, column 15):
This character is 281 years old. Check to make sure it is not an error.
--- Error 20 of 28 ---
At history\characters\altmer.txt [37708\1028.1.1\birth] (Line 4184, column 15):
This character is 236 years old. Check to make sure it is not an error.
--- Error 21 of 28 ---
At history\characters\altmer.txt [37707\946.1.1\birth] (Line 4173, column 14):
This character is 256 years old. Check to make sure it is not an error.
--- Error 22 of 28 ---
At history\characters\altmer.txt [37706\824.1.1\birth] (Line 4161, column 14):
This character is 311 years old. Check to make sure it is not an error.
--- Error 23 of 28 ---
At history\characters\altmer.txt [37705\699.1.1\birth] (Line 4149, column 14):
This character is 415 years old. Check to make sure it is not an error.
--- Error 24 of 28 ---
At history\characters\altmer.txt [37704\602.1.1\birth] (Line 4138, column 14):
This character is 301 years old. Check to make sure it is not an error.
--- Error 25 of 28 ---
At history\characters\altmer.txt [37703\552.1.1\birth] (Line 4127, column 14):
This character is 338 years old. Check to make sure it is not an error.
--- Error 26 of 28 ---
At history\characters\altmer.txt [37702\481.1.1\birth] (Line 4115, column 14):
This character is 236 years old. Check to make sure it is not an error.
--- Error 27 of 28 ---
At history\characters\altmer.txt [37701\335.1.1\birth] (Line 4104, column 14):
This character is 357 years old. Check to make sure it is not an error.
--- Error 28 of 28 ---
At history\characters\altmer.txt [37700\239.1.1\birth] (Line 4093, column 14):
This character is 241 years old. Check to make sure it is not an error.

At history\characters\reachmen.txt [18153\3316.1.1\birth] (Line 1126, column 15):
This character, 18153, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18152\3313.1.1\birth] (Line 1111, column 15):
This character, 18152, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18133\3343.1.1\birth] (Line 929, column 15):
This character, 18133, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18132\3339.1.1\birth] (Line 915, column 15):
This character, 18132, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18131\3349.1.1\birth] (Line 901, column 15):
This character, 18131, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18081\3323.1.1\birth] (Line 674, column 15):
This character, 18081, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18080\3353.1.1\birth] (Line 661, column 15):
This character, 18080, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18079\3351.1.1\birth] (Line 648, column 15):
This character, 18079, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18078\3348.1.1\birth] (Line 634, column 15):
This character, 18078, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18077\3319.1.1\birth] (Line 619, column 15):
This character, 18077, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18037\3291.1.1\birth] (Line 231, column 15):
This character, 18037, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18036\3289.1.1\birth] (Line 216, column 15):
This character, 18036, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18030\3286.1.1\birth] (Line 138, column 15):
This character, 18030, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18029\3259.1.1\birth] (Line 125, column 15):
This character, 18029, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18028\3256.1.1\birth] (Line 108, column 15):
This character, 18028, is a bastard/legit_bastard, but does not have the trait.

At history\characters\reachmen.txt [18027\3227.1.1\birth] (Line 94, column 15):
This character, 18027, is a bastard/legit_bastard, but does not have the trait.