Adding O3 Parse Type to `;parsemembers`

[Ragviswa]

Current Behaviour

Problems, Frustrations, General Description

As it stands, all parses done through ;parsemembers log as a normal parse and give a standard pre-defined amount of quota. This is not scalable as different dungeons have different requirements for parsing and can be harder or easier and the quota reward should reflect this.

Wanted/Expected Behaviour

Improvements, Additions, Changes

Add a system that is configurable per-server which allows parses to give different amounts of quota depending on which raid it is executed on. This would require ;parsemembers to read the type of the current raid and log it on a per-server basis based on pre-defined links. This particular change requires adding o3 parses and o3 current week parses to Lost Halls. The quota for each parse is worth 1.5 points.

Alternatives

This could be done by having a new argument attached to ;parse. Another alternative is to have a set of pre-defined links between types of ;afks through templateIDs and give the corresponding parse type.

Reasoning

This will allow parsing to be scalable and configurable where different types of parses can award more or less points. There can also be more logging done to see what dungeons are being parsed more than others.

Tasks

Things to Do

• Add the relevant new configurable system or file for defining links between parses and templates
• Make the corresponding changes to ;parsemembers to support different types of parsing
• Make the corresponding changes to ;quota to award 1.5 points for the O3 Parse Type
• Connect the parsing Google API on the testing bot instance for testing
• Add relevant fields into the Database to support the O3 Parse Type
• Test to ensure the change works as intended

Paths to Files

• /commands/parsemembers.js
• /data/quotas.json
• /data/currentweekInfo.json