User talk:Medyro

Ghostly aura

Strawberry Ghost has a chance to grant. https://wiki.guildwars2.com/wiki/Ghostly_aura --Life Infusion «T» 20:37, 22 October 2019 (UTC)

That could be. I've only tryed a few of them and wasn't turned into a Ghost by any of them whereas i was turned into one imediatelly after the first time trying any of the other three Items so i concluded that it would't grant it; not thinking about the possibillity that it may only be a chance. Nightsky (talk) 03:36, 23 October 2019 (UTC)

Wvw objective chatlink

No idea what I was smoking that day to get the two the wrong way around. Apologies and thank you for fixing it. -Chieftain Alex 18:26, 8 November 2019 (UTC)

Apologies accepted. And while i might have fixed it; it's there in the first place now because of Your groundwork. As such, thanks for bringing it up. Nightsky (talk) 23:28, 8 November 2019 (UTC)

Discord

Hey. I'm sorry to see that you left discord; it was quite a surprise to all of us, but we'd like to make this right. Our discord is open to the public, but is not intended to be a replacement for talk pages. We expect our users to be aware of this when they join; to that end, I've added a warning to Guild Wars 2 Wiki:Discord and to the #help-and-rules channel on the discord itself pointing out that there is a possibility wiki-related conversations may get pasted onto talk pages for archival purposes. I'll understand if you choose not to return to the discord, but I hope you'll be willing to open a dialogue with us about what you feel went wrong and how we can improve your experience in future. —Idris 20:00, 23 November 2019 (UTC)

I'm aware that it's not a replacement for talk pages. I just do not apprecheate it that something i had written on there was put on a talk page withouth giving me a chance to do it myself. Maybe let me know i should put it there so i can put it there myself instead of just blantly copy pasting it withouth any consent or notice beforehand. Nightsky (talk) 01:29, 24 November 2019 (UTC)

Yeah, I get how that felt like a violation. I think it's important to bear in mind that when it comes to wiki-related stuff (specifically wiki-related, not random chatter), there's always a risk someone might move your input to a talk page, and copy-pasting is a lot easier and leaves less room for error than paraphrasing. I'll talk to Alex about it, though. —Idris 01:46, 24 November 2019 (UTC)

Re: Champion Ancient Ghost Captain (Defeat the threat to the festivities)‎

When this article was created, it was under another name. I guess you would know that since you were the one that moved it. For the most part, the enemies attached to this set of events are not unique - there's usually another champion-level enemy elsewhere in Dalada with the same profile. If the basic Champion Ancient Ghost Captain has the same abilities and attacks, then the appropriate info should be moved there, this article deleted, and the event relinked. SarielV 08:27, 29 December 2019 (UTC)

Alright, noted. I figured the same but wasn't quite sure. I still have on my to do list to double check the abilities of the basic Champion Ancient Ghost Captain, since they are only one short of what the Defeat the threat to the festivities! version has but since they appear to be different so far i put the combat abilities on the Defeat the threat to the festivities! enemy version page; haven't gotten to it yet though, since sleep and all. I guess i could also see about the attacks/skills (provided they appear in the combat log as i would imagine that they do) and if i should find that both abilities and attacks/skills are the same i can move the information and put up a {{delete}} request, otherwise i'll put things where appropriate; first have to get what skill information i can get from both enemy versions though to be able to check if they are the same and of course also the abilities of the other one still. Nightsky (talk) 15:21, 29 December 2019 (UTC)

Icons

Hey Nightsky. I just saw that you uploaded the icons for the shining aureate weapons. For each new patch someone batch uploads all new icons and puts them on User:Darqam/Dat Icons, from there one can move them to their correct name. —Kvothe (talk) 13:04, 18 January 2020 (UTC)

Thanks for the notice; i appreciate it. I'm aware of the existence of the Page. I just uploaded them myself because i want to avoid having to look at it because i don't want spoilers. I figured it would be better for the Pages to have icons though so i provided them using means i'm confortable with (the API) untill there's better. Feel free to replace my uploads with the ones on there. Nightsky (talk) 15:56, 18 January 2020 (UTC)

SMW decimal separator

Regarding {{#show:Mystic Clover#recipe3|?Has output quantity|link=none}} returning 0,33. I'm not aware of any case where the decimal separator of a smw query is "," instead of "."; e.g. using your query gives 0.308 (note the "." separator). So this edit should have no effect. It may have a negative effect, namely for output quanitities >= 1000 where the smw query adds the thousand separator "," on default. To be fair, so far we don't have any recipe which returns such a large quantity and #expr doesn't like "," as thousand separator so it would be broken anyways. Returning a plain number can be achieved by appending the suffix "#", namely ?<property># (see smw:Help:Displaying information#Plain (unformatted) printouts).

So no idea what made you think this edit is required, but I think your edit doesn't have any effect. --Tolkyria (talk) 08:38, 8 July 2020 (UTC)

I had set the interface language for the Wiki to german which resulted in the , being output instead of the ., since that is what is used as a separator for this purpose there. And while this implies that the output of semantic media wiki is ui language aware the expr parser function seems not to be since it then produced an error, complaining about the ,; expecting a (dot). So what i did might really seem to have no effect; untill one changes their interface language in the settings to one that uses , for separation of the decimal places and then tries it again in a preview somewhere - find what i have found - and then change it back. Adding a # suffix is probably something that would be helpfull for ensuring that everyone gets the same results regardless of which interface language they might be using and the intricacies in number formating associated with them withouth having to special case all possible format variations then. Nightsky (talk) 02:59, 10 July 2020 (UTC)

Sorry, I wasn't aware that the language also affects the smw number property printouts since I'm using en and I usually append the suffix "#" on default as soon as I'm using a number property.

But with this knowledge, the plain printout is the only way to do it properly. We simply can't replace one language decimal separators without getting negative effects from another language (e.g. thousands separator vs decimal separator), see also w:Decimal separator. --Tolkyria (talk) 11:08, 10 July 2020 (UTC)

No need to be sorry. There's nothing You have to excuse for; i can understand why You didn't understand at first. I have mine set to english as well and haven't noticed anything before either and i should have probably included that i some time after changing the template had switched through languages during testing to see if it breaks with any which i do sometimes recently. (For what it's worth i haven't seen anything break anywhere else i've done that before so that's a good thing.) I just thought i'd fix it though in case someone's actually using it as i happened to notice it when i was changing through them. And while i have done so in the best way i could Your version is obviously the better solution to this problem. I just didn't know there would have been a better way to do it. As such; thank You for fixing my fix. Nightsky (talk) 00:14, 11 July 2020 (UTC)

Different tokens

So why do we need different tokens per account widget- isn't that just annoying? -Chieftain Alex 22:41, 8 October 2020 (UTC)

Is some of it related to the changing cookie standards (e.g. for firefox) which have been throwing console messages for a while? -Chieftain Alex 22:42, 8 October 2020 (UTC)

Actually reading it again I don't really get what's going on anymore at all, if you could giev a summary that'd be useful. -Chieftain Alex 22:46, 8 October 2020 (UTC)

(Edit conflict) The idea behind it is that while for API keys you can select which permissions they have so it makes sense to store them in the same key based on the permissions given to them so that all widgets can use it if they require those permissions, for subtokens you can also limit the urls accessible via them which if they were stored similar like api keys are based on their permissions they might still be limited by the urls and not work with one widget while working just fine with another as while the permissions might be the same the urls used might not be. So i figured as the widgets seem to use mostly different urls that it would be beneficial to store the subtokens only local to them.

If you're refering to the "Secure; SameSite=Strict" bits i've added; i've done so only because i figured that it would be more secure if they are only sent over secure https connections and stay as local as possible. As they are pretty much first party cookies if i understand that correctly that change (if you mean SameSite=Lax per default) shouldn't affect us on the widgets.

Next i wanted to change them from using cookies to localStorage as there's no reason that they are sent to the server with every request but as i didn't wanted to do that now i've done it like so for the time being. Nightsky (talk) 23:05, 8 October 2020 (UTC)

Contact

Hey Nightsky, could you email me via the wiki? It will require you to set up an email on the wiki, first. There is something I would like to talk about privately with you. Greener (talk) 02:05, 20 November 2020 (UTC)

Hm.. wouldn't that disclose my email address to you? (I'm not sure how the wikis emailing system works.) Nightsky (talk) 02:12, 20 November 2020 (UTC)

It would only if we have a back-and-forth conversation, which is my intent. The initial emails will not disclose your email address. I totally understand if that discourages you. Instead, perhaps you could send me a message in-game? My account ID is Greener.6204 . I will do my best to be online either late tonight, or tomorrow. Greener (talk) 02:16, 20 November 2020 (UTC)

Late tonight or (would that also be late then?) tomorrow your timezone i assume? (Which i further assume to be UTC-8 (Based on {{List of administrators}})). If that's the case and it's your timezone i'm afraid but your later today won't work out for me so it would have to be tomorrow. But your later tomorrow should work (as it stands right now). (At least that's the only thing remaining of the things you listed; other days/times could work too of course.)

Should we do a thing then where i comunicate to you a somehwat random, difficult to come by by chance, value/string (or you give me one (or we could do a mixture of both)) which i then either first provide you with in game (or you alreay have it) and then put on the wiki using my account so you know it's really me? Nightsky (talk) 03:03, 20 November 2020 (UTC)

Good god, what have I done? Okay. So. cracks knuckles Open up your Guild Wars 2 launcher. Insert your account name and password, and log in. Once you've chosen a character to play, please look to the top left of your screen. There should be an icon which appears to be an envelop; click on it. This will open up a GUI element with a button labelled "Compose"; click on it. For the line labelled 'To:', please input Greener.6204. For the line labelled "Subject:", please input a subject of your own choosing. For the body of the text, please insert a message also of your own choosing. I will be using the combination of your Subject and Body choices to suss out if any received message is really from you. Finally, click on the button labelled "Send".

I will check for any in-game mail from you within a 24-hour period from the posting of this message. Please look for a reply from me within the same said period. Greener (talk) 03:47, 20 November 2020 (UTC)

Shall we do this song-and-dance again? Let me know at which point we should start. Greener (talk) 19:29, 12 November 2021 (UTC)

Sure. As i'm unsure about at which steps you're seeing points and which of those are an option i think i'd prefer from the start. I'll send you an in game mail once i've gotten the game to update; unless you happen to be online at the time, at which point we could potentially hash out a different starting point in /w too. Nightsky (talk) 20:26, 12 November 2021 (UTC)

.

-Chieftain Alex 19:26, 11 December 2020 (UTC)

Nightsky (talk) 07:14, 12 December 2020 (UTC)

Incorrect set numbers with broken highlighter

Hello Nightsky, the set numbers on the updated individual pages Template:Daily Fractal Schedule & Template:Daily Recommended Fractal Schedule each show set ranges from 1 to 15 as they should. However after transclusion into Fractals of the Mists#Daily Fractals, the set ranges now incorrectly go from 1 to 30 with 1 to 15 for daily frac and 16 to 30 for daily rec frac. The highlighter currently does not work on Fractals of the Mists for the recommended schedule even though it works fine on the individual template page. My guess is that there is some transcluded code from the two templates improperly interacting with one another causing the set number issue on the Fractals of the Mists page. Canopy (talk) 06:58, 2 January 2021 (UTC)

Thanks for the heads up! I've went ahead and fixed it. Your guess is partially correct (or possibly fully as i assume the following's what you actually mean). The template codes are interacting propperly with one another, just in a unintended way; that i didn't spot as i never checked the Fractals of the Mists page but only the individual templates (as you can probably tell). So, again, thanks for pointing it out to me. Nightsky (talk) 11:54, 2 January 2021 (UTC)

Very much appreciated, thank you for fixing. Canopy (talk) 19:55, 2 January 2021 (UTC)

About Lost Invasion

I see you leave comment for "The "Lost Invasion" thing is probably a bug, right? At least the API still has it. (https://api.guildwars2.com/v2/achievements?id=4166) But i can't seem to find it in the achievement pannel."

That one is hidden achievement, if you not clear that will not appear in your achievement pannel. so not be a bug. Wong8888 (talk) 21:36, 25 May 2021 (UTC)

Hm.. well that could be. I removed every achievement i could find in the achievement pannel from the old version of the Current Events achievement category page to see if anything remains. But i did not take note of it being hidden. So it could verry well be i don't have it. Feel free to correct the texts accordingly to where it went if you have it unlocked. Nightsky (talk) 21:50, 25 May 2021 (UTC)

Actually, you can check for Portal Panic page. More detail at there. Wong8888 (talk) 21:57, 25 May 2021 (UTC)

I've noticed that's there. It's why i removed it from "Current Events" seeing as it remained there without context. You're free to add it yourself now though. You don't need me to do the achievement and add it. If you have it already; go for it. Nightsky (talk) 22:23, 25 May 2021 (UTC)

Spirit Vale unnamed dialogue

In reference to this change https://wiki.guildwars2.com/index.php?title=Spirit_Vale&curid=158015&diff=2287019&oldid=2287011

This is the symbol used to separate the years in the tombstones https://imgur.com/a/haVS5f2 It very much looks like an underscore

The gravestones aren't actually gravestones. They are nameless objects. While Gravestone (Spirit Vale) is a nice article, the name is fan-given.

Same thing for Dead bandit, they don't have a name.

I don't think making articles with fan names is a good idea. I put that dialogue there because those objects were nameless, so how else would you look for them.

Take a look at Unknown. Perhaps we could put that dialogue in Spirit Vale#Objects as you suggest, or follow the naming conventions of the aforementioned article: "Unnamed Object (Bandit's Rest Tombstone)" and "Unnamed (Dead bandit)"

Warming Hearth (talk) 10:09, 10 July 2021 (UTC)

"Fan named" articles for unnamed objects are often using either a descriptive name (Tombstone/Gravestone) or a name without full capitalization (Dead bandit), to emphasize the name is not official (since all official stuff has proper capitalization). Sometimes we add an Unofficial term category. Imho, there is nothing wrong with continuing to do that, gazillion pages named Unknown will not help anyone and writing in the intro "Unnamed dead bandits can be found ..." is acknowledging the uncertainty with the name, and is better than "Unknown (#1000) can be found". Also the underscore is in 99% cases indeed "—" as noted by Nightsky, it just appears like that with the font Anet is using. ~Sime 16:23, 10 July 2021 (UTC)

(Edit conflict) You're right. That indeed seems to be a _ and not a —. I didn't know these are fan given names. I agree they should not be named like that, but rather similar to how you suggested. Specificially i'd suggest "Unnamed Object (Bandit's Rest​)" and "Unnamed NPC (Bandit's Rest​)" to be in line with the other articles on Unknown and to also not retain (or introduce a different) fan given name ("Dead bandit" and "Tombstone" in these cases). This would also then be what you'd search for. Or rather, you'd still find them in the Objects section (and probably the NPC section for the bandits then) on the Spirit Vale article as you can now with the fan named articles; which is what i meant, that the two things i mentioned in the edit description can be found there already wihch in turn contain the dialogue (altough incorrectly with —'s instead of _'s for the time being; as you brought to light) which should hence not be duplicated in the dialogue section on the page. Nightsky (talk) 16:31, 10 July 2021 (UTC)

""Fan named" articles for unnamed objects are often using either a descriptive name (Tombstone/Gravestone) or a name without full capitalization (Dead bandit), to emphasize the name is not official (since all official stuff has proper capitalization)." I would have never guessed or thought of that from the naming. Could we maybe make a {{notice}} like template for unoficially named things that explains that the object/item/npc appears as "Unknown" or withouth any name in game and that the name is as such unoficall or something along those lines so that these cases are more obvious? Nightsky (talk) 16:40, 10 July 2021 (UTC)

There is no policy afaik about such objects/stuff, that's why some unnamed things go by Unknown (Name) and some have normal names. The no full capitalization comes from creating headers/pages afaik, when it is a name directly from Anet it has full capitalization, when it is not from Anet it does not (like Astral creatures vs Vampire Beasts). With that, what you are proposing does not sound bad and could go along with the Unofficial category (though I would personally split the category between npcs/names and mechanics). However, it should probably go through the Community portal first. ~Sime 16:44, 10 July 2021 (UTC)

I quite like that notice idea. For the time being, I'll just specify in those articles that the objects are actually unnamed. Warming Hearth (talk) 16:48, 10 July 2021 (UTC)

Yep, for example the Genshin wiki has a notice on some pages saying that as there is no official name for something, they are using a made up/unofficial one. ~Sime 16:52, 10 July 2021 (UTC)

Tilmeline addition reply

"Your additions to Timeline

I'm afraid i have to agree with the IP's removal of the creation of Rata Primus. I'd go even further and remove the facility in Fahranur too. For the Fahranur facility there's an earlier reference on an inquest terminal stating, quoting the dialogue on the aricle, "Your package was unable to be delivered. Last attempted delivery was—seventeen years, eight months, and nine days—ago." indicating there had been an outage or some kind of disruption of the core. There is also nothing preventing the facility to have existed before these dates. They only give the earliest date we can tell that the facility existed but that doesn't mean that it was built exactly then too. And while i didn't easily see any earlier reference for Rata Primus than the 87 days, the same holds true for it. Only because we can tell the earliest it existed seems to have been then, that doesn't prevent it from having existed already before that. Based on this, i'll remove both entries; provided you don't have any good arguments against me doing so. Nightsky (talk) 20:57, 27 June 2021 (UTC) "

Removing it because not knowing the original date isn't a valid argument, you should have asked an admin before taking your ease. Those indications are better than nothing, and even if we don't know if farahnur station existed before, it worth mentionning since when the core and so power of facility have been operated, same logic can be applied to rata primus. I readded farhanur reference. At this point, many timeline events can be questionned becuse just mentionned in a book or events and therefore not sure. Even for primordius as example, you have ton of inconsistencies from anet about where primordius was located and awakeneing.

I readded the ref of farahnur but edited the date to be 17 years before. --88.163.127.2 14:43, 19 July 2021 (UTC)Ezrielia

For the original text with formatting see here. Nightsky (talk) 16:02, 21 July 2021 (UTC)

Perfected Envoy Armor stealth bug

To add on this https://wiki.guildwars2.com/index.php?title=Perfected_Envoy_armor&curid=203613&diff=2301822&oldid=2301810

Although the bug notice was only added recently, the bug has been happening for years, since the introduction of the envoy armor I guess, so I don't think it's related to the legendary armory. Here's an old comment about it https://www.reddit.com/r/Guildwars2/comments/7bzfem/bug_legendary_armor_issue_with_photon_forge/dpm5tyr?utm_source=share&utm_medium=web2x&context=3 though they mention it's only the user that sees the armor visible, but I recall seeing other players with this bug a long time ago. Warming Hearth (talk) 10:11, 7 August 2021 (UTC)

Actually; does you seeing them mean only the armour, the weapons or both? Nightsky (talk) 17:18, 30 August 2021 (UTC)

Here's a raw unedited video of the bug.

It seems to always happen if you gain Hide in Shadows while the armor is transformed or during the transformation animation. Doesn't seem to happen if the armor is untransformed. The weapons and character's skin go invisible, but the armor remains fully visible. NPCs do not "see" you, though. Seems to be just a visual bug. Warming Hearth (talk) 18:04, 30 August 2021 (UTC)

I don't have legendary armor so it doesn't affect me but good to know nevertheless i suppose. Only wanted to know if it also affected weapons back then already too or not. And even if it's just a visual bug; it's still anoying if you're trying to take a screenshot while being invisible, like i was trying to do, only to then not be fully invisible because you're weapon decides not to cooperate. Nightsky (talk) 18:22, 30 August 2021 (UTC)

Lead GM Marauder

He's legit, he just accidentally created his userpage as his employee page. - Felix Omni 16:33, 27 August 2021 (UTC)

Then please ask Stephane if he can get Dornsinger to update the list of employes again to confirm this. If that's indeed the case then i appologize but it's better to err on the side of caution when it comes to employes. Nightsky (talk) 16:37, 27 August 2021 (UTC)

I added the name to the list. (Confirmation by Rubi.) —Kvothe (talk) 17:33, 27 August 2021 (UTC)

And where's that confirmation by Rubi located at? (Also, while i generally appreciate people correcting my typos, please maybe don't "correct" typos et al. in my comments on talk pages.) Nightsky (talk) 17:49, 27 August 2021 (UTC)

