Guild Wars 2 Wiki:Community portal

From Guild Wars 2 Wiki
Jump to: navigation, search

Community Portal

Lost in a sea of projects, formats, and debates? Look no further! These are the current hot topics, and you can find previous topics here.

To begin a new topic on this page, use the "+" button at the top of the page.

If logged in, you can also add this page to your watchlist to track any changes and stay on top of things!

Old topics are archived to these subpages.

Newsletter of the week[edit]

This newsletter is maintained on User:Relyk/Wiki Newsletter and might not objectively reflect what happened on the wiki.

General formatting guides[edit]

With a new expansion on the horizon, we're facing a huge amount of new content that will require new articles to be created, and likely an influx of new users to help out. I think now would be the perfect time to review the Guild Wars 2 Wiki:General formatting guides, as many of them are out-of-date and some (traits, effects, etc) are missing. I've already made a start on updating them, but I thought I'd leave a heads-up here if anyone wants to help me. --Idris (talk) 14:51, 2 August 2017 (UTC)

Thanks for looking into these. As a general statement, there's a difference between scaffolding (giving editors a framework to build off of) and dictating (saying, "This is how we do things around here!"). I hope the messaging from the guides is more on the former than the latter.
Also, as Vent and others are aware, I'm terrible at such conforming, so as much as I wish I could, I don't think this is where I can help too much. I am sure that others will come along and lend a hand, though. G R E E N E R 16:12, 2 August 2017 (UTC)
Ditto, every time I edit an npc article it needs bleaching. -Chieftain AlexUser Chieftain Alex sig.png 17:29, 2 August 2017 (UTC)
I wouldn't mind helping make an Effect formatting page. Anet releases like 20 new effects every living story update, and while they're all very uniform at the moment, I think that's because it's the same few people working on them, not because it's easy to find the formatting. (When I started, I spent like 2 hours figuring out how the effect infoboxes worked, etc.) And I think consistency in linking effects for Achievements and Skills is important.--Rain Spell (talk) 21:19, 2 August 2017 (UTC)
I've expanded the list of guides on the general formatting page; some of them are red links (including effects), so go nuts. :) --Idris (talk) 18:30, 3 August 2017 (UTC)
I love the table! Not sure about two things though: Raids are formatted the same as dungeons, so I'd probably remove that link and tweak above text accordingly. Also I think Mastery Insights could easily go on the Object page, but I don't mind either way there. - Doodleplex 18:36, 3 August 2017 (UTC)
Ah, wasn't sure about raids. Will fix. I was tempted to include mastery insights on the objects page too, but then I noticed that hero challenges have their own page, and realised that it's not immediately obvious that hero challenges and insights are "objects", so I think it's helpful to list them separately. Do you think they should share an article though? --Idris (talk) 18:40, 3 August 2017 (UTC)
Hero challenges come in many different types so that's why they have their own pages, but since Mastery Insights are virtually the same as communing hero challenges that could fit nicely there. Perhaps a slight tweak of adding "getting there" since some mastery insights are like mini jumping puzzles should be added if that happens, which if nobody has any other objections or inputs, I'd say go ahead and do. - Doodleplex 18:48, 3 August 2017 (UTC)
Done. --Idris (talk) 19:20, 3 August 2017 (UTC)
Oh, and Greener: since diplomacy is your strong suit, I think you'd actually be a great asset to this project, as you can help ensure the wording is appropriate. I'm sure I've already messed up and come across as dictatorial in a few places already. --Idris (talk) 18:46, 3 August 2017 (UTC)
Sure, so a few things I'd like to point out, and encourage feedback on.
  • First, we want to make sure our messaging is on point. Every well-intentioned edit is appreciated, and no one should feel like they cannot contribute because they can't live up to our standards. If we present ourselves as having formats and rules, we'll ostracize parts of our community.
  • Second, I hope we're not setting ourselves up for what I consider to be bad habits. I don't want to see wiki editors going around and changing the order of sections because "that's how we do things". For example, if the "Content" header is above the "Acquisition" header, does it really matter? We should be making sure the information order on that page is conducive to the reader, rather than conforming to a predetermined format.
