Feature description:
I assume this isn’t a bug–seems more like it’s just the way the parser works… But I figured I’d ask anyway while I work on my NPS:
Do you have any plans to add a way to use both the “&&” and “||” conditional operators inside the same statement?
Problem solved:
Functionally? None. This is mainly a convenience request.
When writing custom strings with 3+ conditions, the number of cases can become quite large. This makes future additions troublesome.
Consider the following three-condition statements, where 123 all individually evaluate to true:
{text%|1 || 2 || 3%}
This prints “text”.
{text %|1 || 2 && 3%}
This does not print “text”.
Thus we must rewrite the second statement purely in terms of “&&” operators. This example must be expanded into three lines to avoid duplicate prints:
{text %|1 && 2 && 3%}
{text %|not1 && 2 && 3%}
{text %|1 && not2 && 3%}
Brought benefits:
Allows users to condense complicated string cases.
Easier for users to add new features to existing strings.
Other application solutions:
Grouping operators like “(” and “)”
Additional description and context:
To be clear: I do not need this feature. It is purely convenience. I’d guess most users aren’t cramming this much into one string 
Pic: current progress of one of my Queue strings.
Quick glance may reveal several “
” statements. Those boil down to three-condition statements like in the example.
I’m about to double those statements as well, to add Sleep Timer functions.
Screenshots / Mockup:
