Hello Brent and Jrwatts,
first of all, thank you for your kind response to my question.
Well, it is worth trying to clarify what I am doing.
Be patient: English is not my mother tongue and I find it difficult to express myself clearly in that language, especially in matters of a technical nature.
I simulated tables (like a CRT, for instance) in order to automate as much as possible the modules I’m working on. Everything works perfectly. The problem lies in the large number of trigger actions needed for the simulation.
In the present case, I have defined three variables: RANGE (the distance between two hexagons on the map), ASP (a differential between the forces of the units involved) and CH (the value of a random chit that varies between 0 and 9).
For example, the condition: RANGE =~1|2 && ASP =~3|4|5 && CH =~1|2|3 (I just removed the blanks introduced by copy & paste) represents the case where RANGE is between 1 and 2, ASP between 3 and 5 and CH between 1 and 3.
Unfortunately, 28 trigger actions are needed to simulate the entire table.
The problem I was working on is trying to drastically reduce the number of trigger actions needed.
To this end, I defined 28 markers, one for each condition to be evaluated in a trigger action, such as:
ASTA2 = “= ~1|2 && ASP =~ 3|4|5 && CH =~ 1|2|3” (without the ").
After numerous unsuccessful attempts, I inserted a single condition in the trigger action with the following syntax:
$ASTA1$ || $ASTA2$ || … || $ASTA28$.
This kind of syntax didn’t work initially, so I asked about the Vassal forum.
A strange thing happened yesterday: I just rewrote the trigger action from scratch, without making any changes and now it works!
Things like this have already happened in the past: it was enough to rewrite the condition and things began to work properly. Perhaps while typing I pressed some key which, although not clearly visible, still modified the condition string and Vassal interpreted it in a different way. I do not know.
In any case, even this problem has finally been solved!
Before I forget, I have another question to ask: I am currently still using Vassal version 3.2.17, but yesterday I downloaded the latest version released, 3.4.3.
In order to learn how to use it better, I would like to know if there is a documentation that describes in detail the changes made and gives some examples on how to use the new features that have been introduced after the version I currently use.
I thank in advance anyone who wants to give me explanations on the matter.
Panther 2010.