To these ends, I'll offer a few suggestions, all of which likely need massaging from you folks. Rather than naming the pages "Event formatting", which by its nature creates and reinforces a constrained view of what's allowable, let's allow ourselves to be more open. May I suggest naming the pages, "Guide to event pages", etc.? I'm also curious on if we can reduce the splash of information that players get when looking at pages such as Guild Wars 2 Wiki:Event formatting. It's a tad overwhelming, and I wonder what it would be like if we put the copy/paste version first.
I love how we're giving contributors, new and old, helpful tools. Let's make sure we're not sending them handcuffs at the same time ; ). G R E E N E R 23:13, 3 August 2017 (UTC)
Thanks for the suggestions. I'm not opposed to renaming the formatting articles, but I'm not keen on doing it myself because I don't have a bot that can deal with all the broken links left in its wake. (I dislike linking to redirects.) As for the splash of information coming before the template -- personally, I prefer showing guide information first; the templates tend to be quite large, so I worry that users seeking the information will miss it if it's hidden at the bottom. Rewording the first sentence to something like "skip straight to the template if you want" and forcing the ToC to display so they can get to it quickly might be a better solution. --Idris (talk) 12:41, 4 August 2017 (UTC)
Any chance of getting a PvP loot box guide/framework? I usually clean up as I might otherwise edit, but I'm sure that there are things that I keep as they are due to others in the same Reward track. (i.e. the acquisition section: Tier 1, 1st reward. (1st of total.) vs without (). Also order of drops, and to sub-section or not sub-section.) Adeira Tasharo (talk) 00:05, 21 August 2017 (UTC)

Wiki header file / theme for Path of Fire[edit]

Hi guys. We need some artists, so get your painting hats on and easels out. If you've got arty gw2 friends, rope them in. We could do with the following:

Skin header (i.e. the colour bit in the top left behind the logo + tabs)
Main Page/editcopy
  • It'd be nice to have some new matching files left and right. The current files are here and here.
  • New release content suggestions.
  • {{Main Page/featured}} - this could be prepared for the release.

Stephane has provided a few textures to get us started:Talk:Main Page#New background needed?. -Chieftain AlexUser Chieftain Alex sig.png 21:03, 8 August 2017 (UTC)

New launcher! We could steal the art from it to make our background, perhaps? --Idris (talk) 21:17, 8 August 2017 (UTC)
File:PoF_Launcher_art_clean.png <-- Uploaded it for easier use. --Idris (talk) 21:33, 8 August 2017 (UTC)
I've applied your changes to the Main Page, it looks great. I'm not going to win any friends with my edits over the last 10 minutes, but I have also applied a header file I did that was a slightly better colour match than the previous one. When there's some agreement I'll change it over again. Also, sorry for protecting the images which will seem like I'm preventing their being edited - which is true in a way, I just don't want spambots replacing them :< -Chieftain AlexUser Chieftain Alex sig.png 21:16, 11 August 2017 (UTC)
The banner you chose is a good placeholder! I like the way the orange shines in from the right like the sun. If we applied that colour to Inc's #2, I daresay we're onto a winner. --Idris (talk) 00:59, 12 August 2017 (UTC)

A few more pictures[edit]

I've added a few more pictures that could be useful to the GW2 wikis, including additional concept arts:

Let me know if the wiki has other, specific needs! Thanks everyone for your awesome work :) --Stephane Lo Presti talk 23:21, 10 August 2017 (UTC)

list of unmatched searches (chatcodes)[edit]

is there a way to display all recent chatcode searches which did not match a page? this would make adding items a lot easier when pof hits, as those who edit the wiki wouldn't have to get the item themselves. I've added a few of the Sunspear weapons during the beta weekend and the only way I could do that was to farm unidentified gear and get them myself. being able to see all searched chatlinks would really speed up the process and convincing players, who are not prepared to edit the wiki themselves, to at least /wiki link their items (and effects and stuff) should be manageable enough (i.e. by posting on reddit a few days prior to launch). even better would be if all unknown id's would get added to a page and automatically removed once the id has been added to an item. Oranisagu (talk) 13:58, 16 August 2017 (UTC)

