-
Notifications
You must be signed in to change notification settings - Fork 21
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
Compact Version or way to hide #47
Comments
@SeaPlusPlush reopen if |
Wow, thanks for the super quick response. This is so much better, but there is a tiny problem in that it removes knowledge of what was being rolled from the dicebot (which cannot be edited or removed) A user could do something like use a 6d6k3 And then edit it to look like it was 4d6k3 Yes there is an edit tag when doing so, but it might not be super apparent when checking a lot of peoples stuff (or if they are deleting their messages). I feel as though having an "impartial" way to confirm what was rolled is needed. Also @arkie I cannot seem to reopen this issue. |
Hello @arkie, I was wondering if you have had a chance to look at this again? |
I feel like a proper fix would be to allow more customization in output instead of the present logic, where Definitely would probably be a good area to improve, but probably will not get a chance to do so in the near future. |
Hello,
When my workspace uses dicebot for public stat rolling, it really clogs up our channel (see below image). While I love the breakout, it adds quite a lot of clutter and I can't figure out how to remove or hide the dicebot messages (maybe there are ways but FYI I'm not an admin).
Anyway, I was wondering if there were a way for rolls like this to be compacted.
For instance, maybe running the command from the pic below (with an additional keyword)...
...has the following result:
Currently this is the result, imagine 6-8 of these in your channel 😱
![image](https://user-images.githubusercontent.com/47161428/53820982-81cb2680-3f32-11e9-9cce-6f20475f6cd0.png)
The text was updated successfully, but these errors were encountered: