You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It could be useful to ban a certain mapper from ever being requested. !banmapper [name]
Presumably this would just check the name of the mapper before adding the request, and if it matches a banned name, it would just state that the song has been banned.
The text was updated successfully, but these errors were encountered:
Feature already exists, just not generally released.
There's already a mapper.list and mapperban.list aswell as list manager functions in the unreleased version of the code.
One is used for approving maps when adding newest maps from beatsaver.
I'll try and release these to the general public once the list manager functions are a little more polished.
---------- Original Message ----------
From: megalon <notifications@github.com>
Date: May 6, 2019 at 3:57 AM
It could be useful to ban a certain mapper from ever being requested. !banmapper [name]
Presumably this would just check the name of the mapper before adding the request, and if it matches a banned name, it would just state that the song has been banned.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.
It could be useful to ban a certain mapper from ever being requested.
!banmapper [name]
Presumably this would just check the name of the mapper before adding the request, and if it matches a banned name, it would just state that the song has been banned.
The text was updated successfully, but these errors were encountered: