I'll be the first to admit I am very much a novice, if anything, of coding in any form. There is a roll query macro problem that is driving me nuts. But in looking at why it is falling apart I found the order of operations. Now, I don't know if this is possible, but why not change the order of operations so roll queries are handled first? Just have an analysis stage come first in the order, which scans the text and finds the last "?{" and resolves that first, start at the top of the order, and repeat until no more queries are present, then expand the first ability, back up to the last query present, and repeat. This would make basically infinite nesting possible. I dont know if that is possible given the program it operates in, but I think theoretically it could work. also to consider: make the "max" column for attributes be the default from which the @{ command draws from, and make a new command that effects the now "current" entry. This would make possible commands that effect, for example, current health, like heal spells among allies or even damage given the target has a name to draw from. if this already exists, let me know, cause I can't find it.