Sorry for the confusion all. I had to create an account for myself on the Wiki... I will update the List of Support Team Agents on Monday morning (after my account ages 24 hours). GM Dornsinger is no longer with ArenaNet and I have replaced her, hence the need to edit the Support page. Thanks for looking out and I look forward to getting to know everyone. - Lead Gm Marauder 18:15, 27 August 2021 (UTC)

Rubi confirmed it directly to the admins while asking about how to let Marauder update the Support Team page (which is semi-protected and he isn't autoconfirmed yet). It's all on the up-and-up, I promise - Tanetris (talk) 18:29, 27 August 2021 (UTC)

I see. And i'm sorry that i'm not sorry to have tryed to figure out if your account is legitimate or not; it just wasn't at all clear to me. You're welcome! I try to do what i can.

I see. Would have been great to maybe bring that up somewhere sooner though to avoid it looking like it's drawn out of the blue. Like, it's great that the account's "legit" and all but maybe also include where that's taken from/what it's based on from the get go next time so it doesn't cause uneeded confusion again. On that note; thank you Kvothe for including some kind of reference as to from whom it is confirmed by, even if leaving out by/through which means/where. And to Tanetris for adding the where. Nightsky (talk) 19:17, 27 August 2021 (UTC)

No worries, you acted perfectly reasonably given the information you had at the time, no one's mad at you. Felix and Kvothe and I weren't meaning to sound accusatory. Basically what happened was that Marauder tried to update the Support Team page, couldn't because not autoconfirmed, asked Rubi, who asked the admin team. Felix suggested he make a userpage to get some edits in to be autoconfirmed. He did, but someone else wound up moving it to mainspace (I've since moved it back). The whole thing happened over the course of an hour, else one of us might've thought to stick a note on his talk page or something, but it all resolved in the end. Our apologies for the belated communication. - Tanetris (talk) 21:41, 27 August 2021 (UTC)

