Does anyone know if @var can be used in random_lists, post 3.0?

[Pancakelord]

I remember trying to use @ Variables (declared elsewhere in this file) a while back, but the scripting engine wouldnt support it.

Have been having a look over the 3.0 - 3.03 change logs, but cant be certain, does anyone know if the above will now work? (and if not, if anyone's seen plans for it to work in LEM?)
Not a deal breaker, but using this would make it easier/neater to test things I'm working on.

 

[OldEnt]

Nope.

Do:

random_list = {
    1 = { set_variable = (...)1 }
    1 = { set_variable = (...)2  }
    ...
    1 = { set_variable =  (...)100 }
}

Courtesy of @corsairmarks .

Then do:

if = {
                limit = {
                    check_variable = {
                        which = variablename
                        value = 1
                    }
                }
                <effects>
                }
}
else_if = {
                limit = {
                    check_variable = {
                        which = variablename
                        value = 2
                    }
                }
                <effects>
                }
}
(...)
else_if = {
                limit = {
                    check_variable = {
                        which = variablename
                        value = 100
                    }
                }
                <effects>
                }
}

Stick it in the scripted_effect.

There are likely more ways around it.

 

[Pancakelord]

Nope.

Do:

random_list = {
    1 = { set_variable = (...)1 }
    1 = { set_variable = (...)2  }
    ...
    1 = { set_variable =  (...)100 }
}

Courtesy of @corsairmarks .

Then do:

if = {
                limit = {
                    check_variable = {
                        which = variablename
                        value = 1
                    }
                }
                <effects>
                }
}
else_if = {
                limit = {
                    check_variable = {
                        which = variablename
                        value = 2
                    }
                }
                <effects>
                }
}
(...)
else_if = {
                limit = {
                    check_variable = {
                        which = variablename
                        value = 100
                    }
                }
                <effects>
                }
}

Stick it in the scripted_effect.

There are likely more ways around it.

Ah figured as much, tried that not long after posting this, was hoping for something less clunky lol.
For now I've brute-force tested what I needed to (sticking Stellaris on an NVME was the best decision I've made in a while) but I hope they consider re-writing that trigger to support @ numbers.