-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Sort !gamemedals by top bar #307
Comments
we sort by medal on purpose since it seems like most people typing !gm just want to see who's highest and lowest. lmk if other streamers want otherwise though, maybe some polls to ask chat in certain streams to find out? can re-open then thanks for opening your first issue! |
splitting it up for radiant & dire isn't a bad idea actually |
opening cause did receive feedback that people want this too |
i think most people prefer listing out by individuals from left to right, it wont make the message much longer than it already is and its easier to read too imo. can do a poll to see what the people like |
The behaviour should definitely be consistent regardless of the rank. Either remove the merging altogether, or only merge them when they're sequential. |
hahahaha,i guess ppl are used to it now? still feel its easier to parse when it is in order, but can just keep it as it is,less code for u! |
You need a larger sample size than 30 people.
…On Mon, 4 Sept 2023, 16:38 Woody3797, ***@***.***> wrote:
hahahaha,i guess ppl are used to it now? still feel its easier to parse
when it is in order, but can just keep it as it is,less code for u!
—
Reply to this email directly, view it on GitHub
<#307 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFA2KHON3QUBR4HCU4ERV4DXYXKUNANCNFSM6AAAAAAWT2Q4IM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
would it be ok if u try putting it in hero top bar order for a while,and see the general feedback from there? |
yeah of course |
Or, at the very least, by teams when applicable
The text was updated successfully, but these errors were encountered: