Closed wasdennnoch closed 5 years ago
It appears that even after setting up a modlog channel the strike command does not work and throws another error, rendering the strike command completely unusable.
@wasdennnoch I can't reproduce that second error in testing. Will follow up with user to find out more.
First error should indeed be ignored by commands for which ModLog isn't essential. Will fix!
First error fixed, will keep issue open in relation to second error.
Fixed in indev branch.
Please describe the problem you are having in as much detail as possible: Using the strike command without setting up a modlog channel results in an internal error related to a missing modlog channel.