Path of Exile Wiki

Please consider helping keep the wiki up to date. Check the to-do list of updates needed for version 3.14.0.

Game data exports will becoming later as the technical changes in addition to regular changes take some more time.

READ MORE

Path of Exile Wiki
Advertisement

Archive 4 | Archive 5 | Archive 6

The Awakening to-do list

Here's a partial to-do list. Feel free to add new things or notify when you're working on something.

  • Area progression changes (levels and structure) in the first three acts (Qetuth is working on this)
  • New leech mechanics
  • Reduced Mana and Enlighten changes
  • Gem vendors
  • "Shotgunning" changes
  • Arctic Armour
  • New Maraketh base weapons need to be added (Domokingu is adding these as well as updating any other bases that need it.)
  • New skill gems and skill gem balance changes (Status: TheMipchunk is working on this. Most active skill gems have been updated, support gems still need work. Estimated completion in a few weeks.)
  • Passives (especially Keystones) need updating (Domokingu has updated the notables and will be working on the regular passive skills.)
  • 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.)
  • Update map upgrade table
  • Map mod changes
  • New map levels
  • Legacy items
  • Changes to base items
  • Changes to flasks
  • Item affixes changes
  • Map-only drops and particulary Item drop restrictions have been changed

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) 08:47, 9 July 2015 (UTC)

I can take on the task of rewriting the leech article. Although I won't be starting on it right away. —Vini (t|c) 12:35, 9 July 2015 (UTC)
I've updated the points from character to keystones, major changes to positioning for MoM and Vaal Pact, and the changes to Vaal Pact and Eldritch Battery functionality, currently working on div cards and respective items —lutem 13:58, 9 July 2015 (UTC)
Sorry folks, I wanted to do a thorough overhaul of the leech article, but I overestimated the time I would have to work on wiki stuff. I haven't even had much time for playing PoE lately. —Vini (t|c) 12:02, 14 August 2015 (UTC)
I'll be going through items/gems/zones/mobs updating their Version History as soon as the patch hits. Iamacyborg (talk) 13:56, 9 July 2015 (UTC)
I'm working on skill gems. I don't expect to do all of the articles but I am prioritizing new skills gems and skill gems that have received major changes in the patch. Other skills with only minor changes have low priority. TheMipchunk (talk) 02:37, 10 July 2015 (UTC)
I realized, that on some old gems (don't know how many) the xp values are still the old ones. If someone wants to do it... ;-) --Lord joshi (talk)
I plan on creating/updating pages with the new 2.0 uniques, in my free time. I'm also uploading the official art images (offline version of the images hosted on poe's cdn servers) for each of them - Haaxxx (talk) 21:06, 11 July 2015 (UTC)
I'm going through the notable passives and updating them as needed, then moving on to the regular passives. - Domokingu (talk) 21:12, 11 July 2015 (UTC)
I was working on item affix 2.0 when i got a message from Vini, i guess i did a mess so later i'll take a deep look to the wiki help and continue, tnx to Vini for the advice. Fucrem (talk) 19:24, 16 July 2015 (UTC)
You didn't necessarily do anything wrong. I just gave you a welcome message on your talk page with some basic tips for wiki editing to help you get started. Thanks all, no big deal :) —Vini (t|c) 20:18, 16 July 2015 (UTC)
It appears that some existing uniques have been changed as well (specifically, my Blackgleam differs from what is listed on the wiki page). Not sure how exactly to handle this as a single sample doesn't show the stat ranges, but I guess I'll just leave the information I have on the talk page of the unique in question for now. Alacia (talk) 21:22, 17 July 2015 (UTC)
I am updating the act pages. In the less direct acts (2 and 3) the progression tables we had were kind of hard to read. I tested giving borders to the arrow cells and find it much clearer, please compare old revision to new revision and tell me what you think. I think a background colour would be even better, but before I add that, I was thinking it'd be a good idea across all those tables to have the style saved in one place rather than copy and pasted everywhere. Before I do that, I'd like to know whether you think that kind of thing is better off in common.css or in a code inserting template like the version history tables use. --Qetuth-(talk) 10:05, 22 July 2015 (UTC)
I am planning on adding the new monsters that have been added in act 4, as well as updating the old monster pages to reflect their appearance in new areas. However, I am having trouble finding classifications of monsters: names are easy to find in-game, but some monsters on the wiki seem to be classed by some kind of system that I can't figure out. For example, on the Monsters page, Birdman refers to avian retches, and Spiker refers to porcupine goliaths. Are these just arbitrary names given on the wiki just for a point of reference? Or are they referred to in the game files as such? SpamNinja (talk) 19:51, 10 August 2015 (UTC)
The internal files do have a system for the different varieties of monsters such as skeleton or zombie, as well as a classification structure above that for things like undead, animal, humanoid. Most but not all of the wiki categorization comes from that system - Spiker for example I think was the type name from the internal files for porcupine goliath-like creatures/bosses, which shared common resources such as a spiker AI or sound effects. Other type names we couldn't find or make sense of from the files and so made up arbitrarily or based on community terminology/ggg announcements. We never did finish unraveling and wikifying the full system discussed at Monster category, which is used for example by map mods. I had planned to try and figure out how the act 4 stuff fits in but won't get to that any time soon, so feel free to try and figure it out yourself or just leave that info out to be added later. --Qetuth-(talk) 23:38, 10 August 2015 (UTC)
I'll be updating the skill progression pages soon (i.e. in a few days probably). I've written a program that will extract the info from the game files - I'm currently fixing up a few loose ends and working on automating editing the wiki pages. The only thing that is still somewhat experimental are the stat requirements, but for the test samples I've used I've got it working. Means also editing pages that already have been edited, as most gems have a progression up to level 30 in the files. --OmegaK2 (talk) 16:58, 15 August 2015 (UTC)
Nice, this means I can stop updating the skill gem stats? =) TheMipchunk (talk) 19:53, 15 August 2015 (UTC)
It might make sense to update the info box though if there were any other changes. Anyway I've done it for the support gems now, it would be nice if someone could check on the stat requirements and tell me if there are any inaccuracies, before I proceed editing the normal skill gems and vaal skills --OmegaK2 (talk) 15:07, 17 August 2015 (UTC)
Updated the progression on all pages. If there are issues with something please drop me a message or post here.
Known issue: The skill gems don't exactly include the stats for summoned minions or totems (other then the minion level and the relative increases), it's something I'll be looking at next. --OmegaK2 (talk) 18:36, 18 August 2015 (UTC)
I'm currently traveling so I can only glance at your skill gem changes on my tiny mobile screen, but firstly the experience values are wrong; you've output the cumulative values rather than the per level values. Of course this can be easily fixed. The second thing, and really the only thing I have a real issue with, is that your script has undone a variety of custom formatting and data that I spent a good amount of time working on on a per-page basis (including minion stats, as you've mentioned already, as well as labeling effects, rounding numbers to match in-game gem display, and a variety of other small things). This is an understandable side effect of using a script but I'm not really keen on redoing all that again. I don't mean to sound harsh; this is a big step forward for keeping the wiki updated. TheMipchunk (talk) 08:13, 19 August 2015 (UTC)
The problem is with the custom formatting I don't really think there is a feasible way of detecting it (programatically). The number of columns given in the header may wary, the order may vary, the meaning of the columns and the wording of the columns; additionaly when people edit it manually there may be spelling mistakes and other mistakes that might cause it to be undetectedable (-- and inconsistency, I had to update a few pages manually prior to updating them since they didn't use the gem progression section properly). So unfortunately the only working way is just to replace the whole gem progression.
I've been considering adding a list of abbreviations programatically, but that involves some work again, it's essetially re-implementing the the entire number of translation strings from the ggg files that are relevant to skill gems which is not a small metric. The way the translation works it would probably also be easier to do it based off the resulting translation instead of the identifers they use internally (since you probably don't know: intenerally there might be multiple identifiers for a single translation - i.e. that's how you get "added x-y damage" for example, it's reffered to by minimum_added_damage and maximum_added_damage for example)
I've updated the script already with the fix to experience and support for abbreviations. But before I'll update the pages in a second round minions and the actual abbr strings need to be done. I'll actually be keeping the total experience (in addition) - it has always annoyed me that it was missing from the tables previously.
I'll be focusing on the minion gems as it's more work then simply adding abbrevations (I've got some mentions from chuansing that will help), but if anyone wants to do them please send me a pull request - I've put them in a huge dict in the gem parser for the relevant strings:
https://github.com/OmegaK2/PyPoE/blob/dev/PyPoE/cli/exporter/wiki/parsers/gems.py
--OmegaK2 (talk) 11:40, 19 August 2015 (UTC)
I guess I feel like the fastest way for me to restore some of the work I've done would actually be to revert rather than edit, and it seems like that defeats the purpose of the hard work you've done. I think the ideal solution would be for the script to accept some custom parameters, such as rounding scheme, label abbreviations. The script would only automate making numbers, with formatting chosen by the script runner. Full automation seems more complicated anyways. For example, there should be support to generate the columns in a different order. I have consistently tried to have the order of the columns match the order in which the relevant stats appear in-game on the gem itself. I also have always used the long dash for damage ranges. I should also remark that I was already using the game data to make the skill progression, but I only used it to get the numbers, not to make a table automatically, precisely because of the formatting concerns. TheMipchunk (talk) 16:21, 19 August 2015 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── To be honest, I don't see your point here:

  • reverting is unnecessary; just rerunning the export once will fix all the issues found and incooperate suggestions made
  • the numbers in the game files are NOT what you see in many cases; in addition to what I explained earlier, translations strings already specify how to format/handle the values already (see translations.py if you want to know what's going on)
    • If there are discrepancies I need to know where these are to look at them
  • rounding scheme, label abbreiviations, label order as parameters would actually complicate the code more much then it is already and actually open more potential for reduced consistency
    • for abbreviations in particular, it's easier to simply define them in the script file which will also gurantee they are consistent within the wiki; in other words, it will ensure "Adds x-y Fire Damage" is always "Fire Damage" and not something like "Fire", "Fire Damage", "Fire added", etc (you get the idea)
    • as for the order, for the stats that are not manually retrieved but based on the stat_ids, it should be exactly the same order the game uses (at least for the skills I looked at)
    • for stats that are not shown in game (like minion damage etc), the same applies again - order will be consistent

Otherwise, I forgot about the –, but it's in the code now. But that's a wiki-only thing, the game just uses -. --OmegaK2 (talk) 17:37, 19 August 2015 (UTC)

All right, I'm confident you'll resolve any issues. Another one I noticed was that some base damage values were listed as modifiers rather than absolutes (see Whirling blades). Also some values should include percentage signs or units. I can look over it more carefully once I'm back from travel. I spent a lot of the past few months on stylistic formatting so I guess I would prefer it was somehow preserved. Even if it isn't, I would just like to make sure that if I make changes again now (eg restoring the labels), that these changes are not repeatedly reverted upon running the script again. As for rounding, this is purely stylistic. I prefer that values be rounded in the same way as displayed in-game. This appears to be on a per-stat basis which was why I was doing it manually. TheMipchunk (talk) 20:57, 19 August 2015 (UTC)
Well, you can look over the abbrevations and let me know if you think which ones need adjusting.
I took the base damage value right from the files (where they are actutally in 10000ths), but yeah it's no problem to add 100 (/10000) so looks like the base damage. I'll also rename it to reflect that...
I didn't originally add a percentage sign since they are technically incorrect if they're also in the header (% * % = 1/100 * 1/100 = 1/10000), but it might be good for readability still, I can certainly add that.
Rounding seems to be bit of a problem though, not sure what people think it's best. I thought rounding to at least two significant digits is good. Could also do an approch of rounding to two digits if they're non-zero on all columns otherwise use the least siginifcant digit (like integers if all ints, 0.x if only up to 0.x values, 0.xx if up to 0.xx values etc) --OmegaK2 (talk) 01:10, 20 August 2015 (UTC)


Quite a few skill gems that are hybrid STR+INT have their stat reqiurements reversed (ie summon flame golem.) --RicochetSaw (talk) 04:58 25 August 25 2015 (UTC)
Thanks! Fixed that in the script.
On a side note, if no further things come up, I'll be updating the pages again tonight or tommorow --OmegaK2 (talk) 16:29, 25 August 2015 (UTC)
I have done many legacy versions of unique items. I went through the patch notes and i think i've got all of them (even the undocumented change for Kongor's Undying Rage). What still needs to be done is recalculating the damage/AS/crit chance of many unqiue weapons, where the base types have been changed. But that has nothing to do with legacy versions. I have also updated base items of several base types, but not all of them. Just check the base types and if one item has been updated, all of this base type have been updated. --Lord joshi (talk)
I have also completely renewed the Maintaining Low Life site. May not be very important for most of us and is also not in the list yet, but is something that comes exactly from many 2.0.0 changes. --Lord joshi (talk)

Launch Options page

I think we need one with a list of launch options and explanation what they do. TheFrz (talk) 17:55, 12 July 2015 (UTC)

Cool. Make one. —Vini (t|c) 18:50, 12 July 2015 (UTC)
Done, but I think I need some help with it --TheFrz (talk) 20:01, 12 July 2015 (UTC)
Looks good to me, what do you need help with? Iamacyborg (talk) 00:14, 21 July 2015 (UTC)

Item filter list ("moderated")

I see people adding their own item filters to the current page. I've had the thought for a while, but I believe we should separate item filters into their own page.

In addition, we should make it somewhat moderated - I've kinda seen it on other wikis, but often things can have potential to end up in edit wars - (people removing other people's filter, people thinking filter X is better then Y and remove it, and so on, filters becoming outdated / dead links etc). The second thing is we probably want stucture and some basic information about filters. If we have a list with 100 filters called XXXs Item filter or whatever, it won't be really helpful to people other then being a collection of filters. Instead, I suggest something like this (ALL required if someone wants to add their filter):

  • Author and a means of contacting the author, e.x. reddit / GGG forums account / email / etc
  • Name of the filter
  • Link to where the filter is published
  • Link to the filter to a place that makes it easy to see updates (e.x. github)
  • an overview of what the filter does, possibly this could be split into a check box type of thing for generic features
    • leveling suitable
    • endgame suitable
    • hiding items
    • modifying certain aspects of the default
      • colour
      • borders
      • font sizes

Possibly also some other optional information such as:

  • ingame screenshots/examples


Besides that, I think inactive or outright broken filters (i.e. author does not respond/update it anymore, in particular if people find out issues) can then be moved into their on section on the page, only keeping the maintained ones there. As for the moderation, basically just oversee that people follow the rules, remind they to follow them if they don't and act if needed (i.e. delete entries, or in the worst case of edit wars protect the page for a bit).

Anyway, first I'd like to hear what other people here think, in particular the wiki sysops, whether you think we should do this at all and maintain a policy regarding it. In the next step I'd post the info on reddit/GGG Forums for user feedback. --OmegaK2 (talk) 03:35, 18 July 2015 (UTC)

I need to understand what the issue is, exactly. There are already two pages (at least?) pertaining to loot filters. One of them is a general overview and missing some critical information. The other is a more comprehensive guide. It is my opinion that the information presented in the Item filter guide article should be merged into the Item filter article. Despite the fact that it's lacking certain information, Item filter is the main article. I don't see why we would need more than one article. —Vini (t|c) 04:03, 18 July 2015 (UTC)
My post was basically about expanding section Item filter#Popular item filters into it's own, moderated page (for reasons mentioned above). I didn't put it on the talk page because it also involves moderation and a page-specific editing policy, which is a bit larger scope then just chaging that page.
Regarding the guide vs the main page, I agree that so much duplicate content is not OK (strangely enough the user who created it links to a thread where some people had the wiki had "none", even though it evidently did for over a month). Some of the item filter guide contents are a bit over the scope or inaccurate as well. For example, I believe colours should get their own wiki page (Colours used in Path of Exile for example), since it's something that basically unrelated to the item filter itself and sees uses otherwhere (for example application programmers might want to look at it to match poe's colour scheme!). Same goes for a list of item classes (I mean, we don't really want to list every single item that's in poe there either -).
Then there is also the question of how much information should remain on the page, I think a more concise page is best, mostly because users aren't greeted by a giant wall of text when they're only there to read about what they do and how to use one. I.e. the information on how to create one could very well go into something like Item filter creation
That I would have usually discussed on the talk page of the filter though. --OmegaK2 (talk) 04:42, 18 July 2015 (UTC)
While it looks like a good idea there is a bunch of questions about how it would look like, who is going to moderate it and so on. I don't say I am against this idea but I can't imagine it at least right now.
On the other hand there is a problem Vini has mentioned few times already that there are 2 articles about the same stuff. Also Item filter guide has been written in the first person style and it's rather a forum post than a wiki page. In my opinion the whole new article should be written based of 2 existing ones. —TheFrz (talk) 16:38, 18 July 2015 (UTC)
The two pages have never worked out the way I pictured when I was thinking a guide page and a base page would be a good pair. To be a good guide, the guide needs most of the basic info the base page should have. I was originally thinking a step by step instructions page and a definition page would be quite different.
On the list of filters, I agree it is not that useful right now - each link is to a forum post, which then links to an external site for the code, and has differing amounts of explanation and advertising. Even most of the forum posts don't actually give a very good explanation for what the aim of the filter is and what kind of player it is for. We could of course have our own summaries to go with the links, but I don't know about keeping that maintained. Also note I think only two of the filter links we have were posted by the author.
On a related issue, how do you all feel about some standard filters being hosted on the wiki rather than a forum or upload site? I am thinking more of base files with some very common changes for other people to edit rather than start their own from scratch, so not files that should need updating (outside of expansion level patches). A "defaults" code which individually sets everything to default appearance might also be good to provide. But also, if we are going to have a "submission" process, we could use that to choose a handful of the best to host here if the author wanted it. --Qetuth-(talk) 23:38, 18 July 2015 (UTC)
I spoke with Iamacyborg and he mentioned something about having the wiki's own loot filter. That could be an option. —Vini (t|c) 01:58, 19 July 2015 (UTC)
Yeah, I think it could be a fun project. Iamacyborg (talk) 00:15, 21 July 2015 (UTC)
Well, the wiki having it's own filter and having examples are two different things. It would need a maintenance as well. Maybe this could be something like a "community edition" filter? --OmegaK2 (talk) 05:52, 21 July 2015 (UTC)
I made a mockup on my userpage of what I had in mind basically User:OmegaK2/test --OmegaK2 (talk) 05:52, 21 July 2015 (UTC)
That looks good to me. In terms of the user submissions process, how do we see that working? We could use something like a Google Form to notify admins. How would we approve filters for inclusion on the page? Iamacyborg (talk) 15:34, 21 July 2015 (UTC)
I'd generally think leaving this in-wiki is good. It's not a problem to put the page on the user watchlist and use the patrol feature to approve of the changes. I am usually for lettings users edit it as long they follow the rules there shouldn't be much intervention required. The only time I see when it needs to go into protected mode is when people start to vandalize it or start edit wars, then I'd use the talk page for user submissions. --OmegaK2 (talk) 15:55, 21 July 2015 (UTC)
If nobody minds, I'll post to reddit and see what people think and then deploy that User:OmegaK2/test page. It seems the item filter page is already getting what I anticipated, with ziggy and hellcat editing and removing filters. Pinging Qetuth, Vinifera7, Iamacyborg :) --OmegaK2 (talk) 14:07, 25 July 2015 (UTC)
Sounds good to me. --Qetuth-(talk) 08:47, 26 July 2015 (UTC)
That looks good to me too. The edit war yesterday was completely unnecessary, we'll have to lock down pages and hand out temp bans if people continue dicking around. Iamacyborg (talk) 22:23, 26 July 2015 (UTC)

Move to remove redundant boss videos on map pages

I would like to propose that we remove the redundant boss videos on map pages. If these boss videos should go anywhere on the wiki, they should go on the articles of the unique monsters themselves. The map walkthrough videos can stay on the map articles. This change should be uncontroversial. —Vini (t|c) 19:26, 21 July 2015 (UTC)

I think most people are likely to be looking for that info on the Map page itself, but your reasoning makes sense. I would think that a map walkthrough video that also happens to cover the boss encounter would be appropriate on the map page though. Iamacyborg (talk) 19:33, 21 July 2015 (UTC)
I agree - map walkthroughs on map video, boss specific on monster page once it exits. However, one thing I would really like to see is all map pages have text info on boss location - own section of the map or not, minions, does the room seal, etc. I added the info to some maps a while back but I really don't play maps often these days --Qetuth-(talk) 03:44, 22 July 2015 (UTC)

Master Page change request

I would like to change a few things about the master pages, but I'm not entirely sure if this is the correct area to post this, so I apologize in advance if I am doing something wrong.

The decorations sections seem to have no ordering whatsoever. I tried to figure out if there was a reasoning behind the entry order but could not figure it out. If there is no order, may I change it either to alphabetical, list by cost, list by level unlocked, or list by view from purchase window top>bottom left>right? I was planning on adding all missing decoration entries, but if I could do it in some semblance of an order that would be much easier.

Secondly, I believe the unique item list that is still on all master pages is not necessary as it seems that all masters sell any droppable unique. Can we remove the unique item list to remove clutter and unnecessary information from these pages? Or are we waiting for a direct GGG confirmation before removing these lists? SpamNinja (talk)

I'm working on the unique item list thing. I'm compiling the prices for all the uniques first. These prices will then be listed on each unique's page directly. About the decorations, I would personally organize it by cost, but anything you think would make it look nicer is probably fine. TheMipchunk (talk) 10:35, 30 July 2015 (UTC)
When posting on the talk page, please do not forget to sign your posts with ~~~~.
The decorations are orderable by clicking on the table columns; I assume you're talking about the initial order, I'd do it by level unlocked (and then alphabetical) since it's easier to check if anything is missing per level up.
For the unique list, it might make sense to move it to it's own page and combine all the lists into one for now. It does look like they're all selling the same uniques, but the list isn't complete and there is whole lot of uniques that aren't sold be the same masters. I'd only remove it and say they sall all uniques if it's absolutly certain it's actually the case. --OmegaK2 (talk) 11:30, 30 July 2015 (UTC)
Agreed on having a separate page with the unique list and taking it off the master pages. I think we decided to do that somewhere in another conversation but never actually did so? For the decorations, I think the original intention of at least some editors was purchase window order, but we didn't always stick to that. By required level might be good, or even by type/size of decoration in different tables. I personally think decorations should also all be moved to their own page, as I think the wiki deco list would be more useful telling players which master to go to to get the deco they want, than what decos they can get from a specific master. --Qetuth-(talk) 11:40, 30 July 2015 (UTC)
Actually that's a pretty solid idea. I think however we really need to start taking screenshots of the decorations as well, simnply having the name is good to locate something if you know what it is. But if you don't screenshots would really be helpful. Anyway, I created a stub for the unique list: List_of_unique_items_sold_by_masters. Unless someone wants to edit it all manually, I'll try to create a program that merges the lists from the other pages later --OmegaK2 (talk) 12:08, 30 July 2015 (UTC)
I do not think that having a list is useful in this case. What users want to know is whether a specific unique can be found. It is not clear that all uniques can be sold, but what is clear in my mind is that all masters can sell a given unique, if it can be sold at all. My solution is that a short section on each unique page will mention whether or not it can be sold by a Master, and for how much. Regardless of whether we will keep a list page up, I will be implementing this addition once I get some extra time. TheMipchunk (talk) 19:13, 30 July 2015 (UTC)
I could be wrong, but I thought that any unique that can currently drop without restrictions can be sold by a master. I like the separate page for the master uniques, I suppose that will just have to be updated manually by people that have level 8 masters until we get a clear answer. Should we add edits directly to that page or still to the individual master pages? On the topic of the hideout decorations, should we create a Decorations page, and link to that under the Hideout page and each individual master? I don't know if I would even have the authority to create a random page like that. Also, if I wanted to start uploading pictures of decorations, is there a guideline for the quality? The thumbnail given by the masters would be extremely simple to screenshot and upload, but they are rather small and not very representative of what the actual decorations look like. On another topic, is there any place that I can learn tips for the formatting used here? I have been deterred in the past from posting anything because I couldn't find any real rules or guidelines on what should or should not be posted. Also, if this is not the place to have this discussion, what is the correct place? SpamNinja (talk) 23:46, 30 July 2015 (UTC)
That is the leading theory, but nobody knows for sure. Currently about 80% of all non-drop-restricted uniques have been publicly reported to be sold by a master. As for wiki permissions, there's nothing stopping you from creating a new page. Anything that would streamline the presentation of information seems worthwhile. TheMipchunk (talk) 01:05, 31 July 2015 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Feel free to create a decorations page. Formatting guidelines written as a guide we do not have but it would basically match any such guide written for wikipedia, but it's often easier to copy and paste as much as you can from other similar pages. And hit preview a lot when trying to get those darn tables looking right. For the individual decorations and their images, it depends whether we want to have an individual page for each decoration like we do for items and mtx so they can be transcluded. I think this might be overkill, but it would mean we were being consistent how we do things across the wiki, and makes it easier to eventually give each decoration its own screenshot. I think for the existing passive/item icons, they were extracted from the game files or the website somehow? That would be a better place to get the shop image than a screenshot. See Drillneck for example, in the infobox we have the high quality imported image, then elsewhere on the page we have screenshots of game use. --Qetuth-(talk) 04:50, 31 July 2015 (UTC)

All the pages that I've edited so far have been through a lot of copy-pasting of similar pages, so I was just wondering if there was a simpler way. I am unfamiliar with datamining, so I wouldn't be able to add high quality game files images. Are you suggesting to not upload low-quality screenshots then? A page for each individual decoration does seem like overkill, but it would be difficult to display multiple variations of every single decoration on a single page. I'm not entirely sure what a good solution to that would be. SpamNinja (talk) 06:51, 31 July 2015 (UTC)
The images added from the game files are usually 2D Art images that are easy to convert and extract. For decorations that means the inventory icons, not the 3D models - these would require reading GGGs model format, and I don't think anyone has made a program for that yet (so screenshots it is). Search for VisualGGPK2 if you want to extract files, though I use a progam I wrote myself since I found VisualGGPK2 a bit clunky to use.
As for I don't know, having decorations have their own page doesn't seem too bad generally, since it means we can use templating (which includes support for variations), but I dont know about hitting transclusion limits again if a lot of these are transcluded into the same page. Besides it's probably something that could be added to the item template (since they're basically just items anyway). --OmegaK2 (talk) 12:01, 31 July 2015 (UTC)

Templating Pages

I think most pages should really be using a template. We are already doing this to some extend with things like the item info boxes, but not enitrely. Basically this applies to anything that has largely repeated content (so any kind of item (=skills, decorations, cards, items, uniques, currency, etc) , quests [done this for quests already], etc).

The point is that most pages are setup in a very similar fashion, e.g. most skill pages go like this essentially:

  • infobox
  • skill functions and description
  • gem progression
  • quest rewards
  • vendor rewards
  • version history
  • navbox

Basically it's no problem to just set that up in a template.

The only downside I can see is that basically editing sections will not work (as those sections would be generated on the template, i.e. people would be promoted to edit the template, so naturally you disable it), so people would have to edit the page basically.

The other is that it adds a bit of inflexibility in terms of extra sections, while that is kind of the point to streamline the pages I'd think it would be best to simply leave an "extra" variable for placing them (i.e. so when people add extra stuff, it doesn't appear in "random" places, i.e. below or above the normal stuff, in middle of version history or so), but always in the same place. Generally, however there is no need to write the same things over and over in a ton of pages - and more importantly, since the format isn't fixed, users may simply forget certain sections - I've noticed this when I was going though adding quest/vendor rewards a while ago, sometimes pages are missing sections entirely or order them entirely differently. It would help sure the pages always look the same roughly and have the information they should have.

It also could make future generation of content easier. For example, if there was an update that largely changed how something works it could simply be added to the template; i.e. people will see that the information is missing and should be able to fill it in. Additionaly with the variables, if we for example deceided it would be nice to have new categories, it would no longer be required to add them to each individual page, but simply have them autogenerated by the templates. Or if we had a central place we get the informaiton from it would also make changes to the individual pages rather trivial (one change in the template vs. editing hundreds of item pages)

But anyway, the main reason still stays the repetition of things. By no means it is decent to have people to copy the exact same sentences from every page into the other page, and then just ajust it. It can as well be filled in by a template just as easily. --OmegaK2 (talk) 12:58, 31 July 2015 (UTC)

The inflexibility for non-standard pages, and inability to edit sections, and the added barrier to new editors, are pretty major imo. Even as an experienced editor I have trouble sometimes tracing imported or generated data or finding fixes to a page can't be made because the error is coming from something a template does automatically. So getting everything on the page completely inside one template might be more trouble than it

's worth. However I think there are a few more things that could be simplified with more templating, and more things our current templates could be doing. Doing gem progression tables the way we do version history tables, for example. I wonder if there is a way to have the version number recorded in the gem progression so things like out of date templates can happen automatically? Gem categories could also be done automatically from the keywords.

One of the big things that could be fixed though is the number of places data has to be (in almost but not quite identical form) in both the infobox and the text of a page. I would really like to see a way to fix that, and maybe having the page text in a template to has the answer there. --Qetuth-(talk) 05:40, 2 August 2015 (UTC)
Well, people can still edit sections. It's just that the [Edit] will be missing next to the section, and instead the page is edited (i.e. variable changed). I should probably write up an example to show it would work/look.
I believe we can probably condense gem progression even further; I believe the gem progression is technically the same for gems that share the same base level (except some bugged outliers possibly), so that could be filled in by default based on the max gem level and gem base level. Same with the stat requirements.
We can put a version number in there and update the template then warning that the page is out of date or so, but the question is when we want to do that. If we do it for every minor update all the gems would be out of date all the time; I mean technically we could do it for specific gems, but simply adding a note on the specific page is better. And we don't get huge updates like awakening every often that overhaul pretty much all the gems. I don't think it's needed.
And regarding the duplicate info, that's pretty much exactly what I had in mind. For those sentences "x is a y and can be found at z" those can just be generated automatically. I'd just leave some fields open for people to enter text manually inside the template (i.e. to fill in triva, item mechanics or similar stuff). --OmegaK2 (talk) 00:20, 6 August 2015 (UTC)

Bandwidth-Heavy Ads

I've recently noticed that if I leave the Wiki open in the browser, it sucks up my internet bandwidth constantly loading advertisements. Is this a recent change in Gamepedia? The problem goes away if I use an ad-blocker (which I would prefer not to do in order to support the site), so it appears clear to me that the ads loading is the problem. TheMipchunk (talk) 06:53, 5 August 2015 (UTC)

Nothing's changed as far as I know but an ad provider could be slipping in bad ads. Could you keep an eye open on which ads are causing the problems and send them my way, I'll bring it up to the adops team who'll be able to blacklist them. There's also this if you want to submit reports yourself: http://support.curse.com/hc/en-us/articles/204270395-Reporting-Bad-Advertisements Iamacyborg (talk) 14:17, 5 August 2015 (UTC)

Damage per second calculations (Weapon lists etc.)

Hi, not sure if this is the right place to post this since I'm fairly new here/to wikis in general, but I think the Weapon DPS calculations that are used on the weapon list pages (not sure if they appear anywhere else) - e.g.: Sword - could use a change, though I don't know how to do that. They currently factor in the weapon base critical strike chance and use the base (150%) critical strike multiplier. That doesn't seem very useful to me though, so I'd like to exclude those and only calculate dps off average damage * attacks per second.

Reasoning: 1. For an RT character, this screws up sorting by DPS, as he wouldn't care about the base crit chance but would have to do the dps calculations himself. 2. A crit character would value an increase in critical strike chance much more highly, as he would have increased critical strike chance from tree and gear, and more importantly an increased crit multiplier as well, so that sorting doesn't help him much either. 3. There are probably builds who don't use either RT nor have crit scaling, but I'd think those are the minority. For these people the dps would be accurate. 4. Both PoE.Trade and https://www.pathofexile.com/item-data/weapon use my suggested way of calculation.

This is a minor Issue (values are at most 3.5% too big), but still something I'd like to see changed (opinions?) since it seems unnecessary to me and I stumbled upon it trying to figure out what the best base weapon for my crit reave build would be to craft from/look out for. —The preceding unsigned comment was added by Lame4Fame (talkcontribs) 14:25, 6 August 2015‎ (UTC)

This seems pretty reasonable. Any objections to this change? —Vini (t|c) 19:13, 6 August 2015 (UTC)

List/Overview of path of exile related applications & websites

Do we currently have such a thing? Searched a bit but haven't found it on the wiki.

If there is no existing list or so to start off I'll go ahead and create a page for websites (List of Path of Exile related websites) and applicaitons (List of Path of Exile related applications) each.

People generally seem to be interted in what kind of tools and utilities there are for path of exile. How else are people supposed (aside from asking) if we don't list things like VisualGGPK, Procurement/Acquisition, PoEBuilder and other cool apps a lot of people use? --OmegaK2 (c | t) 05:39, 28 August 2015 (UTC)

Sounds like a good idea. This post on the subreddit already lists a good number of tools (maybe a bit outdated) and might be a good place to start. --Climmels aka SirProblematique (talk) 08:00, 28 August 2015 (UTC)

Something broke the item tables

The item tables are broken right now (see the tables at Helmet for an example. They have an extra column saying "strength", "dexterity" or "intelligence" based on what is required, and the values of armor, evasion and/or energy shield are being pushed to the side. This happens with the lists of unique items as well. Any idea of what caused this? Testante (talk) 22:31, 29 August 2015 (UTC)

fixed (edit: it may take a bit for the changes to affect the pages due to caching, if you hit edit and preview, it should be correct) --OmegaK2 (t|c) 22:53, 29 August 2015 (UTC)
Thanks! :) Testante (talk) 02:42, 31 August 2015 (UTC)

Info: recently installed extensions

I've got in touch with the curse staff and had some extensions installed here on the wiki.

  1. SyntaxHighlight
  2. Labeled Section Transclusion
  3. Math
  4. Semantic Mediawiki

A few use cases:

  1. Used to highlight source code, i.e. useful for documenting the scribunto modules
  2. Allows to create sections which you can then transclude. This should be helpful if we have pages with a lot of text which could also be useful on another page without having to resort to creating templates or so.
  3. Math allows the use of latex syntax, so formulas can be formatted properly on the wiki Example
  4. SMW is probably the largest and about the best thing we can want on this wiki. It can help us dynamically query pages and insert page content into a database basically, which should help combating content-duplication and the generation of xyz lists; there is however a lot of work involved and existing templates need to be reworked to include this behavior (more about this in an extra section)

--OmegaK2 (t|c) 18:41, 31 August 2015 (UTC)

I've been trying to read up on SMW. I still have no idea how it works. —Vini (t|c) 18:46, 31 August 2015 (UTC)
Yeah, I've found the documenation difficult to understand. Basically you can properties to a page which will populated into a database with [[My property::My value]] or with the set parser function. Then you can query those with the ask parser function like {{{#ask: [[Category:Forsaken_Masters_NPCs]] }}
There is a lot more you can do however then those simple examples, the queries are complex and kind of similar to SQL I think --OmegaK2 (t|c) 18:57, 31 August 2015 (UTC)
I think we're replicating a lot of it's functionality already with our templates, which while complicated are a pretty elegant solution. I need to look at what other wikis are doing with SMW though, see where we can improve. Iamacyborg (talk) 19:30, 31 August 2015 (UTC)
Pretty much any page that is more or less based of the game data can benefit greatly from SMW. In particular the items & gems - yeah, we're doíng similar things already, but working around the limitations heavily. I've considered looking at the smaller / less important bits first (i.e. like the versioning) before tackling the huge templates. The largest benefit lies in that there is only a single page that will need updating and not multiple pages. To give an example, we have plenty skill lists and all of those could be autopopulated (sorry for all the links, just to illustrate the problem) --OmegaK2 (t|c) 19:48, 31 August 2015 (UTC)
SMW sounds useful. For example, would it be possible to automatically populate List of removed passive skills with any passives that have the "Removed passive skills" category? That would really open a lot of options. --Climmels aka SirProblematique (talk) 21:37, 31 August 2015 (UTC)
Yes. However prior to that the properties would have to be set on the pages, otherwise you'd just have a list of pages in that category (with no information about the version, what the skill looks like, etc). --OmegaK2 (t|c) 12:43, 1 September 2015 (UTC)
I've changed the way the version pages are created to show off what SMW can do a bit:
Version_history uses the queries extensively
Template:Version now is based on lua and automatically sets the properties on each version page. One of the neat things, it also queries the previous and next version for their dates, so dates only have to be entered once now
So what do we get? Each time a new version is added, it will automatically show up as latest version on the front page, it will be automatically linked from the previous (and next) version pages, and it will also show up in the version history page on it's own. And with some work it's possible to do things like this for the whole wiki :) --OmegaK2 (t|c) 12:43, 1 September 2015 (UTC)
That's rad as fuck, dude! I am really excited to see what else we can do with SMW. I removed the current version SMW query on Version history, since that was only there to be included on the front page. I put the query on the front page directly. —Vini (t|c) 15:55, 1 September 2015 (UTC)
I've been doing a bunch of SMW stuff on another site just to wrap my head around it. Definitely a ton of cool stuff possible. What are we looking to do with it here at the moment? Iamacyborg (talk) 15:27, 24 March 2016 (UTC)
Looking at how we're building Version History, is the current template overly complex? We could build everything the LUA module is doing directly into the Version template. The benefit being that it'd be much easier for others to work with in the future. Iamacyborg (talk) 15:37, 24 March 2016 (UTC)
I think OmegaK2 was thinking about redoing the item module using SMW. A similar thing could be done with passives. In fact it would be easier, since passives are much less complex than items. —Vini (t|c) 16:07, 24 March 2016 (UTC)
Makes sense. Obviously a pretty big overhaul but would make things much simpler in the future - particularly with the item lists which wouldn't require manual updates after patches. I'm going to play around with the Version template and see if I can simplify it over the weekend, I don't think there's any real reason to be using lua in it. This page shows a quick example of how I'm using SMW on another wiki. Iamacyborg (talk) 16:27, 24 March 2016 (UTC)
I don't see a point of moving a lua template into a normal template, esp. since it works just fine - the time would be better spend on doing something like vini suggested i.e. the passive skills. Lua is faster and has more capabilities in general, it leaves option to extend things more easily if the need arises. Not to mention I also think lua templates are much more readable since you don't have the same convoluted syntax and can place line breaks where you want.
Honestly I think we should be sticking to lua templates in every case unless the template is very simple.
Lastly I'm indeed reworking the item module. Not sure whether I am entirely happy with the results yet, I've run into an unexpected problem - displaying things is fast, but setting a lot SMW stuff slows the down the wiki page loading a lot. I also want to specifically keep this possible to be automated by scripts as well as user editing so the maintenance part (look into the wiki rework section) becomes easier. Gem stuff is somewhat okay-ish (examples User:OmegaK2/test2 User:OmegaK2/test3) --OmegaK2 (t|c) 02:03, 25 March 2016 (UTC)
The page loading issue might be one we can resolve through caching. Iamacyborg (talk) 09:57, 25 March 2016 (UTC)

Long-term Project: "Path of Exile Wiki 2.0" - bringing the wiki up to shape

First off, this a general draft and idea at this point. If it's something most people here who contribute can agree on, this should get it's own page to discuss it; for now it's something to discuss and get some general input on and agree on some ways to proceed.

The general idea is to tackle a few problems with the current 'state' of the wiki:

  1. Lack of guidelines/rules
  2. Content duplication
  3. out-of-date pages & updating issues
  4. Lack of editors
  5. Little ways of internal wiki communication

1. Lack of guidelines/rules

We barely have any in place. While I think it's good to not over-regulate something, I think it's time to agree on specific sets of rules and guidelines. Guidelines in general should take the priority, as they also help editors to see how things are done in the wiki. And it helps for consistency accross the wiki.

Some examples where I think it should be acceptable:

  • how to name pages (& files, templates)
  • order layout for specific types of pages (I still think we should use a general template for these pages)
  • style guidelines for regular pages
  • style guidelines for lua modules

This is a short-term task.

Draft: Path_of_Exile_Wiki:Manual_of_Style

2. Content duplication

Since we now have Semantic Mediawiki installed, we should be looking at eliminating all duplicate content. This will be a very long-term and extensive task requiring changes to templates, modules and pages up to the point of reworking major parts of individual pages.

First steps to take here are

  • Identifying what is optimal to set as property
  • Reworking the templates / modules to automatically verify the arguments and set the properties
  • updating all affected pages to the new templates (if required)
  • finding the pages with duplicated content (i.e. lists, navboxes etc) and updating them with SMW queries

Draft is up: Path_of_Exile_Wiki:Semantic_Mediawiki_rework

3. out-of-date pages & updating issues

When the content duplication has been tackled, part of this problem is solved. Only updates to a single page are required. However, part of the problem remains that is updating single pages with information. For many pages however this could be semi-automated - a compelling amount of information can be found in the .dat files.

I've mentioned it before, but I've been working on toolkit for GGG's file formats and as part of it I'm looking to create updating bots/scripts for the individual pages. This isn't entirely an in-wiki project, but it would help a lot in general with updating the wiki. Meaning that having the pages up to date after any kind of update would be a rather trivial task (i.e. just running a script) which most users should be able to do. In some ways I believe this could be considered similar to what poedb did, except it's only on a semi-automated basis.

However this is a very time intensive task to create all those scripts in the first place and also verify they are working correctly. In particular because it's not just outputting a few lines, but also formatting the information properly; overriding user-input data has also to be carefully considered when it makes sense and when it doesn't. This is something where someone with programming experience could help, but it is a very long-term task overall.

4. Lack of editors

The other large problem the wiki is facing is the lack of editors in general. Honestly, I'm not entirely sure where the problem here is, it might make sense to make a survey or ask people why they don't contribute (well, apart from the 90% that would basically not share information to other players immediately according to a reddit poll :/).

However some things that I think that could help are the guidelines as mentioned above, but also generally providing a link and resource collection (in the sidebar possibly) to get people started; i.e. links to the basic wiki syntax (we don't need to reinvent the wheel - it's all on wikipedia in a pretty good fashion :) ). There could be some other things that could be done to get people to help, i.e. reaching out to some of the popular streamers and have them do mini guide or endorse the wiki for instance.

This is something that can be done in a short to mid term.

5. Little ways of internal wiki communication

I believe that we should communicate a bit more outside of the wiki itself. I mean talk pages are all fine and good, but I think it would be really nice to have a go to place to discuss things or to just help people out. In particular this goes for the other sysops here, so some things could be talked though swiftly.

