Reformatting of #raidbot-info and #raidbot-commands embeds

[jiajieh01]

Current Behaviour

Problems, Frustrations, General Description

The ;mm command is currently becoming quite a popular tool amongst the Security and the Officer teams alike. ;mm identifies the mutual raiders between a set of input raids.

To put things in context, a Security will typically begin by running ;mm on a few raids in which a crasher was spotted. Very often in these analyses, the context inside of #raidbot-commands is useful. Therefore this typically will involve a lot of switching back and forth between the #raidbot-info and #raidbot-commands embeds; this act of switching is rather inconvenient and currently involves a lot of unnecessary trickery with the search bar.

How to Reproduce

Wanted/Expected Behaviour

Improvements, Additions, Changes

As a first attempt to remedy this, we propose the addition of links in the #raidbot-info and #raidbot-commands embeds that lead to each other, creating a reciprocal relationship between the two embeds. Further to that, the raid ID (message ID in #raid-status-announcements) will be placed in the footers of the parse and the #raidbot-info and #raidbot-commands embeds. The ;mm command will be also be re-organised so that it searches by raid ID rather than message ID.

Reasoning

Easier analysis for anybody executing the command. The raid ID operations also more inline with current practices and sets up a potential future wherein database queries are more common.

Tasks

Things to Do

• Add links in the #raidbot-info and #raidbot-commands embeds that lead to each other. Work out the best position for these.
• Add the raid ID to the parse of a given raid
• Add the raid ID to the #raidbot-info and #raidbot-commands embeds.
• Refactor ;mm so that it searches by raid ID rather than message ID