Path of Exile Wiki talk:Community portal/Archive 4

This is an archive of past discussions for the period June 2014 to July 2015.

Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

• ← 1
• 2
• 3
• Archive 4
• 5
• 6
• 7 →

Revisiting weapon categorization

I've been thinking about revisiting weapon categorization, but I'm not sure which scheme to use (if any). Let me know what you think.

Current	Option 1-A	Option 1-B	Option 2-A	Option 2-B
Axes Bows Claws Daggers Fishing rods Maces Staves Swords Wands	One-handed axes Two-handed axes Bows Claws Daggers Fishing rods One-handed maces Two-handed maces Staves One-handed swords Two-handed swords Wands	Axes One-handed axes Two-handed axes Bows Claws Daggers Fishing rods Maces One-handed maces Two-handed maces Staves Swords One-handed swords Two-handed swords Wands	One-handed axes Two-handed axes Bows Claws Daggers Fishing rods One-handed maces Sceptres Two-handed maces Staves One-handed swords Thrusting swords Two-handed swords Wands	Axes One-handed axes Two-handed axes Bows Claws Daggers Fishing rods Maces One-handed maces Sceptres Two-handed maces Staves Swords One-handed swords Thrusting swords Two-handed swords Wands

—Vini (t|c) 03:21, 12 July 2014 (UTC)

2B makes the most sense to me. Iamacyborg (talk) 11:30, 12 July 2014 (UTC)

With options 1-A and 1-B it's a simple matter to generate categories automatically. With 2-A and 2-B I'm not sure how to distinguish thrusting swords and sceptres with only the data currently available. —Vini (t|c) 12:00, 12 July 2014 (UTC)

In that case, 1-B would be the best, as it more closely reflect the weapon categories within the skill tree. Just FYI, I fixed what I assume was just a typo in the table, with Maces incorrectly labelled as Axes in 1-B. Iamacyborg (talk) 17:37, 12 July 2014 (UTC)

I'm good with the categorization now, but I don't quite like how I have the pages themselves set up currently. I'll work on improving this. —Vini (t|c) 23:35, 19 July 2014 (UTC)

Pages that exceed post-expand include limit

I noticed that there are a few pages which exceed the post-expand include limit, namely list of unique items and Full Item Index. This is an issue where the total include data is simply too long. We might not be able to use these extremely long item indexes. —Vini (t|c) 22:03, 19 July 2014 (UTC)

Yeah, just having a look now. It's a pain in the arse, particular the full unique page as that's one of the most popular pages on the wiki. I guess we'll need to look into the best way to present those pages now, and how they'll need to be reworked. Iamacyborg (talk) 23:40, 19 July 2014 (UTC)

I did a little experiment to see roughly how many item tables would fit on a page before reaching the post-expand include limit. I specified in the wiki code to output all unique item tables and I also doubled the number of uniques displayed in each table by repetition. As you can see, the result is not promising. As GGG releases more and more uniques, we will be able to show fewer on the page at once. I don't exactly have a solution for this. The item templates are extremely convenient, but simply don't lend themselves to this sort of mass inclusion. I currently know of no way to make the templates more efficient in terms of inclusion data length either. —Vini (t|c) 03:35, 21 July 2014 (UTC)

What do you think about using the current unique item page as the main hub, linking down to individual item type lists through top and bottom navboxes? Those individual item list pages would then all link to one another again through navboxes placed at the top and bottom of the page. I know it's not an ideal solution, but I can't see a reasonable way of keeping all the pages up to date without creating many times more work for everyone involved. Iamacyborg (talk) 17:37, 21 July 2014 (UTC)

What if we redirect list of unique items to the unique item page, and rework that page so that the lists are more accessible? —Vini (t|c) 17:47, 21 July 2014 (UTC)

Yep, that's what I had in mind. We'll also want to improve the navigation between the individual unique item list pages so people can more easily find the items they're looking for. Iamacyborg (talk) 18:06, 21 July 2014 (UTC)

Jumping in here because I told some random stranger in 5055 that I would. Why? I dunno, really. Anyway, he asked me to put forth the suggestion that rather than break the unique items page into sections for each individual item type, you break it into broader classes like weapon, armor and jewelry. While this would only be a temporary solution, I am all for anything that reduces the number of unique pages.

As for my own suggestions, would it help any to use inline links? They're clickable anyway, so if you want to go to an individual item's page to see more information, you can. Another idea, which I honestly don't know is even possible on a wiki, is to embed the individual "list of unique boots" etc. pages into one master page. Would that get around the limit while still being able to function the way it used to? EDIT: Aaaand I forgot to sign. ∞ The one, the only, the Moses

Thanks for the suggestions. What you suggested at the end there is essentially what we're already doing. And no, it doesn't avoid the post-expand include limit because "embedding" (actually it's called transcluding) the pages contributes to the limit. The fact that we're trying to transclude all of the individual pages into one super long page is why the problem exists. —Vini (t|c) 07:37, 13 November 2014 (UTC)

Lua extension

I thought we had the Lua extension installed, but that doesn't appear to be the case. Am I just remembering incorrectly? If so, is there a way we can get this installed perhaps? —Vini (t|c) 03:30, 22 July 2014 (UTC)

I'll ask! Iamacyborg (talk) 11:51, 22 July 2014 (UTC)

It's now been installed, let me know if it's not working as you want it to. Iamacyborg (talk) 15:02, 22 July 2014 (UTC)

It seems to be installed correctly. I created a test module and was able to invoke it without issue. —Vini (t|c) 22:03, 22 July 2014 (UTC)

I've spent several days experimenting with Lua and I believe I've traced an error that has been haunting me to the frame:getTitle() function. As described in a talk thread on Mediawiki, the getTitle function was added in the version of Scribunto for Mediawiki version 1.23. In order to get access to this function, we'd have to update Mediawiki as well as Scribunto. How difficult would it be to upgrade? —Vini (t|c) 05:00, 26 July 2014 (UTC)

Updating Mediawiki should be fairly simple, although Curse tend to update all wikis at the same time. I'll check with Ben to see when the next scheduled update is. I'm not sure about Scribunto, I'll have to check on that as well. Iamacyborg (talk) 11:09, 26 July 2014 (UTC)

I can confirm that the update to MediaWiki 1.23 that Curse made in September fixed this issue. —Vini (t|c) 02:29, 8 November 2014 (UTC)

Proposal for merging the Vaal Orb and Corrupted pages

I don't really think there's any point to having two pages when the two concepts are so closely tied together. I've created a page here to demonstrate how I wish to arrange the information. It also contains more detailed information not present on the original pages. What I'd like to do is change the Vaal Orb page to the linked page, then either link the corrupted page to the Vaal Implicit section or keep a small amount of information regarding corrupted areas and vaal skill gems (though both of these have their own pages already, so IMO this is not necessary). Looking for ideas, suggestions, corrections, etc. ∞ The one, the only, the Moses 04:31, 30 July 2014 (UTC)

I think I'm fine with consolidating the information specifically regarding Vaal Orbs on the Vaal Orb article. However, I don't agree that the article about the corrupted modifier should simply be merged into the Vaal Orb article. Corrupted has other distinctions besides Vaal Orbs, so there should be two pages. —Vini (t|c) 04:43, 30 July 2014 (UTC)

Which distinctions, though? Again, corrupted areas and vaal skill gems both have their own pages. Is there something else that I'm missing? If not, would it be enough to make a small note on each page? Something like, "Due to the corrupted modifier, this (gem/area) cannot be modified by currency." ∞ The one, the only, the Moses 05:25, 30 July 2014 (UTC)

I agree with Vini, a lot of the information should be consolidated onto the Vaal Orb page, but we should maintain them separately for the time being, at the very least it would be useful to keep it separate as a disambiguation page. Iamacyborg (talk) 20:49, 30 July 2014 (UTC)

Any objections to these Vaal Orb and Corrupted pages? I'll move the info to the main pages today if no one objects. ∞ The one, the only, the Moses 10:53, 4 August 2014 (UTC)

I think I'm good with it. —Vini (t|c) 11:42, 4 August 2014 (UTC)

Happy with both those pages! Iamacyborg (talk) 16:59, 4 August 2014 (UTC)

Allow a redirect from Corrupted to Vaal Orb Implicits. Removed icons from inside table, the heading icons needs to be bigger or in text. I would be alot better if they were organized by weapon first then armours. 1BLOOBERRY (talk) 1:57, 5 August 2014 (UTC)

I recommend using text, rather than the icons. —Vini (t|c) 17:30, 5 August 2014 (UTC)

Deleting User Pages?

I vaguely remember being told that only admins could delete pages. I was wondering if things could be changed to allow users to delete sub-pages of their own user page. If not, please delete User:TheOneTheOnlyTheMoses/Corrupted and User:TheOneTheOnlyTheMoses/Vaal_Orb. Also, if there's already a way to do this and I just am not seeing it, please correct me. ∞ The one, the only, the Moses 23:31, 5 August 2014 (UTC)

There is not a way for normal users to delete pages, even if they are merely sub-pages of their userspace. However, you can mark pages for deletion using Template:Delete and an admin will eventually take care of it. —Vini (t|c) 21:42, 7 August 2014 (UTC)

Supporter newsletter numbering issues

Probably most of you didn't realize this, but there has been a problem with the numbering of the supporter newsletter issues. The issue that was released on July 20 was the seventy-fourth issue, but it was erroneously published by the GGG staff in charge of the newsletters as issue #73. You'll notice that the subreddit thread is correctly titled #74 though. This is because I informed beastfsho of the problem and he created a new thread. However, since that time GGG has not rectified the numbering problem and continues to be off by one each time. The seventy-fifth issue was put out as #74, the seventy-sixth issue was put out as #75, and so on. This is really annoying since the numbering in the archive does not match the published issue number. What can we do to fix this? The simplest and best option in my opinion would be for the GGG staff in charge of the newsletters to fix the numbering by releasing the next issue as #78 (not #77), but if they can't or won't what should be done? —Vini (t|c) 03:57, 11 August 2014 (UTC)

I didn't expect this latest issue to be the last issue ever, so I guess this point is rather moot now. Oh well... —Vini (t|c) 04:14, 11 August 2014 (UTC)

Forsaken Masters

Hi, since there has been no info related to Forsaken Masters on the wiki yet, I went ahead and created some pages for it, which in turn need a lot of updating when it is actually released or more is available. All Pages related to the update are in Category:Forsaken_Masters with a sub category for the new masters Category:Forsaken_Masters_NPCs.

--OmegaK2 (talk) 22:44, 12 August 2014 (UTC)

Thanks for the good start. Lots more for us to catch up on as well. Iamacyborg (talk) 16:27, 13 August 2014 (UTC)

Now that I have a chance to comment on this, I want to say that I dislike the idea of using this categorization. The distinction of "pages related to the update" becomes largely arbitrary and useless the farther away from version 1.2.0 we move. If people want to see what content has been introduced by the patch, they can simply read the patch notes. Please don't misunderstand me; A category for the masters actually does serve a purpose, however I would like to rename it to simply Category:Masters. —Vini (t|c) 00:30, 22 August 2014 (UTC)

I don't have a problem with this category being used as a parent category for the new features specifically added in this expansion, such as masters, hideouts, beyond/corrupted monsters. Similarly a SotV category could be a parent to the categories for strongboxes, invasion bosses, and corrupted areas. But I don't think it is appropriate to use such categories for skill gems or uniques, as this is not a fundamental property of the skill gem so much as a coincidence of timing. We could create an entire "Skill gems by Version introduced" tree, but a list page (Skills by Release Date) should be sufficient for this. --Qetuth-(talk) 00:52, 4 November 2014 (UTC)

I agree with all of that. Looks like the skills by release date page is another project that needs working on. ~Bobogoobo (talk) 02:28, 4 November 2014 (UTC)

Helpful Tip on Updating Old Skill Gems

To who haven't realized this yet, poe.xyz.is and player's shop posts are generally a very, very easy way to find updated/reworked gem information. Its a little slow/laggy to do this since you have to check each gem level in a totally different shop usually. Of course this isn't as useful with brand new gems as its unlikely anyone is going to be putting those in a shop for awhile. Ebonmourn (talk) 18:36, 22 August 2014 (UTC)

Just a note on this for future reference: While this is a great way to collect some gem data like mana costs, there are some modifiers which the website interface and hence xyz's data rounds to less accuracy than in game display. Claritys mana regen is an example of this. --Qetuth-(talk) 00:16, 4 November 2014 (UTC)

That's a good point. We should always display it on the wiki the same as in game. —Vini (t|c) 01:36, 4 November 2014 (UTC)

Fan portal in sidebar

I would like to revisit the links displayed under the fan portal section in the sidebar. First of all, is ExileStats even a site that people use anymore? It's listing ladders from Anarchy and Onslaught. As for shop indexers, poe.xyz.is is still the main one that people use. Unlike poemarkets, poe.xyz.is provides a tutorial and doesn't have missing character glyphs in the user interface. Shouldn't we link to poe.xyz.is instead of, or at the very least in addition to, poemarkets? Are there any other widely used online tools or fan sites that we want to link to? —Vini (t|c) 13:17, 28 August 2014 (UTC)

Maybe link to Procurement? Or at least, the thread on the forums. Happy to swap the market site to xyz, and to get rid of ExileStats. Iamacyborg (talk) 14:38, 28 August 2014 (UTC)

I think linking directly to the page for Procurement on Google Code is fine. It gives a good description with images and links back to the forum thread. —Vini (t|c) 14:44, 28 August 2014 (UTC)

Cool, I'll update. Iamacyborg (talk) 14:57, 28 August 2014 (UTC)

Tilesets

I'm wondering what we can do with tilesets: Most maps and corrupted areas reference them (and hideouts too!), but I'm not sure if there is any purpose to a page for each. There are monster type tendencies connected to the tilesets, but not absolutes.

I was thinking of a "List of areas by tileset" type page, and also categorizing areas by tileset. What does everyone else think? --Qetuth-(talk) 11:11, 19 September 2014 (UTC)

Your suggestions sound good for now. I don't think we need anything more complicated than that for the time being. Iamacyborg (talk) 12:05, 19 September 2014 (UTC)

I have made a start at sorting them at tilesets - I'm not sure how closely to group some tilesets - a lot of areas have the same basic terrain but a few distinct doodads setting them apart (eg the act 1 outdoor areas). Any advice there would be appreciated --Qetuth-(talk) 05:13, 22 September 2014 (UTC)

Searching by wiki code, or some other way of finding old pipes

Is there any way to search pages by wiki code, or a list of piped links or something? I am asking because I keep coming across pages with old links piped to a current page, eg "[[Unique Monsters|Gneiss]" or "[[Unique Items|Death's Harp]" and with so many pages legitimately linking to these master pages it is hard to find the ones that shouldn't be. --Qetuth-(talk) 03:48, 21 October 2014 (UTC)

Yes, actually. Go to the Unique Monsters page and click "What links here" in the sidebar under tools. It will list all of the pages that link to to that page. —Vini (t|c) 03:52, 21 October 2014 (UTC)

I use What links here a lot. It lists links to the page and links to redirects to the page which is great. My problem is I don't know how to distinguish, among the 320 or so pages that link to Unique Monsters, which ones are links in templates, which are piped links, and which are straight links. At least without checking each page individually. --Qetuth-(talk) 11:45, 21 October 2014 (UTC)

There are only a handful of pages to check though, and some of these you don't even need to check since they are user pages or talk pages. —Vini (t|c) 13:38, 21 October 2014 (UTC)

Hideout pages

I think it would be useful if hideout pages had at least one image of what the hideout looks like (when you first get to it) so they can be compared. That would be one way to get those pages a little more fleshed out. ~Bobogoobo (talk) 10:00, 3 November 2014 (UTC)

The current hideout pages are largely stubs and could definitely do with more stuff, including pictures. Go for it. Long term I was thinking the rather cluttered individual Master pages could be split into say Elreon with the overview, crafting, and store info, Elreon missions with the list of quests, monsters, areas, experience, and Enlightened Hideout with the decorations list (they could do with pictures too!). --Qetuth-(talk) 00:25, 4 November 2014 (UTC)

You don't want me to take pictures, I play on 1024x768 fullscreen with minimum settings and texture quality 4 :P. I'll leave it to someone who can get good quality ones. ~Bobogoobo (talk) 02:28, 4 November 2014 (UTC)

Dead-end pages

Most of the pages in Special:DeadendPages could have links added for the equipment type, microtransaction type, etc. Proposed examples:

• Abyssal Sceptre: "Abyssal Sceptre is a normal one-handed mace."
• Acid Scorpion Pet: "Acid Scorpion Pet is a type of pet obtained through microtransactions."
• Acid Weapon Effect: "Acid Weapon Effect is a type of weapon item effect obtained through microtransactions."

Not really much to say, since each list of items has pretty much the same information. Individual pages don't have the flavor text contained on the listing pages though, so that could be added if you want to give those pages a bit more content. ~Bobogoobo (talk) 02:31, 4 November 2014 (UTC)

For mtx it would be good to have the flavour text from the store, and the basic non-discouted cost. For weapons, I don't think linking to rarity is that useful (since really the Abyssal Sceptre page is the page for all Abyssal Sceptres) but I don't know what else could go there. Maybe a basic DPS calc for comparison with other weapons? --Qetuth-(talk) 02:48, 4 November 2014 (UTC)

Right, that makes sense. DPS display sounds useful. We might as well build all this into the Item template, if possible. ~Bobogoobo (talk) 03:06, 4 November 2014 (UTC)

I'm still not sure why it's even necessary to display prices for MTX on the wiki. I don't know if the prices actually change very often, but it's just one more thing that has to be maintained. Nobody is going to come to the wiki to look up prices for MTX when they are right on the website. —Vini (t|c) 05:02, 4 November 2014 (UTC)

On individual MTX pages maybe, but on skill pages I think it's useful to display the MTX price. The categorisation on the official site is pretty sucky, so it's not easy to find all MTX for one skill. Iamacyborg (talk) 18:03, 4 November 2014 (UTC)

Well, you've convinced me that it has some utility at least. Tell me what features are needed and I can build them into the item templates. —Vini (t|c) 21:28, 4 November 2014 (UTC)

Video link and price for sure, can anyone think of anything else? Iamacyborg (talk) 12:55, 5 November 2014 (UTC)

Proposal for cleaning out unused Korean translation pages

I would like to suggest cleaning out (ie, deleting) any of the many unused Korean translation pages that are cluttering up the wiki. In a whole year, nobody has edited these or added more Korean translation pages. Not only are these pages severely outdated at this point, many of them are merely placeholders and do not even contain translated text. —Vini (t|c) 08:39, 7 November 2014 (UTC)

I have noticed most of those, and the Japanese ones as well, are out of date, referring to old area names or incorrect data etc, so this seems like a good idea. Is there a way to see how often they are viewed? (I remember using such tools at wikipedia, but can't see it here) --Qetuth-(talk) 09:14, 7 November 2014 (UTC)

The Korean pages have had about 12k pageviews total since January 1st, so I'm more than happy to scrap them all, particularly as they're way out of date now. Japan's had a fair few more at about 44k, but I'm happy to get rid of them as well as they're not at all maintained. I don't think there's a tool that's accessible for non-admins, but I can ask the Gamepedia team if they can put something together. Iamacyborg (talk) 17:17, 8 November 2014 (UTC)

Very well. I am scheduling the nuclear launch to wipe out all Korean and Japanese translation pages for November 27th. If anyone disagrees with this action, you have two weeks to say your piece. —Vini (t|c) 07:45, 13 November 2014 (UTC)

S'all good with me. Iamacyborg (talk) 18:24, 13 November 2014 (UTC)

Purge complete. —Vini (t|c) 13:15, 27 November 2014 (UTC)

Nice one. Iamacyborg (talk) 13:34, 27 November 2014 (UTC)

Math extension

According to the Gamepedia Help Wiki, we're allowed to install, the Math extension. This has been requested before and I would also like to request it. Can we get this extension installed? —Vini (t|c) 23:27, 26 December 2014 (UTC)

Proposal for Unique Item Rarity

I'd like to propose adding a column on unique item tables entitled "Rarity" to denote a unique item's drop/chance frequency. This can be very simple information conveyed by a single letter such as C, U, and R along with an asterisk where necessary. Add an key to the bottom of unique tables:

• C = Common Unique. These are items that you could expect to drop while leveling a character. It is likely that dedicated players will see multiple of these items.
• U = Uncommon Unique. These are items that you could expect to drop within the span of a couple months (one league). Dedicated players may see these drop.
• R = Rare Unique. These are items that only a few players will see drop. Some players may play for years without getting one.
• * = Special (Added on to any of the above. Example: R*). These items are league-only drops from past leagues or no longer available.

Exacting accuracy is unnecessary. But if something like this could be added, I think it would be VERY helpful for the many folk who use this site thinking, "I'll make a build based around X unique because X looks like a lot of fun!" only later to find that the unique in question is super rare / out of price range / no longer available in temporary or permanent leagues without Zana.

(P.S. Thank you to all of those who maintain and update this fine site. It's an amazing piece of work that has saved countless players many hours of frustration!) —The preceding unsigned comment was added by Sederien (talk • contribs) 06:03, 28 December 2014 (UTC)

While I do think it could be useful to have such information displayed on the wiki, I'm not aware of any official source that divulges the rarity (or even relative rarity) of unique items. If based on independent research consisting of extensive data gathering, it might be considered trustworthy depending on the methods used. On the other hand if it's based on personal experience and conjecture, it's really not suitable for inclusion on the wiki. —Vini (t|c) 07:03, 28 December 2014 (UTC)

That's a good point and I fully agree. Perhaps someone with trade data could look at the availability of items in the market as a proxy for rarity. It's not a perfect proxy, of course. (Items that may be used vs. traded, desirability of items, etc.) Yet, I think we could generally agree that with very broad categories of rarity, items with thousands of copies for sale vs. a handful could give a decent impression of the data. We might have to have a "not enough data" tab for some of the harder to track/newer items. (EDIT: Of course, methodology can be included on the wiki itself so players have this information as well.) --Sederien (talk) 17:42, 28 December 2014 (UTC)

Quest Rewards page timing out

The Quest Rewards page seems to be timing out when users attempt to edit it. Can we get the Curse people to look into this? —Vini (t|c) 20:23, 13 January 2015 (UTC)

I'll make sure they see it. Probably related to the previous issue with skill pages. Iamacyborg (talk) 21:51, 13 January 2015 (UTC)

I don't think it's the same issue. Those templates aren't used on the Quest Rewards page. —Vini (t|c) 22:52, 13 January 2015 (UTC)

True, but maybe the page being slow caused the issues with the templates. Iamacyborg (talk) 02:16, 14 January 2015 (UTC)

I can't see how the two things could be related. Those templates don't have anything at all to do with the Quest Rewards page. —Vini (t|c) 02:21, 14 January 2015 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ I've also been getting time-outs editing Summon Raging Spirit. --Qetuth-(talk) 22:19, 14 January 2015 (UTC)

This is the other issue we were talking about. Probably many of the skill pages are having this problem. What we need to do is manually populate the Quest Rewards section on each skill page, rather than using {{QuestReward/Skill}}. If you want to start on that, you can. —Vini (t|c) 22:37, 14 January 2015 (UTC)

Yep, we need to get around to manually fixing all the skill pages. I did some of the newer ones but there's a load left to go through as well. Iamacyborg (talk) 15:45, 15 January 2015 (UTC)

Do we want to replace it with just the link to the quest rewards page (lacks data the reader may be looking for, but never needs updating, a copy of the current info, or both? Or maybe we could subst the current template calls, so it only needs to be edited once per page, and again whenever rewards get changed, but shouldn't interfere with other editing? --Qetuth-(talk) 02:02, 16 January 2015 (UTC)

You can't use subst on {{QuestReward/Skill}}. It won't do what you think. Not all templates are meant to be used with subst. —Vini (t|c) 06:37, 16 January 2015 (UTC)

My choice would be to link to the page, just for the sake of it being easier to maintain over time. Having people check another page will be better than people complaining because some info isn't up-to-date. Iamacyborg (talk) 14:48, 16 January 2015 (UTC)

Passive skill tree image

Could we get an updated image for the passive skill page? It's still showing the tree from 1.0.0. I don't know how to get such a large image (or if I even could on my system). ~Bobogoobo (talk) 21:17, 22 January 2015 (UTC)

I'll need to see what's possible for getting the image. I don't think there's any version of it available anywhere so we'll have to hack our own one together. Iamacyborg (talk) 22:23, 22 January 2015 (UTC)

In-game item screenshots and Hideout items

It'd be great to show what items look like in-game on relevant pages. How does everyone feel about starting off this process by creating some image guidelines to kick this off? Iamacyborg (talk) 22:58, 18 February 2015 (UTC)

Starting off by creating guidelines sounds like a good approach. —Vini (t|c) 23:11, 18 February 2015 (UTC)

540 x 800 size should be good to see the item in enough detail. That's assuming a fully zoomed in screenshot that's been cropped down to see the character. Using the Marauder would be a good base as well to keep things consistent as his character model doesn't have too much going on. Screenshots should be taken in the Tidal Island as there's good lighting there. Character should only have the item to be shown equipped. Screenshots should be taken with the character facing forwards, backwards, left and right to see the item properly. How does that sound? Iamacyborg (talk) 17:25, 19 February 2015 (UTC)

Improvements to item templates

In this post I will explain the improvements I made to the item templates. Initially I didn't want to bother writing a post about this, because 1) nobody cares and 2) I'm lazy; but for those who are interested in wiki editing and how this wiki in particular works, please read on.

Recently, I rebuilt the item templates from scratch using Lua. As of writing this, these templates are used on well over a thousand pages on this wiki. They are what allow you to do neat tricks like typing {{il|Coral Ring}} and getting Coral RingCoral Ring+(20-30) to maximum Life (mouse over the link), which uses the data taken straight from the Coral Ring page. It makes editing the wiki extremely convenient, because we can take that same data and format it in lots of different ways, like putting it in a table.

Previously, this was all done using intricate features of Media Wiki's template syntax, which if you've ever worked with you know is more akin to writing regular expressions than anything in a modern programming language. The Lua module functionality added by the Scribunto extension allows you to create complex templates using actual, readable code. Better still, running Lua is also much more efficient than the wikicode parser.

The new implementation is also leaps and bounds better for pages that transclude a lot of templates. We previously had an issue where at the end of long pages, templates would not get transcluded. This is because Media Wiki has a hard limit on the amount of data that can be generated by templates. The new implementation doesn't "fix" this—the limit still exists—but it greatly cuts down on the amount of data contributing to the limit. I didn't bother recording metrics to illustrate this, but trust me, it makes a big difference.

I also added a feature in the new implementation that cuts down redundant fetching of item data on pages that want to display the same items many times on the same page, such as the vendor recipe system page. It does this by saving the data output by the template; in this case, I'm talking specifically about Template:Il. If that same item has already been displayed on the page before, it will simply re-use that data rather than fetching it again from the item page. So in other words, if I type {{il|Chaos Orb}} {{il|Chaos Orb}} {{il|Chaos Orb}}, displaying Chaos OrbChaos OrbStack Size: 20Reforges a rare item with new random modifiersRight click this item then left click a rare item to apply it. Chaos OrbChaos OrbStack Size: 20Reforges a rare item with new random modifiersRight click this item then left click a rare item to apply it. Chaos OrbChaos OrbStack Size: 20Reforges a rare item with new random modifiersRight click this item then left click a rare item to apply it., it will only fetch the item data from the Chaos Orb page once!

Cool stuff, right?

—Vini (t|c) 12:27, 27 April 2015 (UTC)

Awesome work, thanks Vini. Does this mean we can make a Unique Item Index again? --Climmels aka SirProblematique (talk) 14:07, 27 April 2015 (UTC)

It certainly appears that way: http://pathofexile.gamepedia.com/index.php?title=List_of_unique_items&oldid=96656 I'm not sure whether that's something we really want to be doing though, particularly with an extra 70ish uniques coming out with The Awakening. Iamacyborg (talk) 14:34, 27 April 2015 (UTC)

Yeah, I'm not sure if it's such a good idea. If people just want a list of unique items, there's Timeline of Unique Items. —Vini (t|c) 20:38, 27 April 2015 (UTC)

I know people have been wanting an easy way to search all unique items for specific things, for example spell block, which the single page makes relatively easy. I guess we could always try it out once the new uniques are in place to see if it even works, I do prefer the current system we have though. Iamacyborg (talk) 20:52, 27 April 2015 (UTC)

Is there a way to explore the limit of uniques on one page now? If, let's say, the limit is 500, I think it's worth it to create a page since it won't reach the limit for at least a year. If it's lower, it's not worth it since we'll have around 400 uniques at the release of The Awakening anyway. It was one of the most popular pages on the wiki and like you said, very useful for finding all uniques related to a specific mechanic. --Climmels aka SirProblematique (talk) 21:24, 27 April 2015 (UTC)

Damn dude, you're a wizard. Iamacyborg (talk) 14:30, 27 April 2015 (UTC)

That's awesome. But I draw your attention to The_Awakening#Unique_items among other pages - can that be made to look less....red? At least some of those are il templates pointing to non existent pages, but at least one is an il template with a typo, and it's basically impossible for a regular editor to tell the difference. --Qetuth-(talk) 23:33, 28 April 2015 (UTC)

I'm not aware of any way to avoid a fatal script error if the page doesn't exist. I realize that most people aren't used to seeing a mess of script errors, but actually checking whether the page exists is a costly operation. The method I'm using is the best I could come up with in terms of performance, which is more important than avoiding the words "script error". I'm not sure how this makes life particularly difficult for editors, considering on the page editor it gives you a list of the templates/pages you're trying to include and displays the ones that don't exist in red. —Vini (t|c) 14:43, 29 April 2015 (UTC)

Okay, I was hoping there would be some (easy) way to replace that with a more specific instruction (like page missing). Still, great work. --Qetuth-(talk) 08:51, 30 April 2015 (UTC)

Awakening Content

Hey. What are your guys thought on adding the awakening content already into the wiki? I've seen some stubs being added already.

A lot of stuff is subject to change I guess, but I think it may be good to start gathering info and data. Since some existing pages might be changed, it may be good to create subpages, like ... Gem/beta and merge them later into the main page as the update goes live. As well as using "Category:Awakening" or so to make things easier to find for people. --OmegaK2 (talk) 20:21, 28 April 2015 (UTC)

See The Awakening for list of beta related links, and conversation at Talk:Path_of_Exile_Wiki#Upcoming_Closed_Beta_patch_notes which kind of stopped before coming to a decision. I think though a new section on a page is better than a subpage. --Qetuth-(talk) 23:25, 28 April 2015 (UTC)

Well, some of the gems for example have substantially changed so that the item flavor box would have to be replicated as well. I'm not sure, it may be better to hold off with the new data before it's put on the main page, I'd not want people to be confused over it (and I think it's more subject to random changes now then after the release). Though it makes sense to create new pages for any new items already (did that the jewels). I think a category would be good, possibly also an awakening navbox to provide an overview. --OmegaK2 (talk) 05:23, 2 May 2015 (UTC)

Please don't create subpages of articles in the main namespace. If you want to gather data and need a place to put it, you can always create pages in your userspace. —Vini (t|c) 23:28, 28 April 2015 (UTC)

Allright. Also see my response above --OmegaK2 (talk) 05:23, 2 May 2015 (UTC)

OK, have people actually created alternate versions of pages reflecting known (and likely not be changed) changes in the Awakening? Thanks to Chuanhsing I think we should have enough to go on to essentially make everything accurate for 2.0.0. Can I suggest that we deploy all these changes in advance of the Awakening update? This will likely mean that, for a brief time, the entire wiki is inaccurate because it does not reflect the current version, but I think that this downside is completely counteracted by having a full functional and (mostly) accurate wiki online at the moment the expansion hits. Lots of people can use the wiki reliably. Also, I can at least say for myself that I will be playing 2.0.0 myself, so I'll have less time to update the data once the patch is actually released.

I am willing to do a lot of the work, but I don't want to do anything that other people have already done. TheMipchunk (talk) 19:33, 8 July 2015 (UTC)

I agree, we should start making the changes. I'll be playing the new leagues too, so I'll have less time to edit the wiki then.

If anyone needs inspiration;

here is a fraction of the things that need updating:

• Area progression changes (levels and structure) in the first three acts
• New leech mechanics
• Reduced Mana and Enlighten changes
• Gem vendors
• "Shotgunning" changes
• Arctic Armour
• New base weapons need to be added
• New skill gems
• New unique items
• Info about jewels
• Mention of div cards on the items they produce
• Add the new maps and new map icons. (You'll have to figure out which image belongs to what map, because they're just called "map12" etc in the game files.)

Some act 4 stuff that needs work:

• Quests pages need to be created
• Highgate NPC's
• Monsters and bosses
• Flavour text of the new zones (no idea where to find these, I don't play the beta)
• Zone and monster screenshots

--Climmels aka SirProblematique (talk) 20:08, 8 July 2015 (UTC)

Nice list! Maybe we can divide up the tasks? For starters I can work on the changes to existing skill gems, including Arctic Armour and Reduced Mana. Maybe we can create a template banner to put on updated pages that says something like "This page is being updated for The Awakening. It may no longer be accurate for the current version of Path of Exile." TheMipchunk (talk) 20:47, 8 July 2015 (UTC)

I've got the rewards covered which includes the gem vendors. --OmegaK2 (talk) 20:56, 8 July 2015 (UTC)

Not a bad idea. I'm useless at creating templates though. I remember we had a similar "notice" template when 1.2.0 was released but I can't remember what it was. Dividing the work sounds good to me. I'll focus on Act 4 NPC's and quests. --Climmels aka SirProblematique (talk) 21:15, 8 July 2015 (UTC)

I created a really basic fmbox template Template:AwakeningUpdate that can be used at the top of a page to indicate that the page may not be accurate until the expansion is released. TheMipchunk (talk) 01:31, 9 July 2015 (UTC)

Revisiting full index of unique items

After the performance improvements I made to the item templates, it was asked whether it would now be feasible to bring back the full index of unique items. I created a page preview displaying all unique items (including the new jewels) and the post-expand include size was 1,411,609 out of 2,097,152 bytes. That means we're already 75% of the way to the maximum possible limit, even with the improved templating. Even if the full index was possible now, it will not be possible in the future as GGG adds more uniques to the game. The other issue is that when I tried saving my test page, the server timed out. I tried saving it again, and again the server timed out. So the full index of uniques does not seem feasible at the moment. —Vini (t|c) 02:40, 1 May 2015 (UTC)

Differentiating skills from skill gems

It has been discussed before whether it would make sense to differentiate related concepts such as skills and skill gems in the way that they are presented on the wiki. Previously in the game's history, player character skills were were explicitly tied to gems, so it was not necessary to draw a clear delineation between the two concepts. With version 2.0 on the horizon, we have several examples of skills being granted to the player character in ways other than skill gems. This raises the question: Do we want to have separate pages to represent skill gems and the skills that they grant. Now that our item templating is much more robust, I think it could be greatly advantageous to incorporate skill gems into it. We could create pages for skill gems in the same manner as any item. —Vini (t|c) 22:14, 7 May 2015 (UTC)

That proposal makes sense to me. It would also get rid of unnecessary templates like sl that aren't too obvious for newer users. Another benefit would be the tooltips that would be useful when people are just after some quick info about a given skill. Iamacyborg (talk) 02:48, 8 May 2015 (UTC)

To me it seems obvious that this would be an improvement, but based on feedback from /r/pathofexile, people don't want this change. It could just be a matter of people not understanding how it would work. I am willing to spearhead this project; I just wanted to poll the community first before making sweeping changes. I think I need to hear from more people in favor of this change before proceeding with it though. —Vini (t|c) 04:08, 8 May 2015 (UTC)

I would be asking, what purpose does the gem page then have? Why would any user want to look at the page for a skill gem, as opposed to the page for the skill granted by the gem? I can see making dummy item pages for use with item templates, but I can't think of instances where I would want a link to go to that actual item page. --Qetuth-(talk) 08:31, 8 May 2015 (UTC)

On the other hand we already treat maps as a regular type of item, despite them also representing areas.--Qetuth-(talk) 08:38, 8 May 2015 (UTC)

You could just as easily ask why any user would want to look at the page for Ancient Greaves, and yet there are pages that link to it. Any time we want to refer to skill gems as items, we can link to the skill gem item page. Quest rewards are the first thing that comes to mind. Regarding maps, I do think it would be sensible to differentiate maps from map areas. I didn't want to muddle the discussion by bringing too many things into it, so I didn't mention it. But yes, I think we should do the same with maps and map areas. —Vini (t|c) 09:06, 8 May 2015 (UTC)

Almost all pages linking to base items are transclusions and some of the ones that aren't like quest rewards ideally should be. There is a good reason to have the page, but far less good reason for someone to actually be on the page (in the Greaves case, only really to check "is there a unique for this base?". But if the Ancient Greaves had some specific ability needing explanation, I'd expect it to be on that linked page, not on a separate "Ancient Greaves abilities" page. My point is that while being able to link/transclude gems the same way we do other items would be a plus, links that go to such a page and then do not have the skill details would just be annoying. I think we'd still be better off keeping all the skill info on the one page and allowing limited info from that to be transcluded in the same two ways ways as with other items (mouseover and tablerow). What is the disadvantage of this, besides the new ice skill page being a bit different (when it IS different in nature) ? Is there a problem with overall size of page for il/itemtable? --Qetuth-(talk) 12:56, 11 May 2015 (UTC)

Thanks for the thoughtful input, Qetuth. Perhaps I am slightly off-base in my approach. —Vini (t|c) 21:12, 11 May 2015 (UTC)

List of unique items sold by Forsaken Masters

For a little while I've been updating the list of uniques sold by each Forsaken Master. Are we convinced yet that every Forsaken Master sells the same list of uniques, and for the same price? In fact, it might be high time to just consolidate all the info about Forsaken Masters into a single page. TheMipchunk (talk) 21:52, 10 May 2015 (UTC)

I think it's a reasonable assumption at this point. —Vini (t|c) 22:07, 10 May 2015 (UTC)

Okay, here are the facts. Based on the compilation of all the uniques that have been reported on the wiki to be sold by Forsaken masters, there are 207 such uniques. There are (according to the wiki) 301 uniques, at least 44 of which are either league-only, race-reward-only, or Atziri-only (I may be forgetting some) and are therefore never expected to be sold by a master. This means that 207/257 uniques have been accounted for, over 80 percent. Given that some of the rarest uniques in the game are reported to be sold, it is possible that in fact every regularly droppable unique is purchasable from a master, and that the missing uniques are only because of the lack of self-reporting from players. If we accept this as the most likely explanation, then I would move to completely axe the lists of uniques sold from each Forsaken master page, instead just having a single sentence that says "At level 8, there's a chance that (master's name) can sell a unique item for between 5 and 10 chaos orbs. Any unique that can normally drop (other than from Atziri or challenge leagues) can be offered".

Furthermore, I would like to add the price of each unique as offered by a master to the main page for each unique item. This would be a little tedious but relatively easy as I have compiled most of the information already. I'll start doing some of these things pending some approval. TheMipchunk (talk) 21:01, 4 July 2015 (UTC)

For now, it might be best to move the table onto a "uniques sold by masters" page so it's all in one place for the people who currently look for the tables on the master pages. And only one page to modify then. Qetuth-(talk) 11:51, 5 July 2015 (UTC)

Maybe. But why would there need to be tables at all if there's a sentence just saying that they can sell any unique? TheMipchunk (talk) 08:53, 7 July 2015 (UTC)

Script Error in the Race Reward table

This table has a script error (Lua error: Internal error: The interpreter exited with status 152.) in every slot below Taryn's Shiver. I played with it a bit and did a few previews, but can't figure out what exactly is wrong. Am I missing something? Is this maybe an issue with the new behind the scenes stuff? ∞ The one, the only, the Moses

I am fairly certain this is because that page is hitting the maximum script execution time. The wiki software allows a single page to execute scripts for a maximum of seven seconds. Once that limit is reached, any additional script calls will throw errors. This is a different issue than a page exceeding the post-expand include limit, but the fix is the same: Include fewer item templates on the page. —Vini (t|c) 05:15, 14 May 2015 (UTC)

I'd suggest that the list of race rewards would be better on its own Race rewards page, or maybe on Races which is quite short on info, while the drop-restricted page should have a general description of alternate art items and a link to the race list - plus a table of the race rewards which are not just alternate art (ie, Demigods). --Qetuth-(talk) 09:11, 14 May 2015 (UTC)

Actually, the page with the alternate artwork list could just be called Alternate artwork items or something similar, which avoids the discussion of whether pvp events can be called races, and any future sources of alt art. --Qetuth-(talk) 09:16, 14 May 2015 (UTC)

Revisiting microtransactions

The MTX section of the wiki is very out of date and disorganised. Before doing a bunch of work there, I'd like to discuss changing the way we do it. Currently:

• Some types of mtx have a page for each mtx (eg Fiery Visage) using the item template/infobox, but with no actual useful info in the box.
• Most types of mtx have a page listing all mtx in that category (eg Pets) using Template:microtrans to construct the tables, but do not link back to the mtx pages.
• The item template is never transcluded. All it is doing is creating the infobox and putting all mtx in Category:Microtransaction features.
• The important info eg price, desc, youtube preview, is only currently found in the parameters of the tables on the type pages.
• I think the only place that link to mtx pages are Daily Deals and Rogue exile.

I propose we remove MTX from the item template and give it its own template which can then be used for all mtx (as not all exist as items) and then that template can be used as a table row for the mtx lists, and possibly the rogues/dailies tables. --Qetuth-(talk) 04:46, 23 June 2015 (UTC)

I'm fine with that, but I'll let someone else take charge of doing the templating for this project. Feel free to ask me questions; I just don't care to do it myself. —Vini (t|c) 17:57, 23 June 2015 (UTC)

Reworking quest rewards

With awakening around the corner, I think it may be time to completly rework how the quest rewards are done on the wiki. Currently, the information is simply put down in a ton of pages in an incosnsitent and very often out-dated fashion. Awakening pretty much redoes all of the rewards, so it is a good time to rework that.

In the past there were also timeouts when trying to edit Quest Rewards or issues on editing skill pages. Something that is desireable to be avoided.

Currently those are places where quest rewards are used (plus potentially more):

• Quest Rewards
• Quest_Reward_Gems
• quest pages
• skill pages

I think the main problem is that optmially a database should be used and select the info accoringly (think SQL-style). Basically, the rewards could be represented in a table with the given information:

• reward
• reward_type
• class
• difficulty
• quest
• display (for display values in case they can't be simply be parsed. I.e. think 4L item reward.

Optimally there should be one single list where the information can be selected out of, so editing in only one place is required. Since in wiki you can't really use SQL (not that I am aware of, unless with direct access to database), maybe this could be done with a lua module as well? I'm thinking of a lua table basically, then very basic programming to get the information out of and create a table. I think it may be a good idea to actually create two modules, one for the data that is intended to be edited and a 2nd one that basically handles the parsing and displaying of the data.

So on pages effectively use something like

{{#invoke: QuestReward | skill=Cleave }} or
 {{#invoke: QuestReward | quest=Enemy at the Gate}} or
 {{#invoke: QuestReward | difficulty=Normal | class=Scion}} 

to produce the results.

If a user wants to edit the rewards, he could edit Module:QuestRewardData. For editing the display style, there would be Module:QuestReward (but usually this doesn't need a lot of edits).

So do you guys thinks it's feasable and roboust enough to do it this way? Unfortunatly there will be some compute time obvioulsy to parse the list everytime, but I believe if it doesn't get edited the results get cached anyway. --OmegaK2 (talk) 12:51, 2 July 2015 (UTC)

It's definitely something we'd have to test to make sure it doesn't prevent page edits like the previous solution did. Would you be able to put something together as a test case? I definitely agree that the current quest reward system is shit, and needs improving. Iamacyborg (talk) 16:06, 2 July 2015 (UTC)

Since you alluded to Scribunto modules, I just want to point out that you wouldn't normally invoke a module function right inside of an article. There is a very specific reason this was done for the item templating that has to do with simplifying the pass-through parameters and adding extensibility in order to make templates like Template:Il be a lot less janky in their coding. The way you would normally use modules is by invoking them from a template, then transcluding that template inside of the article. —Vini (t|c) 20:09, 2 July 2015 (UTC)

If you haven't seen alredy, I put something up at Module:QuestReward. The data is located at Module:QuestReward/data and is currently simply exported from the game files (might upload the script later to github). The resulting page is here User:OmegaK2/test. Also has support for display on class and skill pages currently, which can be found here User:OmegaK2/test2

There is still some work required that needs to be done such as checking some of the arguments and wrapping it in a template. I've also considered whether to add another display style other then table, but I think tables are generally more pretty and readable. Though I'm not sure, in the past some pages used skill lists. --OmegaK2 (talk) 17:55, 5 July 2015 (UTC)

Nice work. I never thought of just using a giant array to store all of the data. I'm not sure how accessible it will be for people to edit though. —Vini (t|c) 22:49, 5 July 2015 (UTC)

Nice. As I had suggested in our other discussion, this database style of information storage seems like it could be useful to extend to other areas other than quest rewards. From what I can tell, the wiki supports running a script server-side to just retrieve data from these modules? That's relatively flexible for doing a variety of other tasks. TheMipchunk (talk) 00:43, 6 July 2015 (UTC)

Looks great, I think a list style could be useful but those tables are definitely a good place to start. How are you generating the initial data? Iamacyborg (talk) 15:00, 6 July 2015 (UTC)

Would Semantic Mediawiki help with any of this? Because we can get it if we need it. Iamacyborg (talk) 16:13, 6 July 2015 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ I've looked over the descriptions for a bit - it seems like a pretty good approch at least. It could be helpful with the editing the data, User:Vinifera7 has a pretty valid concern that editing a big table may not be the most user friendly way. I've formatted it so that it should be relatively easy to edit though in case any issues occur. If I read it correctly, it stores in SQL and also has lua bindings (or can be called from lua), which should fast. But I haven't used it, so I can't say for sure how well it would work. Autocollecting properties though templates for example seems like a pretty solid way to set this up.

Semantic MediaWiki seems to have some support for importing data (though extensions) if I read that correctly. Maybe that could help with auto-populating/updating pages, but I don't know for sure. Since you mentioned it, maybe you know? In essence it seems to do a lot of things I tried to do with that quest reward page (in a simpler manner).

But generally if it works like I think it does, it could help with the problems of those pesky hugeass templates (and more recently lua modules) and the custom logic behind that.

But anyway, generally there are still a few concerns:

• Info in centralized place versus information per single single pages
  • Keeping a big single page up to date is easier than keeping hundreds of pages up to date
  • Editing a big single page is harder/messier than editing many smaller pages

The update issue could be a non-issue though if data can be imported (i.e. as json or whatever) as described above.

There is another issue that came to light (again...), which doesn't quite depend the data: expanding templates and pages... in particular a few hundred or more is really damn slow. The lua script I wrote can sort and filter pretty fast. It spends almost all of it's runtime getting other pages and formatting it (and almost hits the 7 sec execution limit if displaying all current 1020 quest entires). I believe there should probably some other reworks that need to be done to the item templating if SMW or any other system was in place - possibly don't include the item pages, but generate the table from the data stored. And replace the hover functions with a JQuery that opens the page asyncronously (unless that is too slow, the curse wiki really seems to be slow a times).

Oh and lasty, the quest data was exported from (the latter two files for info about the item and the quest itself)

 contents.ggpk/Data/QuestRewards.dat 
                    BaseItemTypes.dat
                    Quest.dat

As I mentioned I'll post the scripts publicy soon (tm), but I'd rather have it in an useable state (=non messy) before that. --OmegaK2 (talk) 00:26, 7 July 2015 (UTC)

I'll check with the Gamepedia dev team who'll be able to better inform me on what SMW is really capable of. It's not something I've personally run before, but I know there are a few GP wikis that run it. Will get info back asap. Iamacyborg (talk) 02:26, 7 July 2015 (UTC)

If nobody minds, I'll go ahead and edit the skill/quests pages with the awakening rewards tommorow or today, considering it's due to release in about two days. I've already done so for cases which linked to the original Template:QuestReward so it doesn't break it.

In addition, there are also vendor quest rewards with the new addon. I think it makes most sense to integrate them into the same module, though with a different data section and template. The main difference seem to be that those vendor rewards are not limited by the difficulty and are simply given after completion of the quest. Plus their availability at certain NPCs with specific costs. I think that suffices to display them in their own table. I could also edit that into, since I don't plan on changing the syntax much, even if the lua coding isn't done yet (i.e. Template:VendorQuestReward would simply return nothing for the time being). --OmegaK2 (talk) 16:18, 8 July 2015 (UTC)

I've added messages for certain situations as opposed to displaying an empty table. I think it's pretty much ready now for deployment. Examples on my userpage User:OmegaK2/test2 and also one live example Added Cold Damage. Planning to remove the fmbox as soon awakening goes live

What do you guys think the vendor quest reward section should be called? I've thought either would do, but need to deceide on one before mass editing pages:

* Vendor reward

* Vendor quest reward

--OmegaK2 (talk) 19:07, 8 July 2015 (UTC)

Looking good! I prefer "Vendor reward" but they're both fine. --Climmels aka SirProblematique (talk) 20:30, 8 July 2015 (UTC)

Great work. I love the way it looks on skill pages, and especially love the way keeping it up to date should be easier or automated now. The big tables on the quest pages themselves look very cluttered though. I would have liked it to use tickboxes for skill rewards too but with the mix of skills and eq, and a large variety of skills in some quests, that might not work out. What is the reason for the big info bars above every table? Can they be removed? --Qetuth-(talk) 00:00, 9 July 2015 (UTC)

I would like to point out that it is slightly incorrect to call it a "vendor quest reward". Not all NPCs who give quest rewards are vendors. Maramoa, for example. Edit: Never mind, I think I see what you were trying to accomplish here. TheMipchunk (talk) 00:34, 9 July 2015 (UTC)

reshuffling of bestiary category structure.

The category structure of the bestiary seems odd to me in that every monster, every monster type, many summary or monster info pages, is automatically added to the root directory. Regular unique monsters don't have their own directory, but bosses (a somewhat arbitrary distinction that has been debated before) do, and then special types of unique monsters are a subcateogry of this. Also, it is odd that we are calling this section of the wiki the bestiary when that term is never used in game or by GGG that I am aware of. Does this bestiary directory which includes everything serve a purpose? With more than 200 items hence more than one page it isn't as convenient to search as just using google or the wiki search. Finally the main place other than this master directory that monsters can be found is in the monsters by act, when several monsters appear in more than one act.

I propose we make Category:Monsters the root category and only have in it summary pages such as Monsters and List of unique monsters as well as possibly some other lists of monsters such as making the blank Act 1 Monsters etc useful in some way. The bestiary directory that contains everything could still be kept as a subcategory, but should not be the main. I'm torn on whether categories like act 1 monsters should be kept - the whole guest monster system kind of ruins it a bit.

The subcategories of monsters would be:

• Monster mechanics
• Monster skills

• Normal monsters
• Beyond monsters
• Corrupted monsters

• Unique monsters

• Act bosses
• Map bosses

etc

• Monster types
• Monsters by Type

• Spiders etc

• Bestiary (if kept)
• Monsters by act (if kept)

• Act 1 monsters etc

So a monster should primarily be in a type category (eg blackguard) and a rarity/status category (eg map boss). Both of these could be handled automatically if we ever finally get monster pages to be infoboxes for table transclusion like we do items and passives.

Note: Parts of this idea have been covered and not really gone anywhere at Template_talk:Navbox_Bestiary, Talk:Bestiary, and I think several other pages I can't recall now. Generally those discussions end in agreement the current system is a bit weird then get forgotten. --Qetuth-(talk) 07:01, 7 July 2015 (UTC)

These changes sound good to me. I'm in favour of just removing the Monsters by act categories, as they have lost most of its usefulness. I do think the Bestiary category should be kept as a list of all monsters, disregarding rarity and whatnot.--Climmels aka SirProblematique (talk) 09:12, 7 July 2015 (UTC)

New Archive

I think it's time to clear this page out and create a new archive, anyone have a problem with that? I'll keep the currently active sections, I just want to make sure there aren't too many things here that could cause confusion. Iamacyborg (talk) 13:58, 9 July 2015 (UTC)

Yeah, that would be nice, it has become very cluttered. --OmegaK2 (talk) 00:13, 10 July 2015 (UTC)

Let's wipe everything, but migrate the Awakening-to-do list to the new community portal. We'll be working on stuff related to that list for at least a few weeks to come. TheMipchunk (talk) 00:26, 10 July 2015 (UTC)

Yes, most of the recent discussions boil down to stuff to go on a to do list, so it's really the conversation that needs to be kept open. --Qetuth-(talk) 01:54, 10 July 2015 (UTC)