Maybe. The ids are stored in the API, so in theory we could write a script that takes each id and then trawls through the wiki in search of a match. Sounds like it would take forever to load, though. --Idris (talk) 17:23, 16 August 2017 (UTC)
I've played around with the #ask command in the hopes I could generate a list of all items in the wiki (like the vendor list and stuff like that) but I couldn't get it to work, as I don't really understand the system. if it was possible to generate a list of all ids in the wiki and then compare it to the list /v2/items spits out, it could be a way to find all missing items, add them or create an exclusion list for those not interesting enough to add. I mean this wouldn't have to be something that's done often, just every so often (as I think the API won't give item ids of things that haven't been found by players yet) Oranisagu (talk) 17:45, 16 August 2017 (UTC)
Sadly each chatcode query is generated on-the-fly on the client end using Javascript, the wiki never logs any results of what is searched for, therefore we can't add a list of automated items-searched-for-without-results.
We could however maintain a list of item ids within the API, and monitor the newly added ids (fairly trivial to do), and then query the wiki for the newly added ids. We would have to manually choose when to update the diff though.
There's a catch to using #ask with more than 5000 results- it's limited to an offset of 5000 +/- 500. Since we've got 51232 item ids denoted on the wiki, we can only really query for the first 5000 of them, which sucks for comparison. The good news is the items API has 57262 items, so we're not really missing too many (11%). I'll figure out a way to pull out the remaining ids. -Chieftain AlexUser Chieftain Alex sig.png 21:19, 16 August 2017 (UTC)
Here is a list of missing item ids from the wiki. raw / table-Chieftain AlexUser Chieftain Alex sig.png 22:37, 16 August 2017 (UTC)
A lot of these probably aren't directly viewable in-game or no longer exist because they are kept exactly the same but assigned a new id. I think we only care about items that are missing ids and don't already have an item article with the item name.--Relyk ~ talk < 04:53, 17 August 2017 (UTC)
Doesn't User:Darqam/GW2W Easy Mode#View New Entries effectively perform the same function? --Imry (talk) 05:57, 17 August 2017 (UTC)
I feel like a skritt in Tarir right now. --Idris (talk) 06:20, 17 August 2017 (UTC)

Nav box rework, version 2017[edit]

So, here we go again, I'd like to propose yet another revamp of several nav boxes.

A couple days ago I stumbled upon this navbox on the French wiki, and I realized that we don't have any option in the profession navbox to navigate from a profession to its elite specs, and also, for some reason, that ever since we removed elite spec skills from the core profession skill lists, no navbox we have manages to navigate between all pages with (at least non-racial) skill lists either. And since I had a few issues with a couple of our navboxes anyway, as well as with the situation changing a bit now that we have 2 elite specs per profession, I decided to try and improve our navigation between related pages once again. For this purpose I took the idea behind {{Specializations nav}} of showing a single profession by default and having the rest expandable, which I find to be a nice solution to the problem of the ever-growing amount of links to navigate between, and applied it elsewhere as well. At first, my plan was to try and make the navboxes adapt a bit more to the type of page it's on (such as a bit different default view on Elementalist vs. List of elementalist skills), but in the end I found it a bit unwieldy and unintuitive. So, right now, this is my suggestion:


Professions, specializations, lists of skills and traits
The current profession nav has bothered me with its square dimensions and surprisingly big focus on the Specialization page compared to the professions themselves ever since its last rework. I propose to add elite specs to it, since I think that might be a common use-case, and, similarly to the spec nav, to focus on a single profession by default while having the others expandable. Since it would replace the profession nav, it would still be useful to have a simple, concise list of all professions visible even before the expansion. A small problem would be elite spec pages, which would either end up having 2 navboxes under each other (Profession and Specialization) or one of them would be missing, breaking the intuitiveness of bi-directional navigation. A solution to this might be to merge the 2 similar navboxes into one – navigation from, say, Elementalist to Fire might not be that useful (hence making the core specs smaller in size), but the other way round would be.

Races and racial skills
I always wanted to have profession and racial skills link to each other, but I realized once again that is simply unfeasible. However, we should at least merge these two navs together.

Skill types and profession mechanics
These two nav boxes are quite weird: they have a significant overlap and they're rather messy. When we only had one elite spec per profession, marking elite spec skills and mechanics with italics made some sense, but now it's useless. Because it's often difficult to tell whether something is a skill or a mechanic (as it might be both), I suggest merging these two navs and using the italics for the mechanics instead. My main suggestion would be to follow a similar format to the spec and now profession navs in having only the relevant professions opened by default, and having a row for each elite spec so that they're distinguishable from each other. The disadvantage to this is that as time goes on, the table will get quite long, especially for something like Signet. I was thinking about multiple solutions, if need be – reworking the nav from divs to an expandable table, or hiding all professions for shared types by default – but I don't like either one. An alternative suggestion is to throw everything together, with varying degrees of icon usage and grouping, but they end up much harder to navigate, especially if you throw in every specific single-skill mechanic (like Steal) to the list, whcih the first suggestion handles much better.

Obviously, if I didn't think these would be an improvement, I wouldn't even suggest them; my personal pick would be versions (1eb), (2b), and (3aa) or (3ad). Now I turn to you: do you have any comments or ideas? Would you approve or oppose these changes? User Noxx Sig.png 20:29, 19 August 2017 (UTC)

I'm a fan of (1eb) for what it's including, though there's an argument for keeping specialization in the row in (1ea). The rest I'm neutral on, or I'll have to take more time to ponder, though please, not (2c)! Thanks for diving into this for us. G R E E N E R 21:42, 19 August 2017 (UTC)
Because there's no real point to having navs like this only static, I turned the more promising nav boxes to proper dynamic templates with a couple more examples:
Don't worry, (2c) is out of the question, that was a dead end. So, any more feedback? Preferences? Reasons why you might prefer the current navs? Knowledge of less hacky way to turn collapsing into toggles? User Noxx Sig.png 19:43, 22 August 2017 (UTC)

Zone navs[edit]

While we're on the topic of nav reworks, Doodle and I had a discussion about the state of zone navs a couple of days ago, about whether or not it was appropriate to include achievements in them. Doodle hasn't followed up on it in a few days because she's busy irl, so I thought I'd mention it here in case anyone has any thoughts to add: Read the discussion here; Example of one of the current zone navs here. --Idris (talk) 02:42, 20 August 2017 (UTC)

As far as I'm concerned, I feel like if a separate page is deservedly created solely to document an achievement (such as No Mask Left Behind), then it also deserves a place in the nav box. Minor achievements don't tend to get their own pages anyway, reducing the feared bloating of the table, and many pages are more about some sort of event, NPC or object, with the achievement just coming along for the ride – those achievements might just be covered by the More link. I agree the selection can get quite arbitrary at times, but I think that removing everything for that reason is an overreaction. I also wouldn't potentially be opposed to singling out JP achievements into their own Jumping puzzles row, even something like Mastery Insights gets one, but that's just a random thought...
Then again, I don't remember ever using the nav to switch between achievement pages, so if they get removed, I won't be starting riots about it either. ^^ User Noxx Sig.png 18:21, 21 August 2017 (UTC)

Achievement Hints Getting Pages[edit]

As per User talk:Greener#Data Keys and Aquitaine.1679 and Dash's comments on the on Wiki of Gold for the set for the Conspiracy of Dunces achievement. After a bit of a "oh no!" moment, I thought I had a bug and had lost the data keys for the Shattered Observatory fractal achievement, I did a bit of poking around and discovered that things like Data Key 3, 31 Zephyr, 1328 AE, and Parable of Lyssa, Page 2 aren't actual items in game, they are in fact achievement hints with icons. This isn't a new thing by the way, check out Lion's Arch Exterminator, all of the hints there are in fact pictures of Karka, and yeah if you poke the API you'll find 50 "Karka Hatchling (80)". I'm guessing in order to make some hints have icons in the achievement panel, they had to code them like items, but they're not actual items that can be picked up, and I don't think they should have pages-they're not items and it's misleading to pages that makes them seem as such. I will note that there are some of the Legendary weapons collections that do have an odd trophy or to that is similar, in that nothing enters the inventory, but those usually involve having a physical item in the players inventory and the player doing something with it as a result, so I wouldn't exactly count those as achievement hints as much as using an object to end the little lore quest. - Doodleplex 21:25, 20 August 2017 (UTC)