re this

Did you see the comment on the api channel of the dev discord that all the Lion's Arch points were noticeably off? -Chieftain Alex 22:31, 12 November 2022 (UTC)

I'm afraid but i can't seem to find any such comment. At least searching for "Lion's Arch" doesn't seem to bring up anything relevant.

Only thing i could find that seems related concerns a POI in Queensdale. Which to me seems likely to be caused by meassurement error.

You may test it's the case using e.g. the following bit of python, which is based on the java code i used to test it with (and is made to work with the example implementation).

Code

# See [[API:1/event details#Coordinate recalculation]].
def scaleCoords(map, con, pos):
    return [
        con[0][0]+((pos[0]-map[0][0])/(map[1][0]-map[0][0])*(con[1][0]-con[0][0])),
        con[0][1]+((map[1][1]-pos[1])/(map[1][1]-map[0][1])*(con[1][1]-con[0][1]))
    ]

def main():
    # As per [https://api.guildwars2.com/v2/continents/1/floors/1/regions/4/maps/50 the API].
    map = [[-27648, -18432], [30720, 18432]]
    con = [[48000, 30720], [50432, 32256]]
    
    ml = MumbleLink()
    
    # Loop until data could be read.
    ml.read()
    while not ml.data.uiTick:
        time.sleep(1)
        ml.read()
    
    while True:
        ml.read()
        
        posAvatar = [ml.data.fAvatarPosition[0], ml.data.fAvatarPosition[2]]
        posPlayer = [ml.context.playerX, ml.context.playerY]
        
        posMtoIn = [posAvatar[0]*5000/127, posAvatar[1]*5000/127]
        posWikiConstant = [posAvatar[0]*39.68, posAvatar[1]*39.68]
        
        print(
            scaleCoords(map, con, posMtoIn),
            posPlayer, # Already in continent coordinates.
            scaleCoords(map, con, posWikiConstant),
            end = "\r"
        )
        
        time.sleep(1)
    
    ml.close()