I've wanted to remove the IRC page, but I've considered that it might be a good idea to start using IRC for instance. There are lot of web clients these days and it would provide a rather easy platform, the only thing left to do is to get people to actually *use* it. I've looked at the channel's user list and it seems like User:Iamacyborg has the access rights to the channel.

--OmegaK2 (t|c) 12:31, 2 September 2015 (UTC)

I like this idea, and you're right on a number of these things.
1. Style guidelines are something I've thought of in the past, but had a little too much inertia my end to actually start running with. I definitely think setting up some basic page templates would be useful, and by template I don't mean Wiki templates, I just mean a barebones page that can simply be copied into a new page whenever we need to create a new skill/item/etc. These templates could be available from a centralised page which also contains general page creation guidelines to make the process easier for everyone.
2. Agree with everything here.
3. I don't have any working knowledge of this kind of stuff, but I could use my position at Curse to get you in contact with other wiki admins who are doing this kind of thing of that might help?
4. There are a few things we could do here, such as opening up wiki editing to people who don't have an account, and creating site notices inviting people to participate. Alongside the steps taken to provide better documentation this might be a great way to get a few more editors.
5. IRC works, but the issue there, as far as I'm concerned is that it's a whole other thing that I have to log into and check every day. Something like Skype, Curse Voice or Steam chat would be preferable as they're all things I imagine a few of us already have installed. I'm not sure how others feel, but I don't think IRC is the best or easiest solution.
Iamacyborg (talk) 14:47, 2 September 2015 (UTC)
It would be nice to have some format guidelines (although I would be cautious to not make it so rigid that a new user would be expected to read three style guidelines before updating an article). Testante (talk) 13:42, 5 September 2015 (UTC)
I've updated the OP with some links to the drafts.
1. This actually possible to with templates (or general pages) with substitution ({[#subst: pagename}}). We could create pages for that purpose
3. Not sure curse staff can help with that really. This mostly off wiki work for the wiki (and requires knowledge of the Path of Exile, Python basically). I might want to reach out and reddit and see whether I can find anyone to help, otherwise I guess I'll be alone with that.
5. Yeah, it might be best to wait for more replies. I added vini and you on steam, let's see how that goes. Though I guess we have to wait for the other admins to reply ... --OmegaK2 (t|c) 21:03, 5 September 2015 (UTC)
1. I think most of us copy an existing page to create new monsters/areas/whatever - The problem has come when there isn't consistency between existing pages, or when things like template documentation haven't kept up with actual template usage. It would be good to have some reference documents, whether they be blank page stubs or a manual of style. If newer/flyby editors don't read the style guide, that's not a huge problem - just the existence of such a document makes it a lot easier for other editors to come by later and clean up the style.
2/3. I'm really interested in how this goes and would love to be involved but just don't have a lot of time at the moment. I'm guessing the bottleneck is probably getting the data imported into wiki pages in a useable format - once it is there, many editors can potentially check the accuracy or create pages transcluding and formatting the data.
4. The areas that get the most attention from lots of irregular editors have been when things are made easy for them to just do a little bit based on what they see in game - such as with the data on the skill gem tables. Moving to more automation might make it harder for non-involved editors to get started. Editing instructions would help there, but another thing that could help as a stepping stone to get one off editors to stick around might be a wiki-wide "suggested changes" page, or clearer instructions on how to suggest a change on a talk page?
5. I don't have steam, and would you believe the main method of communication with my guild members is ICQ? We're old-school. If the IRC room is going to be actively used I might look into it, but I'm a bigger fan of asynchronous communication. I think something that held the monster revamp up for a long time was no centralized discussion place for it - There are individual talk pages which get little attention, and then there is this community portal which has a lot going on including sometimes multiple large project discussions and is harder to keep track of. Does anyone think project talk/community pages for each major section such as monsters, areas, items, passives etc would be helpful? --Qetuth-(talk) 00:12, 8 September 2015 (UTC)

Availability next couple weeks

Hey, I'm planning a 4000+ mile move over the next couple weeks so I won't have a great deal of time to devote to the wiki, I will be checking back daily though! Iamacyborg (talk) 16:21, 16 September 2015 (UTC)

Side Navigation Bar

The Shop Tool link under the Fan Portal section in the left side navigation bar links to the old project site on google code, can an admin update it to point to https://github.com/Stickymaddness/Procurement/ also another shop tool called Acquisition (https://github.com/xyzz/acquisition) is pretty popular now, should we link to that project as well? Crimsonfalconer (talk) 09:47, 22 October 2015 (UTC)

A Question Regarding Unique Items

Hello, PoE Community! I received a support ticket from a PoE user that I think you'll be able to answer better than I can. To summarize, the Unique item page states that there are 493 unique items as for version 2.1.1. However, when the user counted all the unique items from the different categories (Accessories, Armour, Weapons, Flasks, Jewels, and Maps) they only counted 478. They'd like to know where the missing 15 items are! Any help with this matter would be greatly appreciated. BriannaMCR (talk) 17:28, 20 January 2016 (UTC)

Has the user actually counted all the uniques on this wiki? And not taken that number straight from https://www.pathofexile.com/forum/view-thread/1477864 ? If so, that may very well be the correct number. I believe that number is manually maintained which can lead to errors over time and as you may have noticed it's difficult to confirm. --Illviljan (talk) 21:04, 20 January 2016 (UTC)
There are 15 unique strongboxes (4 uniques, 3 obas, 8 grandmasters) so that could be the issue. Personally, I counted 481 items which have pages within the unique items category tree, so 496 with the boxes. --Qetuth-(talk) 21:58, 20 January 2016 (UTC)
Okay, I've done a proper survey. There were 21 uniques not showing up in their categories, which has been fixed. I also didn't count Song of the Sirens in my initial count. However, I did count 13 beta-only jewels. So that takes my total on the wiki to 490 (+ 13 jewels + 15 boxes). The forum post linked which claims 478 is missing Whakawairua Tuahu and the 12 on List of Descent: Champions unique items from its list of items which means they should be 13 below my count at 477 - I didn't check their count, just compared cat by cat. They also have 3 of the demigods items in the list twice (I assume they only counted once), and are still using the old name for Meginord's Vise. --Qetuth-(talk) 23:35, 20 January 2016 (UTC)

Lua item module and hybrid flasks

So after some time spent reading up on templating and transclusion to fix the formatting errors on the hybrid flask and related lists and places such as flask main page, and realizing it wasn't the template as such that was the issue but how the parameter calls always returned life+duration or mana+duration instead of each separately, which led me to this Module:Item thingmajing which I'm competent enough to track down the offending section in but if I were to be so brazen as to actually edit myself would a) take hours of dusting off coding skills I haven't used in nearly two decades and b) undoubtedly break something somewhere else. So yeah, assuming it doesn't work this way for any other reason than convenience I reckon it'd be ideal being able to call duration separately when you want to stick a bunch of flasks in (on) an item table. It'll temporarily break the formatting of all recovery flask lists but I'll fix that, and any related issues I can find or be pointed towards. twitticles (talk) 02:30, 21 January 2016 (UTC)

Character start items & progression

Where do you guys think it's appropinate to post the character starting setup? We currently have 5 different released variants of this, the default starts (with nothing), 2 PvP variants (lv28 blank and lv28 equipped), and now 2 race variants for act 2 and 3 starts respectively.

I can see multiple pages where this could belong:

  • character page
  • for each individual class on their class page respectively
  • split up into serveral pages, i.e. one for races, one for pvp, and the default starts on the character page
  • all in one page which then could be linked to from the various other pages

I'm currently mostly in favor of putting it into a single page. I don't know how much this information will change in the future, but I think it may be a good idea to move away from the internal representation of the data, as the table it produces is pretty hard to read. I think optional would be making some kind of virtual character inventory where we can "place" the pieces/info into, but that would be quite the thing to realize in the wiki and I'm not really a webdesigner. Perhaps User:Vinifera7 has a better idea there. --OmegaK2 (t|c) 13:19, 22 January 2016 (UTC)

When I go looking for some race information I typically do that on the respective races' such as Descent: Champions and I'd expect to find infmration about specific and alternate starting environments there as well. Doesn't make much sense to have it all bundled on the character page as it doesn't really apply to most new players, but a note on that page would of course be prudent. To keep things neat and not add unnecessary maintanenance down the road (without really knowing much about the behind-the-scenes stuff) maybe a single page and then pull the relevant data off of that to transclude (or some other method using alien languages and arcane gestures I have yet to learn about) it to each relevant page as well? twitticles (talk) 17:31, 22 January 2016 (UTC)

Detailed vs ingame mod displaystyle

For the mods I currently use the ingame display style and use the full text as hover effect. I am thinking of reversing this, since I think it's more useful to look at a glance.

This is how it currently looks:

Gains Endurance Charges


I'm thinking of reversing it to:

50% chance to gain an Endurance Charge on Hit

I think the reversed format is actually better. Shows more useful information on the first glance. Especially useful for pages like List of monster suffix mods. So what does the community think? --OmegaK2 (t|c) 00:50, 2 February 2016 (UTC)

I'm undecided, but something to consider: Lines like "Evasive" and "Gains Endurance Charges" are the lines players are familiar with and might search for. If anything I think it is the suffix name which is the least important of the 3. --Qetuth-(talk) 07:50, 2 February 2016 (UTC)

WOHOO

Congrats! In PoE offical site menu in "Game" have link to our community! :3 Thanks all! —The preceding unsigned comment was added by ExileWhoDieByZombieInStart1Act (talkcontribs) 13:43, 14 February 2016 (UTC)

Did they add that recently? If so, it's well overdue. —Vini (t|c) 17:53, 14 February 2016 (UTC)
Probably, has to do with this endorsement they're talking about here: http://www.gamepedia.com/news/994-exclusive-path-of-exile-cosmetic-arctic-crown-to --Illviljan (talk) 18:23, 14 February 2016 (UTC)
Wait, does this mean we have to do things in a serious fashion now? twitticles (talk) 18:34, 14 February 2016 (UTC)
Absolutely not. Iamacyborg (talk) 09:09, 15 February 2016 (UTC)

Finding all these awesome things meant to make editing a smooth and joyous experience

Might just be me but I'm having the darndest time actually locating things like templates, scripts and alot of other magic thingamajings people use around here. Like templates, they're not linked anywhere under the "Tools" section in the navigation sidebar, if I find a linked template I can work my way up to Category:Template and then chance my way downwards again through some subsection and maybe find what I'm looking for, or something I wasn't looking for but seems fun to use somewhere sometime.

Or I can just copy an already filled in template from a similar page and just replace the relevant data, but that seems like a really lousy way of doing things as it increases the chances of me missing some info that wasn't used on the page I copied from but would be used on the page I'm creating/editing, and I certainly don't learn much doing it that way, as opposed to checking the templace doc page which admittedly can be very sparse but at least has some information that can be decoded, and also I have a penchant for long sentences so I'll end this one soon, about now.

Same with scripts, the one I got at the tip of my toungue right now is adding a reference, which I know I looked up at the gamepedia wiki wiki but unless my memory failed me it turned out to be different here so I just copied an existing one and manually edited it which felt really dirty. Maybe that one's actually no different from the standard gamepedia one but there are things, like scripts, which are only used here or used in another form here which I haven't been able to find listed anywhere, such as a "This is a convenient list of magic words we use at the PoE wiki and a brief description of how they work and how to use them". Is there such a list for templates that's in a more handy format than the category pages? —The preceding unsigned comment was added by Twitticles (talkcontribs) 04:29, 4 March 2016 (UTC)

Please renember to sign comments with ~~~~
There is no good overview at the moment - having some general guide lines (and probably updating the community portal) sounds a good idea. There is discussion about that here on the talk page in some of the sections above. For the time being you'll continue to look at other pages and see how things are done or search for things manually.
But as with everything, it needs to be created in the first place and that's where everyone can help. Be it writing up such an overview of the templates/categories or improving the documentation on template pages. --OmegaK2 (t|c) 06:46, 4 March 2016 (UTC)
Yeah some sort of beginner -> intermediate guides/expanding help page/"Oh so you want to do more than just fix tyops?" stuff sounds like something I could get started on once the Ascendancy rush slows down. twitticles (talk) 07:55, 4 March 2016 (UTC)
If you weren't aware, when you click "Edit" on a page, all of the templates used on that page are listed for you. —Vini (t|c) 06:53, 4 March 2016 (UTC)
Ah I hadn't noticed the template list, that's quite helpful :) twitticles (talk) 07:55, 4 March 2016 (UTC)
We definitely should try provide some sort of resource with example placeholder pages, and a list of all noteworthy templates. Iamacyborg (talk) 10:44, 4 March 2016 (UTC)
That would be a beautiful thing, and certainly make it easier for new editors. There seems to be a steady influx of new people but I would presume few are willing to scavenge for information when they don't find much guidance, so they correct a typo, add some data, get frustrated with the lack of help and don't bother to log in again. The same conclusion about lack of editors was reached under the "wiki 2.0" paragraph earlier on this page. twitticles (talk) 17:57, 4 March 2016 (UTC)

navbox appearance

Some of our larger navboxes (eg Template:Navbox Skills or Template:Navbox Bestiary) would be a lot easier to read with cell borders separating the different lists, or some other way to distinguish the lists from each other. Can we add something like that to the navbox style? --Qetuth-(talk) 05:51, 8 March 2016 (UTC)

Yep, they've gotten pretty monstrous. Maybe we could even break them down by the type of skill they are? Iamacyborg (talk) 09:11, 8 March 2016 (UTC)

Updating the skills with item template v2

The fruits of reworking the item template, something I've wanted to do a while ago, but I think it's good enough to update the pages with it.

Generally the template does take a bit since setting the properties take some seconds, however the advantage is that building skills lists with smw and other lists should be relatively easy to do.

I've also prepared the bot/backend so I can generate those lists reliably in the future, though I still have to do some work to keep the radius intact.

There will be some changes:

  • the 2d art will be named <item_name>_inventory_icon.png - this is for consistency and so it's immediately visible what the file is for. Previously we had just the item name for a lot of things like screenshots, inventory icons and other purposes
  • <item_name>_skill_screenshot.jpg - simiarily, this will be used for the skill screenshot
  • skill progression is now part of the item template (but also separately available as Template:Skill for non-item skills); this will exclude minion progression specifically (the best way I believe is to create a table specifically for the minion skills)
  • the formatting of progression is now handled by Template:Skill progression which takes arguments to format the progression accordingly. I've done this automatically in my bot before, but it's better to keep this in wiki so people can correct or update it as needed
  • the item template includes a few extra options

There are some caveats:

  • quality as per data will be very hacky. Quality is set per 1000ths, and the translation strings might be sightly wonky/wierd when downscaled. I've had to use tricks to get this to work to display for 1% quantity, since floating point stats do not exist (like 0.5% damage would be infact 0% damage - which would be rather confusing as 1% quality stat :P)
  • the templates will be a bit larger and pretty verbose about the stats, but should be still properly editable by hand if the need arises

On another note, I think this should also be used opportunity to reconsider the way skills are categorized. This should be based on the gem tags (and the item class).

I think we should consider removing the distinction between "xxx skills" and "xxx supports" in the categories, and just categorize them by their tags. It's probably just a much better idea to create "List of xxx" pages that match those conditions instead of having complicated categories. Instead we would have a "list of cold skills" which could then have a distinction between spells, attacks, support gems for example.

I've also changed the gem tags to link against <tag_name>_(gem tag). I believe we should just create pages for the tags and then list relevant other pages, skills and other content there. The reason for this distiction is that I felt the way what words actually link against is pretty random, like "AoE" or "Projectile" will take you to an overview with some mechanical information, but things like "Bow" take you to the item page. So it probably makes sense to draw the distinction between the general mechanics involving some of the keywords and the keyword it self.

Relevant pages:

If you have feed back or thoughts please reply before this change is applied to the several hundred skill pages.

Things on the todo:

  • auto-align the item box from Template:Item to the right

--OmegaK2 (t|c) 18:16, 2 April 2016 (UTC)

Very exciting! Once we're done with converting all of the item pages over to the new templating, let's not forget to copy (or merge) Module:Item2 over to Module:Item so that we have contiguous edit history. —Vini (t|c) 21:05, 2 April 2016 (UTC)
Would you mind showing a example for a support gem? One thing I think the old template lacked is support for the shorthand Id that support gems have. For example Arrogance SupportArrogance SupportAura, Support
Icon: B
Level: (1-20)
Cost & Reservation Multiplier: (220-201)%
Cooldown Time: 0.00 sec
Requires Level 31Supports any skill with a reservation.Per 1% Quality:1Superior2Anomalous3DivergentSupported Skills have 0.25% increased Aura effectSupported Skills have 0.1% reduced Life ReservationSupported Skills deal 0.5% increased DamageSupported Skills have (10-19)% increased Aura effect
Supported Skills Reserve Life instead of Mana
This is a Support Gem. It does not grant a bonus to your character, but to skills in sockets connected to it. Place into an item socket connected to a socket containing the Active Skill Gem you wish to augment. Right click to remove from a socket.
has B. My idea is that the user only needs to input the B and then the module would figure out the primary attribute requirement and the corresponding background color.
What is intelligence_percent for? Isn't level1_intelligence_requirement enough to define that?--Illviljan (talk) 20:53, 3 April 2016 (UTC)
I've made an example out of Multistrike. Added the support gem letter support, knew I forgot something.
Technically gems don't even have a per level requirement, it's all derived from the percentage. I actually left the level requirement int/str/dex there because the reverse engineered code I came up with to get the level requirement isn't 100% correct for all cases. Just so people can correct it (and people have an easier time correcting those small mistakes then fixing a formula) --OmegaK2 (t|c) 22:02, 3 April 2016 (UTC)

As addendum:

So are there any other suggestions or ideas?

I could also use some help going through the skill pages, since this has to be done manually for now.

This is what needs to be done

  1. Grab http://omegak2.net/poe/Skills.zip and unzip it
  2. Locate pages that don't use the new template, i.e. with Special:WhatLinksHere/Template:GemLevelTable
  3. Replace the gem infobox template with the item export from the zip file, make sure these are specified if appropriate since they're not added automatically:
    1. radius = if the skill had a radius specified before
    2. has_percentage_mana_cost = True if the mana cost of the skill is a percentage like most auras
    3. has_reservation_mana_cost = True if the mana cost of the skill is reserved rather then used like on auras, heralds, etc
  4. Move the skill icons, inventory icons and skill screenshots to the appropriate new location
  5. Remove the gem tag categories from the page (they're added by the template now)
  6. Replace the gem progression template with Template:Skill progression; for this to work the semantic properties have to exist, so you need to save the page first
  7. Repeat at step 2

Also do add not skills that do not exist but happen to be in the export. They are a bunch of other skills that are not released yet and may never be released. Don't add that information.

Once the skill items have been updated the navboxes, skill lists, categories etc can be taken care of. --OmegaK2 (t|c) 21:21, 5 April 2016 (UTC)

Just chiming in to say that this change is great, you're doing some really good stuff for the community! Iamacyborg (talk) 19:50, 6 April 2016 (UTC)

With the help of Illviljan the skills were finally updated!

I've switched the Template:Sl to use the new item links, some old syntax isn't supported anymore - the pages with those broken links are automatically added to this category:

Other then fixing the links, the next thing to do would be updating the other templates, item lists and so on with smw queries and data. --OmegaK2 (t|c) 21:57, 7 April 2016 (UTC)

Is it possible to make Template:Sl not case-sensitive? It looks like it causes the error mostly. — Freeeeez aka TheFrz – 22:40, 7 April 2016 (UTC)
Not really. SMW strings are case sensitive, the only way to do it would be to store item names as lower case for the lookups; not sure I want to do that --OmegaK2 (t|c) 18:18, 12 April 2016 (UTC)

Naming of negated SMW properties

I want to add negated/reversed properties for semantic media wiki for the cases where this is possible and makes sense. Basically, they are a list of "not" entries or the difference between the set of the given values and all possible values.

However, I want to find a good common naming scheme for those, ideally:

  • It must retain the original property name in it's name, so it's easy to guess the negated one
  • It should not be too noisy (i.e. not a very long sentence or description)
  • It should retain human readability

To avoid confusion, an example of what I mean

  • The acceptable values are {A, B, C, D, E}
  • The property is Property:Has MyProperty
  • If Property:Has MyProperty is set to {A, C, E}, then Property:Has MyReverseProperty will be {B, D}

Here are some ideas based on Property:Has gem tag and what bothered me about it:

  1. Property:Has gem tag (not) - seems unnatural
  2. Property:Has gem tag (reversed) - seems unnatural
  3. Property:Has reverse gem tag - feels like a bit misleading to what it actually does
  4. Property:Has gem tag difference - not sure people are familiar with the mathematical terms for sets; I feel like this might imply something else
  5. Property:Does not have gem tag - I feel it gets rather noisy/long. May also be confused with a boolean, however I've already used something along of Propety:Has no gem tags for boolean values

Anyone has some ideas or preferences? Otherwise I'll just go with a random one of the above.


Also what do people think about renaming stats to plural if they are intended to contain multiple values? I think it makes sense - I feel it may be the best to better draw the distinction on the usage - like use Property:Has stat with a single value on the mod pages, but on the skill pages I just have been dumping all values into the properties (due to some restrictions). I was thinking it might make sense to rename these to Property:Has stats; similarly for Property:Has gem tag; renaming it to Property:Has gem tags --OmegaK2 (t|c) 00:02, 15 June 2016 (UTC)

The word should replace "Has" and preferably imply the opposite. The ones I like, in order, initially are
  1. Has no gem tag
  2. Not gem tag
  3. No gem tag
  4. Lack gem tag
I don't think using both plural and singular is a good idea, for example Empower: Has gem tag, and Wild Strike: Has gem tags. I can imagine times when you have a long list of #ask queries and then you need to copy/paste it all after the OR to include the missing values. But I can understand the need to distinguish between single and multiple values. IF there is a risk that that the property CAN have multiple values just add in the -s. Even though it may not always be right it implies that you may need to approach it differently, and that method should work for both a single value and multiple values anyway.

--Illviljan (talk) 07:04, 15 June 2016 (UTC)

Yeah the plural form would be used consistently for places where things can commonly have multiple tags. It would be the plural for all gems.
The problem with "Has no gem tag" is that I've this as boolean before in particular Property:Has_no_item_class_restriction and I think they more imply that there are no tags at all rather then not having specific ones --OmegaK2 (t|c) 15:36, 15 June 2016 (UTC)
Agreed, I thought about an irrelevant example. Then we go one step down then to "Not gem tag". The grammar may not be that beautiful, but I think it'll do the job since NOT is well established what it means.--Illviljan (talk) 16:31, 15 June 2016 (UTC)
I start to think it may actually best to go with one of my earlier examples like Property:Has gem tags difference or Property:Has reversed gem tags, I think it's fairly clear in what it does and doesn't sound as awkward. --OmegaK2 (t|c) 23:52, 17 June 2016 (UTC)

Right Ad sidebar blocks content at narrower resolutions

The wiki works fine at wider resolutions such as 1900. At narrower resolutions, in my case 1080, the right "info/ad" section makes much of the content hidden from view. Take the maps page as an example. Is there some way to make it less intrusive at lower widths or do we need to make some modification to much of the wiki content? MegaGrubby (talk) 10:32, 15 June 2016 (UTC)

There would need to be changes made to the layout of the page to be more accommodating of lower resolutions. One quick fix would be to wrap the wider sections with divs that cause overflowing elements to scroll horizontally. Also, if you do edit this (or any other Gamepedia) wiki regularly, you will gain enough wikipoints to qualify for Gamepedia Pro which causes the right siderail to disappear completely — Game widow (talk) 20:37, 15 June 2016 (UTC)
It would be much better if the "ad area" was either across the top of the page or a static option that would allow the content to flow around it. It is way too obtrusive in its current form. Any way to contact them about having it go across the top or making it static? Blocking content does not seem to be a good solution for anyone....--MegaGrubby (talk) 16 June 2016
You have contacted "them" by posting here. Unfortunately there is very little chance that will change, but i will absolutely pass along your comments. I should add, as well, that below 1000px width, the siderail disappears — Game widow (talk) 13:22, 17 June 2016 (UTC)

Improving the Path of Exile Wiki

I wanted to let everyone know about some improvements we're working on for the wiki.

  • We’re now only displaying gaming-related content in the siderail - no show spoilers or weird celebrity news.
  • The siderail will now hide on browsers sized approximately 1350 px or smaller. (It was previously set to hide at 1050 px or smaller.)
  • We've reduced some of the wiki padding to make more room for content.
  • We're working with ad providers to resolve issues with ads crashing browsers.

There are a few tables around the wiki that still aren't displaying great for users with lower resolutions - and the display issues aren't from the siderail. We're working with the admins, wiki managers, and dev team to make these tables display correctly for all users.

Another reminder - ads that auto-play sound are 100% not allowed. If you come across one, please grab the URL it links to and email it to community@gamepedia.com. We'll contact our ad ops team and have the ad removed from our system.

There's been a lot of feedback recently about the wiki, and I wanted to let everyone know we're listening. I'm glad that you're vocal, I'm glad that you care, and I'm glad that you're pushing us to improve the wiki to the best of our ability. Please feel free to reach out anytime with questions, concerns, or ideas. Thanks, all! Brilovely (talk) 19:12, 30 June 2016 (UTC)

Due to the continued issues with the siderail, it's been removed from the Path of Exile Wiki. I apologize for the annoyance it's caused. Brilovely (talk) 15:30, 11 July 2016 (UTC)