-
-
Notifications
You must be signed in to change notification settings - Fork 444
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unopresses Mentors (adds mbwoink) #8124
Conversation
But why? |
DUH!!! |
Now we just need the ability to do !mwho in discord |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But why?
Main reason for this is that the current system of using discord to mhelp someone requires a ckey.
When observing; mentors seem to want to go out of their way to try to help people that are struggling.
Right now if someone is clearly struggling to do something they either have to get an admin to communicate something to him or do something weird like spawning spawning them in as a helpful ERT to give them a mini tutorial on how to do something (for example on how to sett up the engine etc)
We as staff have very convenient tools to help (PM bwoink, Subtle message, narrate , osay (to make objects talk) etc ) but assisting us by delegating these types of inquiries to mentors is what they are for.
Having this tool be in the right click menu will only stop them having to go through a backwards method such as asking admins for a ckey etc.
Right now some mentors even suggested going through replays to try to get a ckey just to mhelp someone which is too indirect and out of the way but they literally don't have other options.
I see no reason why a mentor should not be able to offer someone assistance when appropriate by right clicking similar to how staff can message players.
BWOINK! The thing goes in the thing |
merge please I need this too |
but how will we oppress mentors now good |
Id really much have it as an ability only observers can use |
Intent of your Pull Request
Explain what the purpose of your PR is.
Mention if you tested your changes. If you changed a map, make sure you used the mapmerge tool.
Mention if your PR is related to an issue.
You can type "Fixes issue #6" and issue 6 will be automatically closed when your pull request is merged. This is much easier for everyone.
Edit the changelog at the bottom for changes that are noticeable by the players. Remove it if this isn't the case.
If you add a name after the ':cl', that name will be used in the changelog. Leave it empty to use your GitHub name.
Include [admin] in the title if it's something admin related.
Include [s] in the title if you don't want it to be announced on discord and the server.
this PR is completely untested
Changelog
馃啈
add: Mentors can now mentor-PM people via right-click
/:cl: