User talk:Lon-ami

From Guild Wars 2 Wiki
Jump to: navigation, search


Hold up, we haven't agreed on anything. --JonTheMon 19:42, 2 May 2012 (UTC)

Sorry :S. They're just 3 moves, and they didn't break anything, so it's not problematic. It's easy to reverse if you don't agree with it (I'll reverse them myself if necessary).--Lon-ami 19:46, 2 May 2012 (UTC)
I was talking about the other templates as well. --JonTheMon 19:49, 2 May 2012 (UTC)


Welcome to the wiki btw. More eager, constructive users is always a good thing :). pling User Pling sig.png 19:54, 2 May 2012 (UTC)

Don't refrain of reprimanding me if I break your rules without discussing them first, I still need to see how you work here :P. GW2 deserves a great wiki, and I'll help in everything I can so it's the best out there ;).--Lon-ami 20:01, 2 May 2012 (UTC)
If you're acting in good faith, and you don't accidentally blow a hole in the wiki, no reprimands needed. Discussion usually sorts things out, so that's the best way of going forward if you're unsure about something. pling User Pling sig.png 20:28, 2 May 2012 (UTC)
Howdy. Sorry if I sounded a bit harsh above. Mostly, I get that way when someone seems to jump the gun on something. But, welcome and enjoy your stay. --JonTheMon 20:31, 2 May 2012 (UTC)
My fault for getting too anxious at doing things. For some reason I misread and thought it was okay when no one had still answered, lol :P.--Lon-ami 20:42, 2 May 2012 (UTC)

I'm just curious[edit]

Is there a particular reason why you do not discuss massive changes to already created templates? I see you mention it occasionally on talk pages, but never seem to wait for follow up or a discussion to even develop. Also, I was wondering where the discussion was to move profession templates from short characters to full names? (ie En to Engineer, W to Warrior, etc). And lastly, I would like to draw your attention to RfC. Please use it. I'm not saying that any changes you make are bad or not necessary, but many of these templates have been in use for a lengthy time, and are widely implemented. At least give discussions a chance to flourish before trying to adopt new formats/utilizations. Thank you. Venom20 User Venom20-icon-0602-sm-black.png 15:36, 6 July 2012 (UTC)

Well, most tango icon templates are named with the complete name, and it's more intuitive like that. Still, I left the redirect for shortcuts. I don't think it needed a discussion, it's not a "huge" change, as per se. If there's 13 templates following a naming pattern, and 8 following another, making those 8 look like those 13 is logic, isn't it? And don't worry, I only optimized and made them follow a pattern, they work exactly like they did before the changes ;).
Thanks for the link, by the way. I didn't find that, glad to see the wiki has one.--Lon-ami 16:14, 6 July 2012 (UTC)
Perhaps I'm missing something. Are you comparing profession templates to race templates in regards to naming convention? Or are you grouping all icon templates into this same convention topic? What I am sying is that you are moving an rearranging templates that have been in effect for nearly 2 years prior to even having a discussion on matters. I understand that you feel that it is more intuitive and thatyou don't think things need discussions, but unfortunately the wiki is a we project. In other words, this wiki is the Guild Wars 2 Wiki and not the Lon-ami Wiki. I understand that you have ideas that you feel can benefit setups, but all I am asking is that you discuss them. Currently you are undertaking a solo project to alter the value templates and have reverted changes because you plan to improve them in the future. Generally things that effect templates on such a massive scale should be mocked up in your userspace to demonstrate their improvements and effectivenesses so that it can be discussed prior to becoming wiki-altering. I know it has been said, and I apologize if this sounds curt, but there is no fire. Take the time to involve the community in things. Venom20 User Venom20-icon-0602-sm-black.png 16:50, 6 July 2012 (UTC)
If I see an article full of bad grammar that hasn't been fixed since ages ago, I'll fix it, no matter it's been like that since ever. You can move them back, I repeat the redirects are still working as intended, and if you revert the move, both versions will keep working (and I won't revert it in some kind of dumb edit war, don't worry). I think you're making a big deal out of it, everything is working exactly as before. Nothing has changed. Whatever you type in the template, the result will be the same as 2 years ago. Anyway, I'll open a new discussion for this here: Template talk:Tango icon sizes since it covers all of those templates.
As for the other case, it didn't change anything, so I don't see your point. It just added extra options that hurt no one and don't interfere with the basic usage of the template. Is that bad? Do I need to use {{Value}} if I just want to output "10 gold"?--Lon-ami 17:15, 6 July 2012 (UTC)
"If I see an article full of bad grammar that hasn't been fixed since ages ago, I'll fix it, no matter it's been like that since ever." That has no relation to the issue that Venom brought up - correcting obvious errors in mainspace articles is something we expect people to do, and it generally doesn't cause any controversy. Making sweeping changes to a bunch of templates that were working perfectly is entirely different. —Dr Ishmael User Dr ishmael Diablo the chicken.png 17:55, 6 July 2012 (UTC)
Don't they work perfectly now? I would say they work even better than before (simplified shared code). I don't think that's the point, naming conventions is, and we already have a place for that anyway: Template talk:Tango icon sizes (continue there, no point to be discussing the same thing in two different places).--Lon-ami 18:18, 6 July 2012 (UTC)
That discussion is about what we should change, not how we change it. The point we're bringing up is that "if it's not broke, you should get consensus to 'fix' it". --JonTheMon 18:25, 6 July 2012 (UTC)