The API lists them as items so I think they should be added as items with a note that says it is consumed immediately. J.Tesla (talk) 22:03, 20 August 2017 (UTC)
The trick is they're not actually consumed because they're not actually items-it's basically an achievement hint indicated via an icon with mouseover text rather than just text. - Doodleplex 22:27, 20 August 2017 (UTC)
I can link to them in game chat like other items. They appear to be an evolution from the old collection items that only have use as part of a collection. Golden Priory Buckle as an example. Only now instead of receiving the item and having to delete it, it deletes itself to save time. Achievement hints have their own different entry in the API and are labels as “text” with recent examples from the rock collector achievement. On the surface they may appear the same but if we go against the API we will have issues when plundering the API for new data entries and whenever we document the outlier cases like the legendary collections. We should keep everything as consistent as we can with the API. J.Tesla (talk) 22:53, 20 August 2017 (UTC)
But they're not items, they're hints, and as a result nothing is collected because these achievements aren't collection achievements, they're scavenger hunt achievements just like the lost coins and badges. Additionally, for most of the lore scavenger hunt achievements, there has been a physical item that is obtained upon starting the achievement which is where all of the things found go, and usually uses Guide to Waterproofing.png or Adept's Training Manual.png, which look nothing like the hint's icon and as a result that's why originally I thought the Conspiracy of Dunces pages were actual items as well as why I thought I had a bug for the data keys. They're not items, and that's misleading. Also with Anet, nothing is really ever consistent, so because of that just it's in the API doesn't mean it's an item. - Doodleplex 23:52, 20 August 2017 (UTC)
What Tesla is saying is that they are mechanically classified as items. However, they do not show up in the inventory at any given time (due to auto-consume/delete). They have API ids just like any item does. This is not like the lost coins and badges, which do not have such items. This is why they have icons in the achievement panel and can at times be alongside items that are seen in the inventory. If they were as you said, the entry in the achievement panel would be akin to what we see for meta achievements - a list of short sentences, not a square icon-filled box with highlighting text. Konig (talk) 00:02, 21 August 2017 (UTC)
I understand what he's saying, I'm saying the ArenaNet is inconsistent and as a result things can be confusing and that tends to cause us hiccups and confusion. After pondering, I think the best thing to do is this: these pages get turned into redirects that go to the appropriate achievement page and the content be moved to the walkthrough on the achievement page with a note being put at the bottom that all of the items for the achievement never enter the inventory. That way the walkthroughs get the attention they need, nobody gets confused/mislead/wonders where the item went, and if people search for the hint/item/whatever they go to a page that gives them all the info they want on how to find it and the rest of the stuff for an achievement. - Doodleplex 00:59, 21 August 2017 (UTC)
Uh, the game considers them items and therefore the wiki does. Creating an item page is preferred, just like with story journal items; we don't have to store an item subobject with the achievement object. The pattern should be the same as legendary weapon collections, where you are trashing all the useless achievement items right after getting them. I disagree with being confusing, as the achievement tracks all your items for you and navigating between the individual items and the achivement is not difficult or confusing. We should start adding the autoconsume flag to the infobox though.--Relyk ~ talk < 03:29, 21 August 2017 (UTC)
I've already discussed this at Greener's talk page, and can only agree with the several statements above. They're items, they have descriptions, IDs, icons and language links. They should be documented on this wiki. —Ventriloquist 10:41, 21 August 2017 (UTC)
We could add a new parameter to the item infobox that lets us specify if an item is a deleted-on-acquisition achievement hint? --Idris (talk) 15:42, 21 August 2017 (UTC)
I would think a line of text, rather than an infobox parameter, would be sufficient. E.g. "This item is autoconsumed upon receipt." -Chieftain AlexUser Chieftain Alex sig.png 17:03, 21 August 2017 (UTC)
I was thinking that the infobox approach would let us easily compile lists of such items, assuming we'd ever want to do that. --Idris (talk) 17:36, 21 August 2017 (UTC)