Adam Sechrest

Thanks for looking at that. This is less a bug and more the silliness of the DR parser. Ugh. This script utilizes our `common-*.lic` helper methods to try to put...

Ok, I've got an idea for this I'll try to work on that isn't a hack and may help as a last resort failsafe if the DR parser confounds Lich's...

Also, a thanks to @rcuhljr for significant help conceptually and programmatically.

Examples in use: ``` [trigger-watcher: Number of elements in history: 2] [trigger-watcher: All history is: {"stand"=>[], "peering_up"=>[#, #]}] > >;e echo Flags.read_matches('peering_up') --- Lich: exec1 active. [exec1: [#, #]] ---...

> This approach seems reasonable to me. A few questions: > > 1. Are there concrete plans now to use this functionality, or is this just in case someone wants...

> re: performance. I was wondering about that too. I suspect it'll be fine given how little what we do should stress a system, how short of a time most...

Ready for final review. After quite a bit of discussion, I'm opting to build a history for all flags. Said history will clear if a user pulls the history for...

@Chewmatca Wanted to thank you for contributing! -Gildaren in Discord

> until DRCA.cast_spell?(get_data('spells').spell_data['Gauge Flow'], @settings) end I just wonder if pulling a base setting, as opposed to a specified setting, is the right approach. Seems logical that some of the...

Huge kudos to @KatoakDR . This was a significant undertaking representing many hours of work, including work setting up unit tests at regex101.com (and he even got the dev of...