Persistent variable wants and oddities

[ajcross]

1. Could Persistent Variables have a limit of 255 characters instead of 28? I was creating dynamic message triggers and had to use 2+ pvar to create messages.

2. Persistent Variables appear to have a String variable and an Integer variable.

'Set Persistent Variable' sets the String and if the value to set is numeric, it sets the integer.

'Modify Persistent Variable' modifies the Integer for Add or Subtract and not the String. I noticed this when my debugging Show Alert would not show changes to the Integer, only the String.

This is also a problem when you want a variable set to the value of another variable like this:
Set persistent variable 'MyVar1' to "{MyVar2}"
It won't get the current Integer value.

3. Can Integer persistent variables be used for Quantity Value's?
This would allow more dynamic Condition and Action Logic.

Right now, I have 'Area contains' triggers to check for different quantity values such as =0 units, >=1, >=3, >=5, >=7, etc to spawn enemy troops. With a Persistent Variable for the Quantity Value, I could have one trigger to spawn when Area count falls below the Persistent Variable.
Area 'SomeArea' contains AtLeast {MyVarA} Any Unit owned by AllSides

Right now, I can add/subtract a persistent variable from another with several triggers like this:

Trigger 1
Set persitent variable 'MyTemp' to "{MyVarA}"
Trigger 2
Test persistent variable 'MyTemp' is AtLeast 1
Modify persistent variable 'MyVarB': Add 1
Modify persistent variable 'MyTemp': Subtract 1
Preserve Trigger

I would rather have one line:
Modify persistent variable 'MyVarB': Add {MyVarA}

Conditions for this:
*Area Contains, Countdown Timer is, *Has Credits, Elapsed Time, Every NN seconds, Own Units

Actions for this:
Create Unit, *Modify Credits, *Modify Persistent Variable, Start Countdown Timer, Wait

* marks my most desired commands to compare qunatities to persistent variables.

4. Could persistent variable Integers be set with quantities from other commands? This is would be the values from the same conditions:
*Area Contains, Countdown Timer is, *Has Credits, Elapsed Time, Own Units

My favorite would be:
Modify persistent variable 'MyVar': Quantity in Area 'someArea' of 'unit types' owned by 'side'

Credits could use $credits or could be:
Modify persistent variable 'MyVar': Credits owned by 'side'

5. Could commands for Integer and String persistent variables be separated? This would avoid data type conflicts and be less confusing for a mission author.

I would:
a. make "Modify Persistent Variable 'text': Set" be the command to set the Integer value
b. stop "Set Persistent Variable" from setting the Integer value.

[crakerz]

Andy,

Many of these have been talked about/asked for in other threads, and are great ideas. I wouldn't expect any great modifications to take place for a while though, now that v1.2 is released. Also, spiffcode has repeatedly stated its desire not to change too many things so current levels retain compatibilty between versions. Witness the "set pvar" issue in another thread (thankfully, there is a workaround). The things you suggest are very desirable, yet would require major revisions in the coding that would render all previous levels useless.

I do know that Scott has expressed a desire to see better logic, including things like Boolean operators, and the ability to use pvars for integer values. Maybe in the next major revision, who knows?

To add to some of your comments: all pvars are stored as text. You can only test that text for "integer" values, and you can only modify that text as an "integer" value. If you attempt to modify a "string" value, it will treat it as zero. For example, if you Set a pvar to "Hello" and then attempted to Add 10 to it, the result would be "10".


I was unable to duplicate your statement about setting a pvar to a pvar:

Set persistent variable 'MyTemp' to "{MyVarA}"

For one thing, the "{}" are not recognized/allowed in strings, as are not several other symbols (Heck, you can cause a level to crash or not even load with some symbol combos!) In fact, I've found it best to stick to Aa-Zz and 0-9. Could you please elaborate on how you were able to do that?

[ajcross]

[crakerz]

[ajcross]

[LawrenceA]