I'm having issues telling if a leveling function is actually disabled.
I have toggled "Only Announce Level-Ups Together With Role Rewards" on and off, while comparing it to /config troubleshoot, and it's not giving me any indication the function is actually off. I have also tried /config delete but it's still giving me that "ā
looks good" with everything I do.
We need it off in our server, and members haven't been getting level up messages because of it.
Solution:Jump to solution
Giving it Admin perms most definitely seems to have fixed it š
I'm so sorry for the slow back-and-forth. I somehow forgot that our server having a "verification role" that members must receive in order to see our channels causes obstacles for bots that join.
If they're moderation bots of any sort, we'd give them admin. If they're channel-specific, we'd give them what they need and full rein over their channel.
Since we need Lurkr to see the whole server, it needed Admin. And I just... didn't realize that <:doggo_concern:906480921266487306>...
16 Replies
You can use
/config check to view your servers configuration
Or you can use the wen dashboard as wellwell /config check is telling me it isn't even configured, and the dashboard has it off. So it should be off.
However, it's now setting in that we're running into another issue: people aren't gaining experience.
We swapped from MEE6 to y'all because I had good experiences using Lurkr in a private server, but we're hitting a lot of speedbumps with this transition.
I'm not sure if the config shows anything that could be causing members not to get any xp, but it certainly isn't happening for the average server member.
One of my fellow staff helped point this out to me.
Did you invite Lurkr with the necessary permissions? If you use the default invite link on the website and invite Lurkr again it will get the correct permissions it needs.
Or you can screenshot the permissions the highest role that Lurkr has in your server and I can take it a look
If nothing else you can try toggling the leveling function on and off using /config toggle
Would toggling it on and off not delete our leaderboard? That's what I'm worried about, and why I haven't done it myself yet. I don't know if toggling it off deletes our- well- everything relating to levels. 
I invited it through the Discord app and gave it all the permissions it asked for when it joined the server.
It's the 5th role in our hierarchy, above even moderators-
and I think I even went in after and gave it a few more permissions than it actually needed. 
ā«ļø In response to your question
Toggling the levels won't delete existing data, but it won't do anything either
The bae role permissions by themselves aren't sufficient (unless the bot had the Administrator permission)
You have to take into account channel permission overwrites as well
Try changing the leveling channels to a whitelist temporarily
And set the channels to the ones you've been trying to level up on
After that, use
/config troubleshoot and it'll tell you if it can or can't see those channelsOkay 
"Leveling Channels
āļø Looks Good"
I whitelisted a full 30.
Ideally I wanted all but two channels in the server to be xp gain channels, but the leveling as a whole has been giving us difficulty.
It's showing all of them on /config check
<:icon_levelup:1086286977118261318> @Sushi/Sockums (pls ping) has reached level 4
Is it working now?
<:icon_levelup:1086286977118261318> @CmdData has reached level 51
I don't think so. People appear to not be getting xp at all. Would giving the bot administrator permissions fix this?
I've realized that the main difference between Lurkr in the Private server I'm in and the Public Server I'm troubleshooting right now is that the Private one gave the bot Admin perms while the Public one (the problem one) hasn't, yet.
We have no issues with giving the bot Admin perms- so I'm gonna give them to the bot and see if anything changes. Y'all can let me know if anything should change, but for now I'm gonna chase this theory.
It probably has to do with our verification role, honestly. 
The bot doesn't have it so Admin perms would be the one override.
The bot doesn't have it so Admin perms would be the one override.