acm-mu/cyberta

A node.js Discord bot created to help manage help queues for TA Office Hours during the COVID-19 Pandemic.

cyberta's Issues

Show Students Queue

Summary

Show the students where they are in the queue when they type !queue.

Basic example

!queue

There are currently 10 people in the queue. You are #4!

Motivation

Per students request.

!afk command

Summary

A command that would allow for TAs to go AFK.

Motivation

In the event that they would have to use the bathroom or get a drink in between helping groups.

Feature Request: Add a non-alert Remove

Avery Request:
"A non-alert remove that doesn't alert students so that we can delete privately"

Feature request:

• remove w/o student alert

Some reacts appear as replies

Description

When going on or offline as well as showing the queue the bot replies with emojis rather than reacting.

Steps to reproduce

execute !online, !offline, or !ready

Expected result

They should be reactions instead and not another message.

Actual result

No reaction, but a reply.

Evidence

Persistent Queue

Jack Requested:
"Persistent Queue so that the Bot won't fail/crash in the middle of office hours"

Improvement

Remove all identifying ties to Operating Systems TA's.

Such as:

1. Discord IDs
2. Discord Names
3. IRL Names

Feature Request: Offline/On Mode

Jack/Student Requested:
"Offline mode to tell students that a TA is getting off for the night. Offline mode to tell that no TA's are on."

Feature Request:

• offline mode
• online mode
• reply if next is called when no TA's are around

Feature Request: !offline allows you to turn others off

Summary

A feature that allows one TA to turn another TA to offline status, in case they forget.
Use could be !offline "user ID" or "username"

Basic example

Avery forget to go !offline at the end of the session. Jack wants to set everyone to offline by 10:00pm so that everyone knows that the TAs are off.
Jack: !offline @Avery

Motivation

It would be annoying to have a TA left online when they are no longer online.

Error when executing `!ready` when person in queue

https://github.com/Jl5her/CyberTA/blob/2f6f71497b9b05cffb7c597d992edbc8a8dbb2be/officehours.js#L36

https://github.com/Jl5her/CyberTA/blob/2f6f71497b9b05cffb7c597d992edbc8a8dbb2be/officehours.js#L250

throws error when executing !ready when person in queue

  const msg = queue[readyIndex].message;
                                ^

TypeError: Cannot read property 'message' of undefined
    at ready (E:\Programs\gitrepos\CyberTA\officehours.js:36:33)
    at Object.exports.onReady (E:\Programs\gitrepos\CyberTA\officehours.js:250:3)
    at Client.<anonymous> (E:\Programs\gitrepos\CyberTA\bot.js:72:19)
    at Client.emit (events.js:315:20)
    at MessageCreateAction.handle (E:\Programs\gitrepos\CyberTA\node_modules\discord.js\src\client\actions\MessageCreate.js:31:14)
    at Object.module.exports [as MESSAGE_CREATE] (E:\Programs\gitrepos\CyberTA\node_modules\discord.js\src\client\websocket\handlers\MESSAGE_CREATE.js:4:32)
    at WebSocketManager.handlePacket (E:\Programs\gitrepos\CyberTA\node_modules\discord.js\src\client\websocket\WebSocketManager.js:386:31)
    at WebSocketShard.onPacket (E:\Programs\gitrepos\CyberTA\node_modules\discord.js\src\client\websocket\WebSocketShard.js:435:22)
    at WebSocketShard.onMessage (E:\Programs\gitrepos\CyberTA\node_modules\discord.js\src\client\websocket\WebSocketShard.js:293:10)
    at WebSocket.onMessage (E:\Programs\gitrepos\CyberTA\node_modules\ws\lib\event-target.js:120:16)```

Feature Request: Clear

Brad Requested:
"Clear command for the queue as well as !next messages for the sake of cleanliness."

Feature Request:

• clears queue
• while clearing the queue, also clears the !next messages

Feature Request: Remove (Student Version)

Student requested:
"I'd like to remove myself from the list"

• Feature: student can call a command to remove themselves from the queue (but not others)

TAs names are null when they don't have a nickname.

Description

When a TA does !ready, if they don't have a nickname it prints null is ready.

Steps to reproduce

Must be a TA to replicate. Reset your nickname, add something to the queue, and ready from the TA_CHANNEL.

Expected result

Instead should use username if they don't have a nickname.

Actual result

TAs name is null, and the students don't know who is ready for them.

Evidence

https://prnt.sc/ruaspr

Crashed - when readying unknown user

@6:00 Friday April 3rd:

Brad experienced a crash when readying a user due to unknown reasons.
Name of User: John Austin

Could be for a number of reasons:

1. User left the discord?
2. User left the channel?
3. Queue object array had issues?

Error Log:

2020-04-03T22:52:01.058610+00:00 app[worker.1]:     at Client.<anonymous> (/app/bot.js:26:25)
2020-04-03T22:52:01.058611+00:00 app[worker.1]:     at Client.emit (events.js:311:20)
2020-04-03T22:52:01.058620+00:00 app[worker.1]:     at MessageCreateAction.handle (/app/node_modules/discord.js/src/client/actions/MessageCreate.js:31:14)
2020-04-03T22:52:01.058622+00:00 app[worker.1]:     at Object.module.exports [as MESSAGE_CREATE] (/app/node_modules/discord.js/src/client/websocket/handlers/MESSAGE_CREATE.js:4:32)
2020-04-03T22:52:01.058623+00:00 app[worker.1]:     at WebSocketManager.handlePacket (/app/node_modules/discord.js/src/client/websocket/WebSocketManager.js:386:31)
2020-04-03T22:52:01.058623+00:00 app[worker.1]:     at WebSocketShard.onPacket (/app/node_modules/discord.js/src/client/websocket/WebSocketShard.js:435:22)
2020-04-03T22:52:01.058623+00:00 app[worker.1]:     at WebSocketShard.onMessage (/app/node_modules/discord.js/src/client/websocket/WebSocketShard.js:293:10)
2020-04-03T22:52:01.058624+00:00 app[worker.1]:     at WebSocket.onMessage (/app/node_modules/ws/lib/event-target.js:120:16)
2020-04-03T22:52:01.255157+00:00 heroku[worker.1]: State changed from up to crashed