Adam Sechrest

@Raykyn55 Thanks for doing the `script_summary` arg. I see you identified yaml settings within that. I got something for you, that you can help me with. Take a look at...

PS - Here's how that works: https://github.com/rpherbig/dr-scripts/pull/5718

PPS - Here is the code in `dependency` that gives the help output: https://github.com/rpherbig/dr-scripts/blob/bb9cebcccf1909a55095d71d4f957066e89aace6/dependency.lic#L51

Had a couple of folks ask if they could mess around with this. This is like super alpha release and you'll see tons of spammy code comments still in here....

@rpherbig @MahtraDR I'm switching this from draft to ready for review. I'm going to try to recruit some testers but in the meantime if ya'll could look through the code...

Currently have a critical bug in the script, so not ready for merge.

With the help of @rcuhljr I fixed the critical bug in the script. It stemmed from a fundamental misunderstanding of how Ruby handles references to an object, and the issue...

Couple small commits. Being a little more verbose when live reloading triggers, and removing some spammy feedback now that the script is mostly finalized.

> The issue of nested code aside, this works fantastically for me. > > The "issue" is that I can't seem to have a trigger that parses variables, which honestly......

Thanks for the report. Is this only on slim lockpicks? Do any others lose the referenceable adjective?