order vs personal story category[edit]

It made more sense to me as Order weapon sets, because that describes what they are, not how you get them. Why did you change it? —Dr Ishmael User Dr ishmael Diablo the chicken.png 16:45, 9 September 2013 (UTC)

Pact weapons aren't order weapons. Also, using "Personal Story weapons" leaves things open for when we get new weapon sets through the personal story in a future.--Lon-ami (talk) 16:48, 9 September 2013 (UTC)

PvP Adorned weapon[edit]

Why'd you change PvP Adorned weapons to PvP Adorned weapon? The page refers to all of the weapons, so it makes more sense for it to be plural, imo. -Somohexual (talk) 23:08, 15 September 2013 (UTC)

You did the redirect wrong. I fixed it and left it in singular because all pages are like that: PvP reward, but I agree it's better as plural. Move the others if you want, too :).--Lon-ami (talk) 23:59, 15 September 2013 (UTC)
The pages were created before it was decided to use plural.--Relyk ~ talk < 00:09, 16 September 2013 (UTC)

Zone#Zones by level table[edit]

Hello, I saw that you changed the table - looked good.

I hope you don't mind, but I changed the format a bit further:

  • to look like other tables on the wiki I've changed it to using {{STDT}}. (purple background for location tables)
  • put the template in the Template namespace. (derp?)
  • changed it from a nested table to using inline divs.

I was trying to get it to look up the explorable and region names + levels automatically, but my wiki-fu wasn't strong enough/it didn't work. -Chieftain AlexUser Chieftain Alex sig.png 15:33, 16 November 2013 (UTC)

No problem, it had no format and fits better now. And yeah, my mistake making it subpages instead of a template when I started copying it from my personal space (Original here), but I kept with it anyway, planning to move it later. I'm sure there must be a way to make it work with just the name, no levels and no regions. I'll look at it later, too. Would be good if eventually the table was generated entirely by itself, with no inputs.--Lon-ami (talk) 15:43, 16 November 2013 (UTC)
if I can get relyk on the case it'll eventually work with no inputs :P -Chieftain AlexUser Chieftain Alex sig.png 16:04, 16 November 2013 (UTC)

You can save some time[edit]

