-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Vaesen dice roll commands not displaying proper die images #220
Comments
It's because I only have two emoji faces for this die: vaesenb6 (success) and vaesenb0 (blank - any other face) |
Oh? Is it an issue with implementing image files for the emoji faces, or do you just not have them for some reason? And if that's the case, would you consider implementing them if I got someone to make them and they were of appropriate quality? |
It was an issue related to emoji slots being limited to servers. Each supported game requires 6-12-24-40 extra emoji for each dice faces, sometimes way more with step dice, but a server could hold only 50 emojis for free. So the compromise was to use less emojis per dice. BUT.. now bots can accept up to 2000 slots. So new dice face emoji could be added easily. If you know someone who can draw them, I have all resources available here - in the "vaesen" folder. Format must be PNG/JPG/GIF 128x128, max 256 kB of size. |
Alright, I'll definitely see if I can get that stuff to you sometime soon. |
Just bumping to see if this has been checked recently, and to double check to see if the image files are good or if they need changes? |
Which command was used?
/roll vaesen
Issue Description
When executing a /roll vaesen command, the die results under "Details" show the results of your roll. However, the emojis displayed at the top of the app's response displays only :vaesenb0: emojis for all dice results, except for successes, where it then properly displays the :vaesenb6: emoji.
Steps to reproduce:
Priority this issue should have?
Low (formatting issues, things that don't impact operation)
Bot's Permissions
The text was updated successfully, but these errors were encountered: