Problem

ExprSecPotionEffect has no keywords or literal text, meaning it is attempted against nearly everything that hasn't successfully parsed. This has lead to many cases where errors would say "cannot use variable here" despite not being relevant, because the var was being parsed for ExprSecPotionEffect and faililng. This shows that we need a better error handling method for parsing, but in lieu of attempting a large project like that, I chose to change the pattern instead.

Solution

Uses a regex match instead of a literal number type pattern to avoid spurious cannot use variables here errors.

Testing Completed

Tested on own repository of scripts (hundred or so). No change to parse times and fixed the wrong errors.

Supporting Information

Completes: #8364
Related: none
AI assistance: none