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
The level system seems perfect to me, but if there was a way to activate it in one place, either discord or minecraft.
Since I have my own leveling system inside my minecraft server, and getting double ''you leveled up'' messages gets annoying.
It should be noted that I would like the level system on my discord server, but not on MC
The text was updated successfully, but these errors were encountered:
I forgot to mention this, you don't get a double leveled up, the message location depends on the very last message before levelup, if it was on discord you get the message on discord, if it is in-game you get the in-game message, as the levelup message depends on the channel used flr last message before levelup (by default)
I forgot to mention this, you don't get a double leveled up, the message location depends on the very last message before levelup, if it was on discord you get the message on discord, if it is in-game you get the in-game message, as the levelup message depends on the channel used flr last message before levelup (by default)
I understand, but what I was referring to is that I have several level systems on my server, by skills, jobs and etc.
And these throw "you leveled up" messages, and many of these messages become annoying, now an additional one that levels you up just by typing... I don't like it at all.
What I love is Discord's level system, but I want a way to disable this level system on my minecraft server (in-game)
The level system seems perfect to me, but if there was a way to activate it in one place, either discord or minecraft.
Since I have my own leveling system inside my minecraft server, and getting double ''you leveled up'' messages gets annoying.
It should be noted that I would like the level system on my discord server, but not on MC
The text was updated successfully, but these errors were encountered: