RoyaleAPI / cr-api-ux

User Experience and content issue tracker for RoyaleAPI website.
https://royaleapi.com
21 stars 16 forks source link

Clan War Readiness for entire clan #164

Open MrKillerCR opened 6 years ago

MrKillerCR commented 6 years ago

Currently, Clan War Readiness is only viewed individually.

It would be a "helpful" feature at least for the HISTORY tab of the clan.

I suggest it should be in the HISTORY tab. So, the system will not need to compile every single clan.

smlbiobot commented 6 years ago

Possibly. If I understand you correctly, you are suggesting that we provide this feature for clans who add our URL to their clan description as a reward for doing so.

MrKillerCR commented 6 years ago

Yes. Also, our clan is currently in silver league 3. I would like to know how ready everyone is for gold league.

On Wed, Jun 27, 2018, 7:00 AM SML notifications@github.com wrote:

Possibly. If I understand you correctly, you are suggesting that we provide this feature for clans who add our URL to their clan description as a reward for doing so.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/RoyaleAPI/cr-api-ux/issues/164#issuecomment-400552401, or mute the thread https://github.com/notifications/unsubscribe-auth/AmuxzuWX-u9fzPMxV0se8EvpNswWGUq5ks5uAx-UgaJpZM4U4nvv .

smlbiobot commented 6 years ago

@MrKillerCR for now you can go to the analytics page. I’ve just pushed a change so that you can click on a member’s name and see readiness. It will not load that for every single person at once mostly because it is a relatively expensive call — but if you feel like it you can tap on all of them…

screen shot 2018-06-27 at 12 59 13 pm
MrKillerCR commented 6 years ago

Alright. Thank you! That's fair enough.

On Wed, Jun 27, 2018, 7:40 AM SML notifications@github.com wrote:

@MrKillerCR https://github.com/MrKillerCR for now you can go to the analytics page. I’ve just pushed a change so that you can click on a member’s name and see readiness. It will not load that for every single person at once mostly because it is a relatively expensive call — but if you feel like it you can tap on all of them…

[image: screen shot 2018-06-27 at 12 59 13 pm] https://user-images.githubusercontent.com/25040297/41956945-f2e254b4-7a17-11e8-8dd9-9e7ca57ae6ed.png

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RoyaleAPI/cr-api-ux/issues/164#issuecomment-400560061, or mute the thread https://github.com/notifications/unsubscribe-auth/AmuxzmKYocd_qVWNhqOlbCIwUbj0D4Otks5uAyjegaJpZM4U4nvv .

smlbiobot commented 6 years ago

With this feature available, do you still require the suggested feature? I can’t promise when I would be able to get to it. The feature on the analytics page was made, however, to help leaders decide if a member’s poor performance can be attributed to his lack of card levels.

MrKillerCR commented 6 years ago

I tried it for a couple minutes. As of now, the only downsides that I found is the extra details will be gone as soon as I change the sorting system. (This is after I tap every single player). Also, by taping for extra details, the number of players that I can compare all at once (in my 15.6" screen) is significantly reduced.

To be honest, yes. I still would like to require the suggested feature. It is much easier to compare having two tabs open than having the information all in one tab.

I personally am a leader of a clan and yes, I would like this feature because I would be able to decide and compare if a member's poor performance is due to his underleveled cards. Or conclude that the member is still having a poor performance even though he is significantly clan war ready for the league.

On Wed, Jun 27, 2018, 8:05 AM SML notifications@github.com wrote:

With this feature available, do you still require the suggested feature? I can’t promise when I would be able to get to it. The feature on the analytics page was made, however, to help leaders decide if a member’s poor performance can be attributed to his lack of card levels.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RoyaleAPI/cr-api-ux/issues/164#issuecomment-400565553, or mute the thread https://github.com/notifications/unsubscribe-auth/AmuxzqMX_Igz-gpruGzsYHbdrw2GMKVJks5uAy64gaJpZM4U4nvv .

smlbiobot commented 6 years ago

Tapping the sorting system will remove the layer, because the layer is added as a table row with large column span and that layer will mess up the sorting.

MrKillerCR commented 6 years ago

Ohh I see. I would prefer it to be in the History section and will load for every single player. So, it would be exclusively and easily compared. Also, having it in history will reduce server traffic(?) for that information coz not every clan will be able to have this feature.

On Wed, Jun 27, 2018, 9:23 AM SML notifications@github.com wrote:

Tapping the sorting system will remove the layer, because the layer is added as a table row with large column span and that layer will mess up the sorting.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RoyaleAPI/cr-api-ux/issues/164#issuecomment-400585761, or mute the thread https://github.com/notifications/unsubscribe-auth/AmuxzmeexkJPZ7cuA4njJ1-noZcydBdoks5uA0D6gaJpZM4U4nvv .

smlbiobot commented 6 years ago

I will think about it, though timing TBD

jdischler commented 6 years ago

I would like this feature. Overall, RoyaleAPI does things better than I'm doing but there are a few areas where I'm stuck with my custom scripts. It'd be nice to have all the awesomeness in one spot (the royaleAPI site).

Tracking card requests (donationsReceived) is one area that RoyaleAPI could improve but I made a feature request "issue" about that one.

The other area is clan level card-readiness for war. Wading through all the members is just too hard.

I want a quick, high-level view for a lot of things so I made this for our clan (we're in silver league, close to gold league):

http://clash-wisconsin.online/card-report.html

...and it kinda suggests our clan will have problems with Gold League so getting into the next league as quickly as possible isn't maybe all that smart.

Something like this could probably be done a lot better by your group but sharing this in case it helps the creative process of coming up with something useful.

jaelson784 commented 6 years ago

I am in favor of this too. We are in the process of advising current members and screening new members based on their clan war readiness now that we are on the border of legends. It would be really nice if this were a sortable feature or available as part of the existing roster csv file.

6Sean commented 5 years ago

Looks like there may be some API constraints here?

ijm8710 commented 5 years ago

www.Howsmyclan.com somewhat shows this as a secondary method

6Sean commented 5 years ago

My thoughts: If it's in the API for the clan, it's easier to refresh & display with one call without storing a ton of data. If not, you have to aggregate the players (50 calls to the API), calculate the CWR, and display it - that's much more intense.

6Sean commented 5 years ago

True @ijm8710 - the difference is the raw number of users and usage.

howsmyclan.com has a global rank of 15,468,496 according to alexa.com image

royaleapi.com is sitting at 46,084 (and rising) image

They're much more capable of pulling, storing, and displaying data at a more localized level without their database exploding or costs increasing exponentially. Picture this more as an enterprise-level website that serves an enormous community of players and developers -- API enhancements and shorter-term storage is crucial... or LOTS of Patreons. :)

ijm8710 commented 5 years ago

Yep I just posted that link to help others have another method to see what they wanted as a tertiary resource, did not intend to try to convincee you guys to do anything different

6Sean commented 5 years ago

:+1: I read it as a response to my question about API constraints. Must have been a timing issue / coincidence.