-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add end command #32
Comments
Okay @thboss we'd have to change the endpoint to a POST request instead so we can give the match ID. |
q!end is not working throwing this error The above exception was the direct cause of the following exception: Traceback (most recent call last): |
@thewickerman22 the issue looks like somehow the endpoint to end the match is redirecting you to the home page, and the error is cause the homepage is returning an HTML response when a JSON is expected. I am not sure that the endpoint for the end command is working properly yet? The bot doesn't even have and end command right now, so I am assuming you are using @thboss's fork |
|
Add a command to end a match by the match's ID. There is now an endpoint to do this on the web side, so a corresponding method needs to be added into the
ApiHelper
as well as the command in theMatchCog
. Should require admin permissions.Calling the command should look like:
q!end 123456
Open to other ideas on names for the command.
The text was updated successfully, but these errors were encountered: