Allow variables in Skill Mechanic
Summary
- skill{s=levelCheck<caster.var.powerscale>} @self
Instead of using orElseCast 100 times to cast levelCheck1, levelCheck2, levelCheck3, all the way up to 100 I can just use a variable to cast the specific skill I need.
Usage
%mmocore_level% - <caster.level> = a number, I can use that variablemath to cast my specific skill This would essentially allow an imitation of a loop, people can create any equation to cast specific skills
Value
Enumeration
Priority
I think this is higher on priority for more experienced users, I've seen a few requests for a workaround with Enumeration to avoid 100s of orElseCast
Implementation
Describe how you think your suggestion should be implemented.