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

request: Nitro boost incentives #786

Closed
gc opened this issue Jan 22, 2020 · 2 comments
Closed

request: Nitro boost incentives #786

gc opened this issue Jan 22, 2020 · 2 comments

Comments

@gc
Copy link
Contributor

gc commented Jan 22, 2020

  • Every server wants boosters, and wants to keep their boosters
  • Giving perks to boosters is the best way of getting/keeping boosters
  • If Skyra could help servers provide perks for boosters, and every server wants boosters....

I'm suggesting a modular system for providing perks/incentives to nitro boosters.

For example: a configurable amount of emojis that boosters can manage through the bot - you could tell skyra that you want boosters to be able to manage 2 emote slots, then they can s!nitro emoji <upload_image> or something like that. So basically, skyra lets them manage only 2 emote slots through her. When they stop boosting, the emojis are deleted.

Things to consider: users can boost a server twice, boosts run out, admins can boost (so they should bypass some perks, e.g. the emoji idea)

@kyranet
Copy link
Member

kyranet commented Jul 9, 2020

This has been made possible thanks to discord/discord-api-docs#1537, but we might need to wait for @klasa/core migration as discord.js does not support it yet.

@kyranet
Copy link
Member

kyranet commented Feb 12, 2022

We'll stick with skyra-project/teryl#10 which is less specific. I personally can't think of more incentives, and even so, we can implement commands to manage those separately.

@kyranet kyranet closed this as completed Feb 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants