`;parsemembers` Rework

[Ragviswa]

Current Behaviour

Problems, Frustrations, General Description

;parsemembers is an old command written ~3 years ago. This means that the original intent of the command has been modified over time, it uses older programming practices, and some parts of the code are completely unused. In addition, there are now additional features that need to be added on top of it which is difficult to integrate due to the bloated and messy nature of the command.

Wanted/Expected Behaviour

Improvements, Additions, Changes

;parsemembers will be written from the ground up, keeping whatever features are necessary, adding any new features and improving the quality of life wherever possible. The exact changes are unclear, so will need to be investigated and scoped out with Officer teams.

Phases of the rework

The rework of the parse will happen in a couple of phases, in order to break up the work into manageable sections with realistic time-frames for completion. Currently the plan is as follows:

Phase 1

• port parsemembers.js to parse.js and add slash command version with subcommands. Options available are members, reacts, and basic
• improve the name matching behavior, as described by husky's comment below
• See Parse rework phase 1 #707 for a more detailed explanation

Phase 2

• Realmeye integration for guild leaks (could also be used for gear parse, but that is secondary)
• Automatic name changes
• Separate parse logging into a separate command (pending officer discussion on parsing)

Phase 3

• Leaker tracking through db correlations
• Switch to tesseract OCR because google is stinky

Phase 4

• website parse???
• ascend to godhood, striking down the mere mortals who dare to break the sacred raiding-rules

Tasks

Things to Do

Possible List of Changes:

• Improving Embed Formatting
• Ensuring all parse embed fields are necessary
• pre-processing improvements for OCR
• Having better matching on names for parsing (l's, i's and whitespace)
• Reconnecting set parsing using RealmEye
• Guild leaks via Realmeye
• Crasher/Leaker correlations from parse logs
• Automatic name changes via Realmeye

Current List of Changes:

• Fixing all ESLint Flagged Errors
• Adding VC-less Parsing to ;parsemembers #551
• Adding O3 Parse Type to ;parsemembers #550
• Bug Fix ;parsemembers Changes #657
• Add o3 parses to ;stats and ;leaderboard #658
• o3parses are not getting logged #662
• ;parsemembers is not logging Oryx 3 Parses for VC-less Runs #705
• ;parsemembers auto-selecting wrong raid #706
• Parse rework phase 1 #707

Paths to Files

• /commands/parsemembers.js
• /commands/afkCheck.js
• /commands/parse,js
• /data/quotas.json
• /data/currentweekInfo.json

Is it possible to change the name reassemble matching to match longest combination first? While that might make it do many extra operations I think the end result might be worth it. Maybe limit it to trying to combine up to 3 parts to reduce unnecessary combinations, since it's very unlikely an ign gets split into 4+.

For example, in this parse, NinjaBadDu got split into Ninja BadDu and Ninja Matched <@402311887141863424>, causing it to show the wrong user as crashing.