Skip to content
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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[IDEA]: Custom Level-Up Messages #1081

Open
cotton105 opened this issue Jan 12, 2025 · 1 comment · May be fixed by #1083
Open

[IDEA]: Custom Level-Up Messages #1081

cotton105 opened this issue Jan 12, 2025 · 1 comment · May be fixed by #1083
Labels
💡 Idea Ideas, sugestions or feature requests

Comments

@cotton105
Copy link

Upon level-up, it would be nice for a server to have configurable custom level-up messages aside from the default "You've leveled up to Level x!"

Maybe it could support using the guild's custom emojis. It could also use a few placeholders to display some values that vary. Some proposals:

  • %l : the user's level
  • %d : level-up date
  • %t : level-up time

Of course, it doesn't have to use the percent (%) prefix. I'm not sure what the best practices are, regarding this topic. Whichever format would be most appropriate should be used.

@cotton105 cotton105 added the 💡 Idea Ideas, sugestions or feature requests label Jan 12, 2025
Copy link

atlanna bot commented Jan 12, 2025

Thank you for opening this issue.
A maintainer will get by as soon as practical to address this issue.

If this is a support question and not really an issue or suggestion, then please ask it in our Discord Server instead.

cotton105 added a commit to cotton105/Bastion that referenced this issue Jan 12, 2025
Allows admin to use `/config gamification` to set a custom level-up
message for users. It supports some predefined tokens: %%level%%,
%%date%% and %%time%%.

Fixes: TheBastionBot#1081
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡 Idea Ideas, sugestions or feature requests
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant