If it helps, i could potentially put put an adventurers log event, but that will obviously not be centralised data, so not that helpful.
It potentially could be helpful given we have access to the Clan HiScores through its API which populates a list of all of our Clanmates and we got the RSS Feeds from the Adventurer's Log. It would just require a bit of coding, but a script could be generated to combine the two by a third party website or spreadsheet. I mean it would fail if our Members had privacy toggled on their Adventurer's Log, but I'm sure they'd like to have it public given the right motivation like a tracker. We all know Clanmates love trackers and competing against each other.
If it helps, i could potentially put put an adventurers log event, but that will obviously not be centralised data, so not that helpful.
It potentially could be helpful given we have access to the Clan HiScores through its API which populates a list of all of our Clanmates and we got the RSS Feeds from the Adventurer's Log. It would just require a bit of coding, but a script could be generated to combine the two by a third party website or spreadsheet. I mean it would fail if our Members had privacy toggled on their Adventurer's Log, but I'm sure they'd like to have it public given the right motivation like a tracker. We all know Clanmates love trackers and competing against each other.
+1 I believe this'd work just fine
Mod Maz
said
:
If it helps, i could potentially put put an adventurers log event, but that will obviously not be centralised data, so not that helpful.
To echo, whilst this is not a solution, it would be a short-term workaround. Ideally, we do not want clan leaders to have to rely on off-site tools for management, and an adventurer's log event is not readily accessible.
Would prefer an additional column on the Website Hiscores, or, alternatively, add a new interface on the Clan Window or Clan settings that records this data for us.
For example, the Clan Noticeboard in-game could contain its own In-Game HiScores, which could contain the same information that is contained on the Clan Page HiScores, as well as additional data such as amount of times capped, boss kills, deaths, etc. This would be game-engine work then, as opposed to web dev work.
Subzero
Incursione
2100+/130+ Clan, Avatar access for all.
24-Dec-2015 00:14:37
- Last edited on
24-Dec-2015 00:15:42
by
Subzero
There's the possibility that someone can change clan and it will conflict with how it's being represented. Unless the hiscore is representing a general point of capping, kills, and such, it will cause a differ in someone who has capped a lot for one clan, compared to just many clans in general.
Or, you could just have a hiscore for each individual clan, that could work too.
Alexander
said
:
I have one issue with this being a hiscore thing.
There's the possibility that someone can change clan and it will conflict with how it's being represented. Unless the hiscore is representing a general point of capping, kills, and such, it will cause a differ in someone who has capped a lot for one clan, compared to just many clans in general.
Or, you could just have a hiscore for each individual clan, that could work too.
Nonetheless, support.
It's contained within the Clan Page's HiScore/memberlist, not on the traditional HiScore section of the website
Subzero
Incursione
2100+/130+ Clan, Avatar access for all.
Well hopefully we might get something in the works now, a capping tracker came 3rd in most repeated suggestions for the Ninja Fixing Plans.
1. Avatar recall / tracking (+cc icon) [41]
2. Clan Chat mute feature [37]
3. Recording who has capped on member list (+API Support) [25]
4. Clan Chat Guest White List /Filters [21]
It was also my top suggestion as I also feel is would be a much valued update and potentially not too much work to implement.
Here is the mockup I would use as a minimum to track 4 states of citadel activity:
http://puu.sh/mlCah.jpg
Using this setup would give us a far greater activity tracking abilities compared to just fully capped, because I know many people do not completely cap if upkeep is met for example, but the majority do tend to hit the quarry masters approval.
Finally, it is essential to simply add API support with this setup, outputting the status as a mere 0 1 2 3, in order for off sites to track these with ease, and potentially add a total counter to keep track of pervious weeks in a much quicker time than it would for the web team to add(since they have a massive workload).