Geoff the Medio wrote:
The rule that you can omit the "label =" part always applies.
Is that rule stated?
It's buried in the Conditions section:
"low = ", "high = ", etc., indicates an *optional* parameter name. All parameters must appear in the order indicated, so the names are not necessary to indicate which value is meant for which parameter. The name may be included, however (except for with the And, Not and Or conditions, which do not have or allow such parameter names).
Probably an example of what that means would be helpful, though.
I've observed that it can sometimes be omitted, but other times it doesn't seem to work. I wouldn't have guessed leaving off the "=" would make it work. Haven't noticed that before.
Except in cases where it would be ambiguous, it should always be fine to leave out the "param =" part. Are there specific examples where it doesn't work?
I didn't intend to exclude complicated examples. I just included the only two ways i was sure SetPlanetSize could be used.
OK, but the question being asked is how to illustrate things in the documentation. How many and what sort of examples should be included, given that "param =" can be left off, there are multiple variations per condition or effect about which parameters are specified or omitted, and parameters can sometimes take only a constant but sometimes can take a reference to something in game?