maskonk / swtor_op_bot Goto Github PK

If the operation is an 8 man a ninth should not be able to sign up. This should also cap roles at the standard maximum listed in the self.sizes. 24 man should have no role caps but still cap at 24 sign ups. The operation dictionary currently tracks how many are signed with the Signed property, however this is not updated when someone removes their signup currently.

Refactor spec command to take into account class and add a translation to Republic side.

Allow a user to sign as a reserve member directly. Main role should be reserve and alternative role should be a role. Alternative role should not be left blank for reserve. Alternative role should not be reserve.

Add side as an valid attribute to the valid operation command.

Accept any as a role and add them to one of the three role signups in the message. Should also add them to the two alternate lists. User should not need to have an alternate role if any is there main role. If they have a main role and any is their alternate role then they should be added to the main role as normal and added to both alternate role lists.

Implement propper error logging with dates and times to an output text file.

Have a json file with guild spefic configuration such as server admins and event channels to lock the bots operation commands to.

Accept variant sizes such as 1t5d or 6d in place of size. They should be added to the sizes dictionary and accepted as valid inputs. The code that currently uses the interger size for max signup comparison could use the sum of the keys.

As well with the commands allow the user to sign up by reacting on the original operation message. Valid reaction emoji's should be the regional indicators for T, D and H along with any custom emoji's with DPS. Heals or Tank in thier name.

The bot should track which side the operation is taking place. This needs to be added to the new operation command as an input, an accepted attribute for updating, the input validated and added to the operation message.

Add the ability to create a random operation, possibly using a subset of the self.operations dictionary. Filtered for full operations. Random should be added as a valid input when creating a new operations then the bot should choose one.

Add common variants of Emoji names to the list of working emojis for reaction sign ups.

The JSON already has a "Open" key for each operation. If the value if False the sign command should return an error message. The add command should still work as normal.

Allow the operation creator to remove a sign up by name. Should be restricted to the operation creator or Admin using the existing check to stop trolls.

Command should look like:

-remove op_id name

Be able to add notes to the operation. Update those notes and display the notes in the operation message. Example:
Operation listing DF MM and note adding only first boss.

Have adding a second role emoji add an alt role.

Port the excuse command over from DnD bot and refactor to be more relavent for SWTOR.

Allow the operation creator to sign up someone else by name. Should be restricted to the operation creator or Admin using the existing check to stop trolls.

Command should look like:

-add op_id name

Add melee and ranged tags to spec command for dps specs.

Port the ask command over from DnD bot and refactor to be relavent to SWTOR.

The remove user command does not remove the user from the alternatives list.

Command raised an exception: KeyError: 'Any'
was the error caused by Goldy's command (-sign 1 any)

The bot does not currently give feedback for successful commands to reduce clutter. Idea is to add a tick emoji to the command to let the user know it is successful.

Remove ctx from rest of the non command functions and write tests for them.

Allow the bot to automate the signup roles so that if 5 DPS sign up for an 8 man one is moved to alternate role if possible. This should be based on sign up order with later sign ups being moved to alternative roles first where possible.