dr-scripts
dr-scripts copied to clipboard
[script][card-collector] Create script card-collector
Useful fire-and-forget script if you're collecting cards. Doesn't take arguments, requires yaml settings:
card_bags:
fresh: bag1
duplicates: bag2
Takes recently acquired cards from whatever bag you designate and attempts to file them in your collector's case. If they won't fit, puts them into a second bag you designate for duplicates.
I run 4 collection cases presently and use a macro to do the card stuff. I have 4 different locations each with a collection case. It starts with the first one, moves any not entered into the first case to the next location and repeats.
@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 this file called base-help.yaml
: https://github.com/rpherbig/dr-scripts/blob/master/data/base-help.yaml
I've got a nice set of comments at the top of the file that show you how to use it. You can also look at some examples. If you add to this file your script and settings, when anyone does a ;card-collector help
in-game, not only will they get the script summary, but they'll get a printout of the yaml settings used in the script.
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
I'd like to see the option for nth level of collection cases. No, not because I have four collections going on. Nope, certainly not that. Nothing to see here, move along. :smile:
I'd like to see the option for nth level of collection cases. No, not because I have four collections going on. Nope, certainly not that. Nothing to see here, move along. 😄
I mean, could cycle through additional cases if it doesnt fit in one, not a bad idea tbh. Adding a second would be as hard/easy as adding a twenty-second.
Should we add the new setting to base.yaml
with a description?
After those comments are resolved, this looks good.
Should we add the new setting to
base.yaml
with a description?After those comments are resolved, this looks good.
Added blank, so script will still proc the error if they're not filled in.