You're welcome to try the above at e.g. a waypoint of your choosing and compare the results against the also output context player coordinates and the API. Of course if you're trying it outside of LA you'll need to change the map and continent rectangles accordingly.

Also, for what it's worth, when determining the distance between two positions, at least one of which a waypoint, by first determining the distance between the raw avatar positons, then translating the resulting length from mumbles meters to inches using *5000/127 is much closer to the waypoint reported distance than when using *39.68; especially when far away. Nightsky (talk) 00:10, 13 November 2022 (UTC)

left-to-right marks

Any chance you could run a repeat of the left-to-right mark search and destroy operation you did on Guild Wars 2 Wiki:Bots/Resolved tasks/archive 7, also including the file namespace? Had a bunch of pages fail today on my bot run due to these. -Chieftain Alex 16:10, 22 January 2023 (UTC)

Sure. I'll have a look at what i can find. Nightsky (talk) 01:02, 23 January 2023 (UTC)

Locator maps

Thank you for making these, look excellent. -Chieftain Alex 20:58, 30 August 2023 (UTC)

Thank you. :D

The images for the maps are still missing though. (Though not for much longer as i'll be uploading those in a bit.)

And i wanted to have a look at Gyala Delve too. Though the process i've been using would be incompatable with your locators, so i'd have to replace them if i were to do it. Would you wan't to finish the locators/images for that zone, or should i? Medyro (talk) 15:02, 31 August 2023 (UTC)

I hadn't noticed the sectors were missing from Gyala Delve pt2, I can do those easily. -Chieftain Alex 16:28, 31 August 2023 (UTC)

Done. Minor point, when recalculating the widget output for the new sectors, it turned up in a slightly different format (possibly something that's changed since original implementation?) -Chieftain Alex 16:51, 31 August 2023 (UTC)

The format did change, yes. (See here for details.) I haven't updated the widget for that yet as i thought the map widget was meant to replace the locator templates, so there'd have been no point in updating the widget for the locator templates. But i guess there's now? Medyro (talk) 17:44, 31 August 2023 (UTC)

I don't mind. I think the curated svg's are prettier than the auto generated ones, but the way I've implemented the widget (which nobody screamed at me for - yay?) as a stopgap until there were svg files available seemed ok. -Chieftain Alex 17:53, 31 August 2023 (UTC)