Bug

[ORI]

My thaumaturgy roll works like this (This is a example of a 2nd level power so difficulty should be 5+ magic resistance if any:
Magic resistance merit is first captured by this line which should take the value of 2 if it exsist (incidently it is also the point cost of Magic resistance so it all should look nice on the character sheet:

   {charcheck: target, store, magicreschk, magic resistance}

The charcheck returns 'Null' for none magic resistance characters as they dont have magic resistance in their character sheet, but when I try to do the following in a roll:

   {rolldice: caster, invoke, <var.caster.castwilpwr>, 5+<var.target.magicreschk>}

Instead I get the result as shown in The Attached image of a roll with 0 difficulty for non magic resistanc characters  .

[Javokis]

That's because you combined 5+null which returns an error (thus the whole math equation returns 0), this is fixed in 0.3a, but in 0.2a, you're going to have to use {var} to change a null value into 0. In 0.3a {charcheck} will always return 0 if 'not found' thus ending this error problem and the need for an extra step to avoid it.

[ORI]

ok thanks, thought it might be that but it didnt make much sense since its a + not a *.

[Javokis]

On the topic of bugs,

I finally fixed the sun damage region bug... sortof. Instead of sun regions not doing any damage to vampires like they should, they at least do damage if you stand out in the sun damage areas long enough. I spent 6-7 hours debugging the cause for the damage override not working with damage regions - I'm going to have to rework script for other damage region effects too.

Ugh... 

[Azraelthe7th]

Ok, I've been trying out my Ride the Flames power and it's been giving me this error:

{check: compare, value, <var.caster.EXCEPTIONERROR>, is:equal:1}

the error being    

{check: compare, value, <var.caster.rideflames>, is:equal:1}

I have a var concatenation for the rideflames concatenation like so:    

{var: caster, rideflames, value, 1}

Any help?

[Javokis]

Activate logging and try the discipline again then attach the log file pertaining to your discipline. Also please attach your code to the discipline too.

[Azraelthe7th]

Ok, here's the log and command files for the discipline/power.

[Javokis]

Ok. Right off hand, you're trying to check a variable that you have not given life to. In this new version all undefined variables start out as 'null'. At the start of your script, you must first check if the variable is null by using the text compare rather than a value compare. Place the check for null at the start of your event.

;This will give your variable a starting value if it had not been instantiated yet.
{check: compare, text, <var.caster.rideflames>, is:equal:null}
    {var: caster, rideflames, value, 0}
{endcheck}

Another good idea is just to stop using values for variables that are only used as flags. Use a text variable instead so you wont have to worry about making the above line of code. Values should only be used for math - not flags. Actually, just change you check compares to text. That should fix the problem all together.

[Javokis]

Ok I found bugs in the feed script. I'll attach the new fixes for anyone who wants them in the repository.