No – not for a single expression like that. CS can handle that just fine (it’s only “two things”).
John: What’s the whole choice block look like, not just that option? What you’ve shared with us looks to me like it should work.
Nope, you’re totally right. All numbers greater than 40 are also greater than 30; no reader would ever see that elseif line, because they would already be at *label shot.
The best way to fix that would be to put the >40 check first, and have >30 be the elseif condition (catching everyone with a stat between 31 and 40).
But if the author was set on keeping the current order of texts for some reason, they could do it with one fewer set of parentheses in each condition than you’ve got in your example.
*if (perception >30) and (perception <40)
text
*elseif perception >=40
text
*else
text
Nothing wrong with slapping everything inside extra parens if that works best for you. Gower does too. It’s just not strictly necessary.
Regardless, that error wouldn’t trigger just because of an unreachable elseif. I think we need to see the rest of the choice and its indents.