Widget talk:Skyscale Rider

Alright so Incarnazeus has helped me to figure out the mapping between the achievement bits and each skyscale rift. What would be a pretty way to present this information? -Chieftain Alex 15:20, 16 May 2020 (UTC)

I've decided upon loading the map by default, and applying CSS to the page.

CSS bit isn't working at the moment, but the maps are working great. You can select which region to display via {{#Widget:Skyscale Rider|achievementid=4718}} --Chieftain Alex 20:39, 16 May 2020 (UTC)

Shiverpeak Mountains

Frostgorge Sound 1 and Frostgorge Sound 2 need to be swapped - the map indicated the other one to be missing for me (gave the api 20 minutes to be sure it is updated). —Kvothe (talk) 11:49, 9 July 2020 (UTC)

Kryta

See Talk:Skyscale Rider: Kryta; maybe a swap is needed for Gendarran Fields - can not confirm though as I had already completed the two in question. —Kvothe (talk) 11:51, 9 July 2020 (UTC)

Tarnished Coast

Brisban Wildlands 1 and 3 are swapped.

As a side note: Shiverpeaks and here again it was only the last missing point that was swapped. —Kvothe (talk) 12:05, 9 July 2020 (UTC)

Afaik the map is correct versus the API, it's only the tables that needed switching. -Chieftain Alex 18:50, 9 July 2020 (UTC)

My own comments are both for the API map. Sorry if that was not clear for this second one. —Kvothe (talk) 21:26, 9 July 2020 (UTC)

Not that you can prove it twice, but I was very meticulous when figuring out the bits:coords relationship, surprised there are any errors tbh (especially as I had most of the gaps in my data confirmed by another). -Chieftain Alex 22:01, 9 July 2020 (UTC)

I was skeptical of the remarks on the kryta talk page myself, even more as I read here that you had worked in cooperation with Incarnazeus - making single person errors unlikely having confimation from a second source already. Which is why I did not bring it up here and did not look into the Kryta discussion. But as I had not done the achievements myself (and still have to do elona and lw) I ran across those two instances which appeared to be wrong - both times I made sure that the API had enough time to catch up and eliminate false positives. As you already wrote I can not prove it again. —Kvothe (talk) 22:16, 9 July 2020 (UTC)

Not saving API key between sessions

I noticed that this widget is not saving my API key between sessions, while other widgets/templates do (e.g. {{Collection table header}}. It's a small hassle to grab the key each time, though I realize I am looking a gift-horse in the mouth, here. Greener (talk) 17:51, 1 October 2021 (UTC)

Not immediately able to reproduce with Firefox 92.0.1 (entered my key, pressed apply, waited for it to load, closed browser completely, opened new instance, loaded page, api key already there) -Chieftain Alex 18:47, 1 October 2021 (UTC)

I'm on Chrome. I closed and reopened once and the key was properly saved. I closed and reopened again and the key was gone. Potentially related to my state of being logged in or not, as Chrome does log me out when I close my session. Attempt 3 & 4 have all since saved, and the key may now be saved in both my logged in and logged out state? If I can find a way to reliably reproduce, I'll post again... Greener (talk) 19:00, 1 October 2021 (UTC)

And the key is gone once again, both logged out and logged in. The other keys are being kept properly. Wish I had more details to give. Greener (talk) 19:47, 2 October 2021 (UTC)

I think this is because of it not using local storage yet. Or rather it's because the widgets that use localstorage delete the cookie. So if you use this widget it will save the key in a cookie; if you then use another widget sharing permissions/the cookie name (Widget:Account achievements, Widget:Account dungeons or Widget:Account masteries) with this one it will transfer the cookie to local storage and then delete the cookie, rendering the key "forgotten" for this widget. Let me change this widget to local storage too so that doesn't happen anymore. Nightsky (talk) 21:02, 2 October 2021 (UTC)

Realised same thing. It's nightsky's rewrite deleting the cookie. -Chieftain Alex 21:08, 2 October 2021 (UTC)

It shouldn't forget the key anymore now. Please excuse the inconvinience/confusion this has caused. I thought i updated every widget, but evidently i missed two. The new insource: "<searchterm>" search is great for finding them though and i should have updated all now. At least there's no more occurences of setCookie that i could update. Nightsky (talk) 21:56, 2 October 2021 (UTC)