Utility wanted - CK event syntax checker

[richvh]

After spending 5 hours debugging a handful of events submitted for LUCKS, most of it waiting for CK to load yet again so I could find the next error, the top of my wishlist is a way to check event syntax quicker, an external utility that could be left running, and read a file that I've just saved.

 

[unmerged(6777)]

That would be a real trick, since (as you've undoubtedly noticed) the syntax is not 100% uniform.

If you ever successfully manage to make one, please let me know. Until then it's Notepad and coffee for me.

 

[richvh]

Something that would at least make sure that the braces are balanced would be a good start.

 

[Orlando]

If you ever successfully manage to make one, please let me know. Until then it's Notepad and coffee for me.

I also use Excel to know what line is the error at, sometimes it is very helpful

O

 

[Coder]

i modified my eu2 event file parser to work with ck event files
http://coder.specialforces.ee/eu2/ckeventparser.zip

currently it mainly checks only syntax not semantics - it doesn't recognise this as an invalid value for age:
condition = { type = age value = old }

and i already found an error in lordship_events.txt file
(line 588, the "Legitimate son Revelead as a Bastard!" event has two action_a elements)

 

[richvh]

i modified my eu2 event file parser to work with ck event files
http://coder.specialforces.ee/eu2/ckeventparser.zip

Super!

and i already found an error in lordship_events.txt file
(line 588, the "Legitimate son Revelead as a Bastard!" event has two action_a elements)

Someone already reported that one on the bug forum.

 

[unmerged(21942)]

coder, you are our hero!

 

[richvh]

The CK event parser missed the missing right brace in this snippet:

		condition = {
			type = not
			value = {
				type = trait
				value = lustful
			}

 

[richvh]

Also missed the missing right brace in this snippet:

	action_a = { # 
		effect = { type = death value = spouse }
		effect = {
			type = random
			chance = 85
			effect = { type = add_trait value = kinslayer }
        }

 

[richvh]

Other things not caught:

nested condition

  condition = {
    condition = {
      type = is_married
    }
  }

condition after type = not (which takes value, not condition):

  condition = {
    type = not
    condition = {
      type = is_married
    }
  }

 

[richvh]

value without preceding type:

                        condition = { value = { type = age value = 35 } }

 

[Coder]

it should now detect missing braces
apparently i deleted a bit too much old eu2 event parser code
and those other things are not detected as errors because as i said, currently it doesn't check semantics
however, i'm planning to write all those condition/effect rules into the syntax/semantics database, althought it might take some time (because ck has tons of them )
edit: found two more errors: Provincial_Structure_Events.txt and sin_events.txt are missing some }

 

[unmerged(6777)]

it should now detect missing braces
apparently i deleted a bit too much old eu2 event parser code
and those other things are not detected as errors because as i said, currently it doesn't check semantics
however, i'm planning to write all those condition/effect rules into the syntax/semantics database, althought it might take some time (because ck has tons of them )
edit: found two more errors: Provincial_Structure_Events.txt and sin_events.txt are missing some }

As it happens, I was going through the Provincial_Structure_Events.txt today. There are no syntax errors in that file in the version that I have (08/03/2004).

There is one missing right elipse in event ID#5300 of the sin events file though.

 

[unmerged(6777)]

Note: you will have to write syntax rules for every command in each of the 3 types since in many cases they follow different rules. Don't forget to have your syntax checker take that into account.

Good example: virtually any condition you use in a spread event will result in an error (or it being non-functional, depending on circumstance) if you fail to specify whether it is a "to" or "from" condition - but those same broken events would work perfectly in a normal (non-spread) province event.

 

[Ibn]

I have no clue when my file is from as I edited it already, but the version I had of 'Provincial Structure events' did have one missing right bracket at the end, 'sin events' had two missing on the bottom as well.


Nice tool coder

 

[richvh]

Confirmed - the last event in 1.02's Provincial_Stucture_Events.txt and sin_events.txt are missing closing braces - 1 in event 990 in Provincial_Structure_Events.txt and 2 in event 5300 (the only event in the file) in sin_events.txt.