Before you add the category to all pages of loot that isn't part of a set (which would take a very long time, I think) I believe a better idea is to set up the template so that if a "set" isn't defined, it defaults to the "none" set, and then you could set up a SMW query for all weapons that have set "none". If that's something you would be keen on doing, I can see about getting the ball rolling on that. Psycho Robot (talk) 18:38, 22 November 2013 (UTC)

Well, that could work, too, and way better. The only problem I see there is that the "set" field is pretty unused across weapons that are part of a set. Also, whenever someone adds a new weapon it would get included in the list by default even if it shouldn't go there. I'll keep with the manual labor for now, but I still think it would be a better idea to do it automatically, though it needs some thinking and preparations to avoid those problems.--Lon-ami (talk) 18:42, 22 November 2013 (UTC)
Adding stuff to the set field is maintenance type stuff that has to get done anyways, I can start working on that later. You have a good point about default stuff though. Instead it could default to having no weapon set property at all, then you could add it to this standalone category later by specifying the set "none" or "standalone", whatever floats your boat. And now that I think about it you could get around the whole "skin vs weapon" argument because we could add "skin set" as a parameter to the weapon infobox and have it behave exactly the same way, then set up a SMW query for weapon sets AND weapon skin sets. Psycho Robot (talk) 18:46, 22 November 2013 (UTC)
There's the problem of standalone and "named" weapons getting mixed, too. Standalone have unique skins, "named" are just weapons with repeated skins. The separate list for those isn't ready yet, but I would like to differentiate them clearly in the future. It would be nice if, eventually, all the categorizations I'm doing happened automatically through attributes, yeah.
I don't understand your idea to fix the weapon/weapon-skin debate entirely, mind elaborating? Do you mean adding both a "set" and "is_skin" fields to the template? My main problem with the debate is weapons and weapon skins not sharing their categories when divided by subgroups (If I want to see loot weapons, I want to see both loot weapons and loot weapon skins in the same place).--Lon-ami (talk) 18:54, 22 November 2013 (UTC)
@Psycho: No, don't try to do weapon skins in the weapon infobox. It's separate from the item infobox specifically so that it can set and display the item's stats - if you put skins in there, you'll have to conditionally disable all the stat code, in which case it'll look just like the item infobox. So it's pointless. —Dr Ishmael User Dr ishmael Diablo the chicken.png 19:25, 22 November 2013 (UTC)
Right, I didn't mean to say that, I meant to say adding skin set parameter to the item infobox. As far as fixing the debate, if you had a parameter for weapon sets, which included "standalone" and "named" (though I'm not sure I understand the distinction), and you had a weapon skin set parameter, which included "standalone", you could set up a page that listed standalone weapon sets and skins without having to identify one as the other, since as far as I know, SMW can add two different queries to the same list. Or it could be split by a level 2 header. Psycho Robot (talk) 19:39, 22 November 2013 (UTC)
What is the point of a "standalone" category anyway? Isn't that just "everything that isn't named or part of a set"? If that's the case, then you're not using categories right. You're trying to do this:
User Dr ishmael bad weapon categories.png
But you should be doing this:
User Dr ishmael good weapon categories.png
Does that make sense? —Dr Ishmael User Dr ishmael Diablo the chicken.png 19:53, 22 November 2013 (UTC)
The only reason I would have a property for standalone weapons is because you can't SMW query for when a property isn't defined. It wouldn't have to be a category at all, just an invisible maintenance type thing. Psycho Robot (talk) 20:05, 22 November 2013 (UTC)
@Psycho: Set: Collections. Standalone: No-collections. "Named": Repeated skins from sets or standalone. "Named" needs a better name, though. The main goal of this way og organizing it is making it easier to browse models/skins.
@Ishmael: That works fine for the main category, but once you want to classify everything I think they're better as the above example, separated for clarity.--Lon-ami (talk) 20:11, 22 November 2013 (UTC)
Spark (weapon) and Usoku's Needle: which is named, which is standalone, and why? Psycho Robot (talk) 20:15, 22 November 2013 (UTC)
My point is that you don't need to classify everything. Some things are just basic things with no special classifications, so you shouldn't make up a classification for them. —Dr Ishmael User Dr ishmael Diablo the chicken.png 20:22, 22 November 2013 (UTC)
In those cases we either take both (like Ilya and Lyss, or the ascended weapon sets) or the one that seems more relevant. Many of the precursor weapons are copies of set weapons, so we can extrapolate that all precursor weapons are "named" (even though they have 2 uniques between them). More examples: Karma vendor and Personal Story reward equipment are very inconsistent, therefore it goes behind other sources like loot and tokens. Also, I consider weapon sets need to match 2/3 of these conditions: Appearance (They look similar), Naming (Common name pattern) and Source (Same vendor and currency, or same consistent recipe). They need to have at least 6~ elements on the set, too.--Lon-ami (talk) 20:28, 22 November 2013 (UTC)
The purposes of setting the set parameter to standalone is not to "classify" these weapons, but rather to just be able to query for them with SMW. If its better, the parameter could be set to "undefined" to make it clear that its not actually classifying anything, and that is just a workaround for a technical issue. BUT should what Lonami said be true, then I think its a moot point, because if the only difference between a named weapon and a standalone weapon is that we call the one that seems more important a "named" weapon, then I would say that there's NO difference, and that we could just put all named weapons in the "named" set and then we'd be done with it. Psycho Robot (talk) 20:41, 22 November 2013 (UTC)
Please give a use case for when you would need a query to return only "standalone" weapons before you go doing this. If there's no use for the feature, it shouldn't be implemented. —Dr Ishmael User Dr ishmael Diablo the chicken.png 21:22, 22 November 2013 (UTC)
You don't understand "the problem". The weapons here: Category:Named weapons aren't inside any set, but they use skins from the sets. Including them together with those who have unique skins (the standalones) would make it a mess. When you search for weapons and across galleries, you don't want duplicates. Named is where we put the duplicates so weapon sets and standalones fulfill the 1 weapon = 1 model/skin rule.
Whatever happens and is decided with the entire system, I still think we need to separate those which have unique skins for gallery and navigation purposes.--Lon-ami (talk) 21:30, 22 November 2013 (UTC)
Anet's practice of reusing skins like a bandit makes this pointless, I think. I don't think having duplicate skins in a list of named weapons is a bad thing because it allows people browsing named skins to quickly see which alternatives are avaliable for a certain skin. If I fell in love with the skin for Spark, I'd be relieved to find that a duplicate is Usoku's Needle. If it would be better for you, we could try to group identical skins together by assigning a duplicate skin a parent "lookalike" in some invisible way, that would group them together in the gallery output. Psycho Robot (talk) 21:54, 22 November 2013 (UTC)
Isn't it easier to just choose one as the "original", and then link the "copies" inside it?--Lon-ami (talk) 22:35, 22 November 2013 (UTC)
I think that seems 100% arbitrary and subjective. If we really NEED to do something like this, just make a project to find every duplicate skin in the game. Then on every item with a shared skin, make a note of what items share that appearance. Otherwise, I'm still not understanding what the "problem" is here. It feels like creating an elaborate solution with no associated problem. Remember, from the perspective of a user browsing for a skin, it doesn't matter what the "original" item is - they'll go after whichever variant is easiest for them to obtain.
As Psycho Robot says, it's sort of a pointless pursuit to categorize things according to duplication, because Anet keeps reusing almost every skin over and over. I propose it's more useful to identify which items have unique appearances not found on anything else, and just assume every other item has a duplicate somewhere. (Caveat: it might be worth distinguishing between PvP and PvE gear, since some things available easily in the PvP Locker are hard to get in PvE and vice versa. The Hunter comes to mind - the PvP equivalent is Plated Rifle, and is fairly easy to get.) Vili 点 User talk:Vili 23:39, 22 November 2013 (UTC)
Gave one possible solution here--Relyk ~ talk < 23:44, 22 November 2013 (UTC)
Well, Relyk, that's exactly what I want, in one way or another. However you'd still have the naming problem: We need to decide which name is the original for each one.
Anyone of you remembers the now-defunct argos-soft gallery? I believe the wiki should be able to offer something similar, between other things because it can be updated by anyone, unlike the web galleries that get eventually outdated.
It would be great if we managed to update the weapon galleries, for example, to be sortable by source/adquisition, as well as display all weapons with the image's model, pretty much like argos-soft did. And for that, we need to have everything organized properly, if not by categories, by template properties (or both, ideally).--Lon-ami (talk) 12:59, 23 November 2013 (UTC)
The name of the file doesn't matter, we'd query for an id or some other unique identifier. If the weapons with the same model use the same icon, we can use the item icon id, although this doesn't guarantee uniqueness if it's not true. We would either categorize it or have a property to identify the game context and/or item type. The weapon model gallery would query image pages for these properties instead of item pages.--Relyk ~ talk < 21:16, 23 November 2013 (UTC)

Halloween Skins[edit]

I don't think its a good idea to combine all the years of halloween skins into one template, or even one page. Sure, it looks fine now, but there will be more skins next year, and the year after that, and the year after that. Its only going to get bigger and more cluttered. I mean, I know halloween 2013 was just a recycled halloween 2012 with half the good stuff disabled, but you know I still think the two should have separate pages. Psycho Robot (talk) 17:28, 30 November 2013 (UTC)

I think it's fine for the page, we have longer galleries anyway. The template... Okay, you might have a point, so feel free to separate it into two different templates, like [[Template:Shadow of the Mad King skins]] and [[Template:Blood and Madness skins]]. The weapon categories are fine, and they're already used elsewhere, so please keep them as they are. The armor pieces, however, don't have any, and I think mixing armor+weapons in the same category wouldn't be very good. Also, do you plan on including other skins like Mask of the Night Skin which aren't tradeable?
By the way, another option could be moving content inside Halloween skins to each release's page, but I prefer having them in one single page like it is now. If someone complains they aren't a set and thus not deserve their own page, well, we'll have to move them somewhere else.--Lon-ami (talk) 18:50, 30 November 2013 (UTC)
I grouped those skins together because they were all obtained via the standard RNG chest method which has disappointingly become the norm. The mask of the night skin and the other miscellaneous things wouldn't count. I still don't think it is a good idea to combine them on one page. The current status quo is to have separate pages for separate weapon (skin) sets. It seem as though the only reason you have for combining them is because there are longer galleries, but there doesn't really need to be a minimum length for galleries. Also I'm not sure what weapon categories you're referring to. Psycho Robot (talk) 20:46, 30 November 2013 (UTC)
Yeah, but these aren't a "set". That's the problem. Halloween skins from both releases are in the same group as these weapon "series": Hall of Monuments#Weapon skins and Phantasm#Related weapons that weren't allowed to have pages of their own because they weren't sets.
I tried to change the article to a generic "skins related to Halloween" theme. If you focus on just the 2012 skins you'll face the same problems. Putting all Halloween skins together could make the reason for the page to exist stronger, instead of it being forced to go on an already existing page. If it was only the 2012 skins, it would probably get moved to the Shadow of the Mad King page.
As for the categories I'm referring to: Category:Shadow of the Mad King weapon skins and Category:Blood and Madness weapon skins.--Lon-ami (talk) 22:13, 30 November 2013 (UTC)
Yeah calling it "halloween 2012" instead of Shadow of the Mad King was a mistake. I'm not sure why I felt like it had to be Halloween 2012 instead of that. In any case, I think that halloween skins are fundamentally different from those other thematically linked weapons you mentioned, namely that they are analogous to every other type of living story weapon skin set, which are incontrovertibly skin sets, such as Winter, Dragons Jade, Fused, etc. The only reason you could argue that they weren't a skin set is because they didn't have a prefix name, but that's a minor point that nobody has really taken issue with. If a halloween skin article in the form of the standard skin set article is fine, then logically articles split by year should be fine too, and since that's the standard, I think that's what should be done here. Psycho Robot (talk) 03:55, 1 December 2013 (UTC)
Yeah, that Halloween 2012 and Wintersday 2012 theme around the wiki was pretty confusing, but I merged/fixed most of it recently after noticing it, also because latest releases with events had everything in a single plage. I guess it's a GW1 tradition, but here events are always linked with their own themed releases so we don't need duplicate pages.
Personally I don't consider them a set, there's not enough of them and they don't look similar. The prefix is important but not vital: Aetherized Nightmare weapons. That's why they are here: List of standalone weapons instead of here: List of weapon sets. Do they deserve their own page? Well, they could go inside their release page, Shadow of the Mad King, or as they are now, merged so anyone can see all Halloween-themed skins in a single place. Don't get me wrong, I'd probably be happier if all standalone series had their own page, but there's many voices around here that don't like non-sets having their own pages. Try giving them each their own page if you want, just respect existing categories, and be ready for complaints.--Lon-ami (talk) 12:22, 1 December 2013 (UTC)

Personal story[edit]

pretty sure the discussion at Talk:Personal_story#Move_to_.22Personal_Story.22 lead to the decision that "Personal story" would be used in any titles or category names. This is just a heads up so you don't go changing too many category names to something that is also wrong ("storyline" was wrong, "Story" is wrong, "story" is what we're going to use.) -Chieftain AlexUser Chieftain Alex sig.png 18:55, 7 April 2014 (UTC)

Ah yeah, it's "story" not "Story". I'm not going to change anything else, so no worries.--Lon-ami (talk) 18:57, 7 April 2014 (UTC)

Armor sets[edit]

Well, my summary could have been clearer, but in addition to me not wanting to constantly fix things twice, there's an ongoing discussion about armor formatting where I specifically suggest removing the "quick" list and what little discussion there is does not contest the removal of that second list, on the guise of it being completely redundant. Psycho Robot (talk) 19:58, 29 April 2014 (UTC)

It's not redundant when some armors have multiple obtainment sources, or when you want a complete and clean list. Also, instead of navigating across the entire page looking for redundancies, you have all of them in a list.--Lon-ami (talk) 20:04, 29 April 2014 (UTC)
I see your point, but I don't think the issue the list solves is important enough to justify putting at the top of the article a big huge list that just repeats the following content in an less formatted manner. Would you be amicable to putting it on a subpage or a different page? I was proposing that the current article be moved to Armor set, and the list which I removed could be put back in on List of armor sets, since that title seems appropriate for a big list like that. The only issue is that in its current iteration it assumes that there is one weight for every line, but that's not true. The current list omits the heavy plate karma armor set because it doesn't have a light and medium counterpart. Psycho Robot (talk) 20:27, 29 April 2014 (UTC)
I think the best idea would be to just add a "show/hide" button, keeping it hidden by default and not wasting the space (It's fine now, but later on it would be huge). But it should remain in the same page, it's there to see a complete list and multiple sources easily.--Lon-ami (talk) 20:40, 29 April 2014 (UTC)


Never got around to a reply on Template talk:SAB NPC infobox--Relyk ~ talk < 17:27, 22 January 2015 (UTC)

Honor of the Waves[edit]

Hi, I have a question about this edit of yours, where you added "Chamber of Harmony" to the locations list in Honor of the Waves. Do you have evidence this area exists? Neither I nor a friend who has completed all paths in this dungeon can find it. --Idris (talk) 17:54, 3 May 2015 (UTC)

It's at the lowest lever, southwestern corner. You can get there from story mode, from the last room, using the tunnel to the south :).--Lon-ami (talk) 19:19, 7 May 2015 (UTC)
Thank you! I'll check that out next time I can be bothered to do story mode. :) --Idris (talk) 19:23, 7 May 2015 (UTC)

small edits[edit]

You can put the template in a sandbox so you don't have 20 sequential minor edits to template :< Makes it way easier to read what you're doing--Relyk ~ talk < 20:36, 16 August 2015 (UTC)

I didn't think I would make so many edits, sorry >_>. Noticed more and more uncovered options while I fixed previous ones. The template's code itself is kind of messy, it could use some cleaning anyway, maybe some day!--Lon-ami (talk) 21:36, 16 August 2015 (UTC)
"code itself is kind of messy", I clean up that code constantly though :(--Relyk ~ talk < 21:40, 16 August 2015 (UTC)
Wikis aren't really visual for straight code. Need some tabulation love :D.--Lon-ami (talk) 09:13, 17 August 2015 (UTC)
2 space indent all day every day. every time there is a tab in the syntax, a baby dragon dies.--Relyk ~ talk < 10:12, 17 August 2015 (UTC)
Tabs are the spawn of Satan. I eradicate them anytime I see them. —Dr Ishmael User Dr ishmael Diablo the chicken.png 12:26, 17 August 2015 (UTC)
I know tabs and wikicode don't like each other, I'm just sad it's like that :I.--Lon-ami (talk) 16:53, 17 August 2015 (UTC)


To my knowledge, "predefinite" is neither an English word nor an official in-game term. (You might be thinking of "predefined" or "predetermined".) Regardless of the word you use, you might consider including an explanation on the page of how you're using it. --Felbryn (talk) 22:15, 2 August 2016 (UTC)

I done fixed it. - Felix Omni 22:47, 2 August 2016 (UTC)
Definite is a thing, so I thought pre-definite would be as well, meaning "concise between limits", or "clearly defined". Defined/Determined were too generic for me, but if predefinite sounds so bad then predefined should do it.--Lon-ami (talk) 00:18, 3 August 2016 (UTC)
The prefix pre- usually means "before". Upon seeing the word "predefinite", my (native speaker) intuition is to parse it as "not yet definite" (similar to "premature", "premarital", or "pre-game"). Which I think is the opposite of what you meant, and for some reason is completely different from the meaning of predefined/predetermined, where pre- means "already" instead of "not yet" (possibly because "defined" and "determined" are verbs?)
The word "definite" already means "clearly stated or decided", so that might be closer to what you meant. But it's usually contrasted with vagueness or uncertainty (where you don't know something), not freedom or flux (where the thing can change), so I don't think it's a good term for "not selectable". "Predetermined" (set in advance) seems like the correct word to me (except that it would naturally apply to the stats themselves, not to the item that has the stats).
On a side note, I can't figure out what the phrase "concise between limits" would mean (in context or otherwise)... --Felbryn (talk) 05:51, 3 August 2016 (UTC)

attribute icon[edit]

Never got around to fixing it when I first implemented. {{attribute}} needs to be pushed to {{item stat}}, {{attribute}} remove the modifier prefix, and attribute icon to use {{effect icon}}. All the notext template calls need to be switched to {{attribute icon|<attribute>|15px}}.--Relyk ~ talk < 00:49, 16 August 2016 (UTC)

Actually, that's still wrong. Split it up because only certain attributes are part of items. Would probably do item stat icon.--Relyk ~ talk < 00:53, 16 August 2016 (UTC)
I only want this template for shortcuts in prefix tables, and so far it's working as intended (with the correct icon size too). Maybe it wasn't the best name, but it's unused so far. The likes of {{Power}} and {{Vitality}} already link to {{Effect}}. I'd say fix {{Currency}} and {{Token}} first.--Lon-ami (talk) 09:12, 16 August 2016 (UTC)
Uh, you could already use {{effect}} and {{effect icon}} to get the same results. I don't like duplicating code in our templates.--Relyk ~ talk < 02:32, 17 August 2016 (UTC)
The purpose is not the same in any way, and the code is different as well. Also, the template can grow to adapt to the table rows better later on, in which case effect (why are we even using something called effects for attributes to begin with?) wouldn't be able to be updated to reflect that in any way that doesn't involve a huge mess, since that one is also used in between text and outside tables. It's working as intended and it's not breaking anything, I don't see where the problem is. At least let me finish the overhauls in peace, and we'll talk about the template once everything is finished. Right now what you see is far from final, and comparisons aren't pretty much pointless.--Lon-ami (talk) 21:36, 17 August 2016 (UTC)
You're making icons and links. The wiki has a constant issue of writing the same code for icons and links constantly. Which means someone gets to clean it up later. I've done a ton of work to clean up icons so we can start using them in tables like this. I am bringing this up because you're overhauling the page and I want to discuss the changes you're making. That's how wikis work. You are using a large mainspace article as a sandbox for this rather than your userspace, so you can understand why I'm not leaving you in peace.--Relyk ~ talk < 22:38, 17 August 2016 (UTC)

Ember Bay region[edit]

Ember Bay isn't part of Heart of Maguuma gameplay wise, Ring of Fire is a proper mechanical region. Southsun Cove's API response does indeed put it in Kryta, but Ember Bay's response puts it into Ring of Fire. User Noxx Sig.png 11:00, 22 September 2016 (UTC)

Yeah, I already noticed myself. Seems the Heart of Maguuma region achievements affect the Ring of Fire region as well. Bug or outdated descriptions.--Lon-ami (talk) 11:13, 22 September 2016 (UTC)
So... I just happened to look on the API for Sparkfly Fen and Metrica Province, and they say the regions are Steamspur Mountains and Tarnished Coast... Remind me, why exactly do we have a "mechanical region" category when it isn't actually properly reflected by the game in the first place? Sure, some regions are clumped together for dailies (Tarnished Coast with Steamspur Mountains, Ring of Fire with Heart of Maguuma), but saying they belong to a region from the other side of the continent is rather silly, when even the API shows that the game code doesn't consider them like that...
Anyway, just a thought, what would you say about turning "mechanical regions" to "daily regions" and using both the daily and regular ones in infoboxes? See Talk:Ember Bay#Mechanical region, if you want. User Noxx Sig.png 01:31, 23 September 2016 (UTC)
Didn't know Steamspur Mountains were included in the API as well, now that doesn't make any sense at all. It puts Southsun Cove in an even weirder position now too.
The 4 established starting regions have some specific attributes. For example, tier 1 and 2 cultural weapons drop by region. Each of these 4 regions have an unique loot-only exotic weapon set as well.
I checked Timberline Falls, and it's included inside Shiverpeak Mountains instead of Steamspur Mountains, so it seems only the Maguuma Jungle zones are affected by this. Seems Bloodtide Coast and Claw Island could be included under Steamspur Mountains as well, but aren't. Crucible of Eternity is included under Steamspur Mountains too.
I say leaving it like it is, after all, only the ingame map refers to these zones by this way. But it is indeed weird.--Lon-ami (talk) 13:55, 23 September 2016 (UTC)
I wouldn't mind leaving it like this if it weren't for the Heart of Maguuma gathering dailies working in Ember Bay. The current way of documenting that would indeed be to place it into Heart of Maguuma, but that hardly seems like the sensible choice. And I don't particularly like the idea of treating each pair of daily-sharing regions differently. It's not that big a deal right now, but with each new map in LW3 it could become worse and get out of hand quite quickly. It's more of "let's think about it" for now, rather than "let's change it today", but still... User Noxx Sig.png 15:03, 23 September 2016 (UTC)
Depends on how many new regions we see in a close future. We could be getting one zone in one new region with every release, which would make noting down each zone a mess of different colors. I would stick with what we have now, and let Ring of Fire be a thing because of the different character background.--Lon-ami (talk) 16:47, 23 September 2016 (UTC)