-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
ChangeA modification to something that existsA modification to something that existsFeatureA new piece of functionality that has been introducedA new piece of functionality that has been introducedLost HallsThis relates to the Discord Guild named "Lost Halls"This relates to the Discord Guild named "Lost Halls"Quality of LifeAn improvement of something that existsAn improvement of something that existsShatters/MoonlightThis relates to the Discord Guild named "Shatters/Moonlight"This relates to the Discord Guild named "Shatters/Moonlight"
Description
Main issue: #552
Parse Explanation
A couple big things have changed with this parsing update:
/parseis now a slash command, because I can- You now have options for the type of parse you'd like to run, which are known as
subcommands
The subcommand you are likely to be most familiar with is/parse members, which functions very similarly to the oldparsememberscommand (with a few improvements, of course). I've given a more detailed description of subcommands below, so check them out.
Members parse
args:
(raid) </who image>
Embed data:
- Potential alts
- crashers in members list (formerly
can reconnectlist)- crashers not in members list/unrecognized names
- deafened members
Subcommand: React parse
This is a way to easily output reactions in a parse-friendly format
alias:
reacts
args:(raid)
Embed data:
- Reactions, categorized by react
- Shows vc state (not in vc/deafened)
- gives
/lock <name>copypasta data
Basic parse
This is a barebones version of parsemembers, which does not rely on the afkCheck object and only compares /who against people in the specified vc. Use this if you are parsing oongus runs
alias:
basic
args:(vc) </who image>
Output data:
- potential alts
- crashers
- unrecognized names
- deafened members
Tasks
Discussion
Arg handling is a little bit rough, regular parse command parses the arguments wrong, since image is required and before vc
Do we need the crasherlist stuff anymore? I am pretty sure we don't want keys kicking without security permission, something to talk about to the officers.
Things to Do
- add getNotes to describe actually how to use the command
- add time back to the parse raid selection embed
- determine order of args and required/non-required
- update getNotes with arg order
- add in subcommand based argument checking
- port in the modal for determining raid for non-slash command (maybe just leave it and let specify a raid id)
- Add logic to determine raid, vc, if not specified
- image is an optional arg, make sure image is attached or image link is attached
- separate logging into a free function
- copy husky parsemembers, function style with passing arguments
- Resolve text detection features, using vision api document text detection/tesseract
- investigate name matching improvements as described here
Examples
Screenshots
Metadata
Metadata
Assignees
Labels
ChangeA modification to something that existsA modification to something that existsFeatureA new piece of functionality that has been introducedA new piece of functionality that has been introducedLost HallsThis relates to the Discord Guild named "Lost Halls"This relates to the Discord Guild named "Lost Halls"Quality of LifeAn improvement of something that existsAn improvement of something that existsShatters/MoonlightThis relates to the Discord Guild named "Shatters/Moonlight"This relates to the Discord Guild named "Shatters/Moonlight"


