A Query? Broken Variable Evaluations?

[Zarathustra_the]

Since the patch release, I have noticed that there appears to be something wrong with the variable evaluation, is_variable_equal. It appears as if this condition is being ignored, either being regarded as implicitly true, or implicitly false at a seeming random variance. @Divine @Meneth Is there any way you can have a look at what is causing the issue. In my usage, it is used for a strict variable comparison. Perhaps has there been some issue with respect to the use of "" as in this code, numeric values are not declared with "" and variable names are.

 

[Romulien]

I've seen in some scripts that there's now a == that can be used for strict equality, as well as >, >=, < and <= for numeric comparison.

AND = {
  society_rank > 1
  ROOT = { society_rank == 1 }
}

 

[theStormWeaver]

I've seen in some scripts that there's now a == that can be used for strict equality, as well as >, >=, < and <= for numeric comparison.

AND = {
  society_rank > 1
  ROOT = { society_rank == 1 }
}

Hell yes. As a programmer, dealing with "=" meaning ">=" for so long has made a tiny twinge in a part of my brain. It's so nice to see proper comparison operators

 

[ngppgn]

@Romulien Note that the comparaison operators only have functionality mostly for the newly added conditions.

@Zarathustra_the There is a. Known bug where variable operation misfunction when manipulating two variables (as opposed to a variable and a value) that might be causing your issue. Hopefully will be fixed for 2.7.1

 

[Zarathustra_the]

@Romulien Note that the comparaison operators only have functionality mostly for the newly added conditions.

@Zarathustra_the There is a. Known bug where variable operation misfunction when manipulating two variables (as opposed to a variable and a value) that might be causing your issue. Hopefully will be fixed for 2.7.1

Well it has broken the entire Dueling and Magic systems in the Warhammer mod. as they use a lot of variable comparison...

 

[Divine]

We're actively pushing for the fix to get in as soon as possible in an upcoming patch.

 

[vukica]

Hell yes. As a programmer, dealing with "=" meaning ">=" for so long has made a tiny twinge in a part of my brain. It's so nice to see proper comparison operators

"=" still means ">="
The difference is that you can now explicitly use ">=".

And OFC, "==" which is entirely new.

 

[Zarathustra_the]

We're actively pushing for the fix to get in as soon as possible in an upcoming patch.

That's good to hear, so first patch then? I mean it is kinda critical for some of the mods out there that this be fixed, else they cannot properly update to 2.7

 

[Meneth]

I've seen in some scripts that there's now a == that can be used for strict equality, as well as >, >=, < and <= for numeric comparison.

AND = {
  society_rank > 1
  ROOT = { society_rank == 1 }
}

Note that this only works for new triggers. The old ones don't support this syntax at this time.

 

[theStormWeaver]

"=" still means ">="
The difference is that you can now explicitly use ">=".

And OFC, "==" which is entirely new.

I understand that, but it's nice that I can be explicit. I'm trying really hard to ignore my refactor itch, but it's getting tough because I also wanna re-jigger my ids and re-do all the localization keys from before I found the style i like.

EDIT: Just saw Meneth's post. Now I am sad panda. Suppose that makes it easier to avoid the refactor itch