Path of Exile Wiki talk:Community portal: Difference between revisions

From Path of Exile Wiki
Jump to navigation Jump to search
>Lord joshi
m (→‎The Awakening to-do list: note about gem xp values, note about Maintaining Low Life site)
 
Line 1: Line 1:
{{archives|style=float:right;}}
== Hybrid gem ==


The hybrid gems i really think need to rework the infobox


== The Awakening to-do list ==
Either remove the parameter for the secondary skill and migrate to skill namespace instead. Or rework the infobox to display the two skills (active and support) correctly


'''Here's a partial to-do list. Feel free to add new things or notify when you're working on something. '''
I think these gems are Hybrid  (may miss a few):
* {{il|Infernal Cry}} (contains Combust)
* {{il|General's Cry}} (contains General's Cry Support)
* {{il|Spellslinger}} (contains Spellslinger Support)
* {{il|Arcanist Brand}} (contains Arcanist Brand Support)
* {{il|Predator Support}} (contains Signal Prey)
* {{il|Shockwave Support}} (contains Shockwave}}
* ...
* Vaal Skill currently has no problem as there are two articles and vaal skill does not interact with base version of the skill.


* Area progression changes (levels and structure) in the first three acts (Qetuth is working on this)
-- [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 04:28, 9 June 2021 (UTC)
* New [[leech]] mechanics
* <s>[[Reduced Mana]] and [[Enlighten]] changes</s>
* <s>Gem vendors</s>
* "Shotgunning" changes
* <s>[[Arctic Armour]]
* New Maraketh base weapons need to be added (''Domokingu is adding these as well as updating any other bases that need it.'')</s>
* New skill gems<s> 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.'')</s>
* Passives <s>(especially Keystones)</s> need updating (''Domokingu has updated the <s>notables</s> and will be working on the regular passive skills.'')
* <s>New unique items
* Info about jewels
* Mention of div cards on the items they produce
* Add the new maps and new map icons.</s> (You'll have to figure out which image belongs to what map, because they're just called "map12" etc in the game files.)
* <s>Update map upgrade table</s>
* <s>Map mod changes</s>
* <s>New map levels</s>
* Legacy items
* Changes to base items
* Changes to flasks
* [[Item affix|Item affixes]] changes
* [[Map#Map-only_drops|Map-only drops]] and particulary Item drop restrictions have been changed


'''Some act 4 stuff that needs work:'''
: I'm thinking part of the solution is migrating all skills to the Skill namespace. That way each gem can simply specify its primary and secondary skills, which are then queried from the skill namespace. —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 04:49, 9 June 2021 (UTC)


* <s>Quests pages need to be created</s>
::Done the easy gem {{il|Predator Support}}, despite i guess the original infobox already missing the stat id behind the mod {{c|mod|Base duration is 8 seconds}}. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 12:26, 2 July 2021 (UTC)
* <s>Highgate NPC's</s>
* <s>Monsters</s>  and bosses
* <s>Flavour text of the new zones (no idea where to find these, I don't play the beta)</s>
* Zone and monster screenshots


--[[User:Climmels|Climmels aka SirProblematique]] ([[User talk:Climmels|talk]]) 08:47, 9 July 2015 (UTC)
::{{il|General's Cry}} also done. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 20:20, 2 July 2021 (UTC)


: I can take on the task of rewriting the [[leech]] article. Although I won't be starting on it right away. —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 12:35, 9 July 2015 (UTC)
== Cat, again ==


:: 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 —[[User:lutem|lutem]] 13:58, 9 July 2015 (UTC)
I wonder is there a need of [[:Category:Bosses]] and [[:Category:Boss monsters]] (the latter is auto populated by template)?


:: 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. —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 12:02, 14 August 2015 (UTC)
As well as should [[:Category:Boss monsters]] also a subcat of [[:Category:Unique monsters]]? I know act boss of an area are skippable and technically a bid different with [[:Category:Map bosses]] (which has {{ml|MonsterMapBoss}}) and probably rogue exile should be called unique monster only as well as Beyond boss has different monster mods {{ml|IsBeyondBoss}}, {{ml|MonsterInvasionBoss}}.


: I'll be going through items/gems/zones/mobs updating their Version History as soon as the patch hits. [[User:Iamacyborg|Iamacyborg]] ([[User talk:Iamacyborg|talk]]) 13:56, 9 July 2015 (UTC)
Another duplicated cat tree is [[:Category:Corrupted areas]] and [[:Category:Vaal areas]].


: 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. [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 02:37, 10 July 2015 (UTC)
[[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 02:57, 11 June 2021 (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... ;-) --[[User:Lord joshi|Lord joshi]] ([[User talk:Lord joshi|talk]])
: Let's start with addressing [[:Category:Corrupted areas]] and [[:Category:Vaal areas]], since it should be fairly straightforward. I propose to remove Category:Corrupted areas using a bot, since this category was added to pages manually. Category:Vaal areas is populated automatically through the template, but I think it should be renamed to Category:Vaal side areas. [[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 03:07, 11 June 2021 (UTC)


: 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 - [[User:Haaxxx|Haaxxx]] ([[User talk:Haaxxx|talk]]) 21:06, 11 July 2015 (UTC)
::Yeah, Vaal side area is the current common name and the name used in patch note. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 03:09, 11 June 2021 (UTC)


: I'm going through the notable passives and updating them as needed, then moving on to the regular passives. - [[User:Domokingu|Domokingu]] ([[User talk:Domokingu|talk]]) 21:12, 11 July 2015 (UTC)
::I have depopulated [[:Category:Corrupted areas]] as all the article in that cat is also belongs to [[:Category:Vaal areas]]. I think the [[:Category:Vaal areas]] cat is associated with [[Module:Area]] thus need to edit the module first. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 05:50, 12 June 2021 (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. [[User:Fucrem|Fucrem]] ([[User talk:Fucrem|talk]]) 19:24, 16 July 2015 (UTC)
::And i have done migrated all boss from [[:Category:Corrupted area bosses]] to [[:Category:Vaal side area bosses]]. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 06:26, 12 June 2021 (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 :) —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|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. [[User:Alacia|Alacia]] ([[User talk:Alacia|talk]]) 21:22, 17 July 2015 (UTC)
== Version history – Unknown introduction to game ==


: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 [http://pathofexile.gamepedia.com/index.php?title=Act_3&oldid=137626 old revision] to [http://pathofexile.gamepedia.com/index.php?title=Act_3&direction=next&oldid=137626 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. --[[User:Qetuth|Qetuth]]-([[User talk: Qetuth|talk]]) 10:05, 22 July 2015 (UTC)
There are articles that state the subject's introduction to the game came in an unknown version. Examples of such articles include [[Crude Bow]], [[Chill]] and [[Buff]]. Many of these articles describe game mechanics that were introduced to the game in very early versions, before GGG even publicly released patch notes. The problem that this poses is that it clutters up the tracking category [[:Category:Pages with version history for unknown versions]]. That category is meant to indicate problems that need to be corrected, but there is no way to know exactly which version buffs were introduced to PoE, for instance. What can we do to resolve this? —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 03:50, 11 June 2021 (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? [[User:SpamNinja|SpamNinja]] ([[User talk:SpamNinja|talk]]) 19:51, 10 August 2015 (UTC)
:Can we set at 0.10.0 and add footnote it probably exist before that? There is lots of basetype are without {{code|release_version}} for the same reason. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 03:54, 11 June 2021 (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. --[[User:Qetuth|Qetuth]]-([[User talk: Qetuth|talk]]) 23:38, 10 August 2015 (UTC)
:: There are two other possibilities that I have in mind:
:: 1. When it is impossible to know when something was added to the game, leave it out entirely. It's not that useful to state that something was added to the game in an unknown version if it was added before the earliest patch notes that we have.
:: 2. Modify the template so that it accepts another special value. Let's say the value is "old". When the template sees this value, it displays "Before 0.10.0".
:: —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 04:03, 11 June 2021 (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. --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 16:58, 15 August 2015 (UTC)
:::Yeah that will do "Before 0.10.0", or before open beta. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 04:06, 11 June 2021 (UTC)


::Nice, this means I can stop updating the skill gem stats? =) [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 19:53, 15 August 2015 (UTC)
:::: Demo: [[Template:Version_history_table_row#Usage]] —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 06:35, 11 June 2021 (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 --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 15:07, 17 August 2015 (UTC)
== Level requirements for low level gear ==


:: Updated the progression on all pages. If there are issues with something please drop me a message or post here.
I never noticed this before, but it seems that the game doesn't enforce the level requirements of low-level gear. According to [https://poedb.tw/us/Fishscale_Gauntlets poedb], {{il|Fishscale Gauntlets}} require level 4, yet they display no level requirement in game and can be equipped by a level 2 character right after entering Lioneye's Watch. Even the [https://www.pathofexile.com/trade/search/Standard/wkY54oKHb official trade site] considers them to have no level requirement – You can see this by setting the max level requirement to 1 in the filters. It's as if the game ignores the level requirement of any piece of gear that requires level 4 or below, even though the data (poedb and pypoe) clearly shows that these items have level requirements. [[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 09:02, 12 June 2021 (UTC)
:: 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. --[[User:OmegaK2|OmegaK2]] ([[User talk: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. [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 08:13, 19 August 2015 (UTC)
: After further investigation, it appears that an item's base level requirement is waived completely if it is below a threshold value of 5. However, modifiers can still add a level requirement. For example, a {{ml|LocalAddedLightningDamage1}} {{il|Nailed Fist}} requires level 2 to equip. I have updated [[Module:Item2]] to account for this. [[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 00:44, 13 June 2021 (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.
== Obsolete monster articles ==


:::: 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)
There are some articles that describe monsters from older versions of the game – in particular, monsters that were present in [[Tora,_Master_of_the_Hunt|Tora]] and [[Elreon,_Loremaster|Elreon]] missions. Is there any reason to preserve these articles? In most cases they contain very little information. —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 20:41, 12 June 2021 (UTC)


:::: 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 think some of the monster articles are untouched like over 3~4 years . For those legacy monster i am not sure it can be improved or not. Sometimes datamined infocard contain all info or may be more than the article counterpart. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 07:05, 13 June 2021 (UTC)


:::: 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:
:And currently [[Module:Area]] has a parameter to switch from jpg to png , which [[Module:Monster]] does not . Except outsider may have no idea on monster skill id means (sometimes it is very different from its actual skill effect) [[Monster:Metadata/Monsters/GemMonster/DexMissionIguanaBoss]] seems contain the same info as [[Twisted Chimeral]]. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 07:48, 13 June 2021 (UTC)
:::: https://github.com/OmegaK2/PyPoE/blob/dev/PyPoE/cli/exporter/wiki/parsers/gems.py


:::: --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 11:40, 19 August 2015 (UTC)
== Monster in Item acquisition template  ==


::::: 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. [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 16:21, 19 August 2015 (UTC)
Currently {{code|drop_monsters}} in {{tl|Item acquisition}} is linked to the infocard in monster namespace. Is it due to [[Special:CargoTables/monsters]] does not have {{code|main_page}} parameter? [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 07:02, 13 June 2021 (UTC)
: We are checking [[Special:CargoTables/main_pages]] according to:
<pre>
        local results = m_cargo.query(
            {'monsters', 'main_pages'},
            {
                'monsters._pageName',
                'monsters.metadata_id',
                'monsters.name',
                -- 'monsters.main_page',
                'main_pages._pageName',
            },
            {
                join='monsters.metadata_id=main_pages.id',
                where=string.format('monsters.metadata_id IN ("%s")', table.concat(monster_metadata_ids, '","')),
                orderBy='monsters.name',
                groupBy='monsters.metadata_id',
            }
        )
</pre>
: But right now we don't store any monster ids there. For this to work we need to update {{tlx|MonsterBox}} (and maybe {{tlx|Monster infobox}}?) to store the metadata_id to main_pages.id if {{code|metadata_id}} has been defined. The passives uses this method, see [[Ghost Reaver]] for an example. --[[User:Illviljan|Illviljan]] ([[User talk:Illviljan|talk]]) 08:25, 13 June 2021 (UTC)
: We maybe should start considering replacing {{tlx|MonsterBox}} with {{tlx|Monster infobox}}, but right now I don't think {{tlx|Monster infobox}} doesn't look as good as the old one still so it could use  some styling touch ups before we go all in on it. --[[User:Illviljan|Illviljan]] ([[User talk:Illviljan|talk]]) 08:34, 13 June 2021 (UTC)
:: I've added the parameter to {{tlx|MonsterBox}} now. It only supports one id per template however since it's just a simple template where you can't split and loop the string that easily. That's a bit of a problem since many bosses have several versions of themselves, probably why I didn't add it before. --[[User:Illviljan|Illviljan]] ([[User talk:Illviljan|talk]]) 10:46, 13 June 2021 (UTC)


{{outdent|:::::}}
:::There is not much boss drop left BTW. I knew the metadata id with "Standalone" suffix apparently for [[The Maven's Crucible]] and apart from Elder (which have 2 articles) i think only Breachlord have more than one id (one id probably for wild , one for in the Breach domain) . And also the prophecy bosses have two id. I think we can just use the id for the main encounter. The thin and fat Doedre of Act 9 encounter (and the map version), we can just choose one for {{tl|Item acquisition}} . {{tl|Monster item drops}} also only support one id. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 11:59, 13 June 2021 (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 [https://github.com/OmegaK2/PyPoE/blob/dev/PyPoE/poe/file/translations.py 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 "{{Abbr|Fire Damage|Adds x-y Fire Damage}}" and not something like "{{Abbr|Fire|Adds x-y Fire Damage}}", "{{Abbr|Fire Damage|Adds x-y Fire Damage}}", "{{Abbr|Fire added|Adds x-y Fire Damage}}", 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 <nowiki>&ndash;</nowiki>, but it's in the code now. But that's a wiki-only thing, the game just uses -.
:::(And it seem i forget [[Atziri, Queen of the Vaal]] have 3 ids for 3 fights ) [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 12:38, 13 June 2021 (UTC)
--[[User:OmegaK2|OmegaK2]] ([[User talk: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. [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 20:57, 19 August 2015 (UTC)
== Charan ==


:: Well, you can look over the [[User:OmegaK2/test3|abbrevations]] and let me know if you think which ones need adjusting.
The POE account [[poeprofile:Foreverhappychan|Foreverhappychan]] claims the account is the new account (or account name) of Charan (aka CharanJaydemyr, 鬼殺し), the signature also indicated that the account also own the reddit account "The_Scourge", which is confirmed to be Charan's reddit username. However, the new account does not have the custom designed avatar anymore. So, is it safe to add this new account name to the unique and mtx designed by Charan? [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 13:32, 2 July 2021 (UTC)
:: 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) --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 01:10, 20 August 2015 (UTC)


: It seems believable that this is Charan's new account, but I don't see the need to continue playing musical chairs with linking to his latest account all the time. In a way it almost feels like stalking. The supporter attribution can simply state that the item was created by Charan without providing a link to the account. Only mention his alternate account names if it's absolutely necessary to provide context to a citation to the forums or reddit. Do you see what I mean? —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 13:49, 2 July 2021 (UTC)


:: Quite a few skill gems that are hybrid STR+INT have their stat reqiurements reversed (ie summon flame golem.) --[[User:RicochetSaw|RicochetSaw]] ([[User talk:RicochetSaw|talk]]) 04:58 25 August 25 2015 (UTC)
::Yeah, "Charan" is probably sufficient as we never know he would change his username once again. And only the sword article need to mention his previous name as a context for the citation's author. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 20:47, 4 July 2021 (UTC)


::: Thanks! Fixed that in the script.
== Is it possible to activate the wide version by default on this wiki ? ==
::: On a side note, if no further things come up, I'll be updating the pages again tonight or tommorow --[[User:OmegaK2|OmegaK2]] ([[User talk: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. --[[User:Lord joshi|Lord joshi]] ([[User talk:Lord joshi|talk]])
This wiki was designed for a display on all the page, but since it has been transfer from Gamepedia to Fandom, the display is not anymore wide. <br/>
There is an option in the personal parameter to make it wide : https://i.imgur.com/oUCNOvI.png but it is only for me, most user don't know this option, and will have a bad display.
So it would be good if you activate it by default for everyone. <br/>
--[[User:GKPlight|GKPlight]] ([[User talk:GKPlight|talk]]) 19:06, 30 July 2021 (UTC)


: 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. --[[User:Lord joshi|Lord joshi]] ([[User talk:Lord joshi|talk]])
: I have requested this, but so far Fandom hasn't given us the option. [[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 20:37, 30 July 2021 (UTC)


== Launch Options page ==
== This wiki would be better if the comment section was not deactivate. ==


I think we need one with a list of launch options and explanation what they do. [[User:TheFrz|TheFrz]] ([[User talk:TheFrz|talk]]) 17:55, 12 July 2015 (UTC)
It allow people to ask question when something is not clear in an article, so we can then improve the article. <br/>
: Cool. Make one. —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 18:50, 12 July 2015 (UTC)
"The talk page existe" is not a good argument : near nobody use it. and if it exist, why a comment section could not exist ? <br/>
:: Done, but I think I need some help with [[Launch options|it]] --[[User:TheFrz|TheFrz]] ([[User talk:TheFrz|talk]]) 20:01, 12 July 2015 (UTC)
It is also much better for a community aspect. Even if most discussion will not be use to improve the page, it is a way to discus of the game, the builds, ... <br/>
::: Looks good to me, what do you need help with? [[User:Iamacyborg|Iamacyborg]] ([[User talk:Iamacyborg|talk]]) 00:14, 21 July 2015 (UTC)
Some exemples of comment section from other wikis : https://warframe.fandom.com/wiki/Oberon#articleComments  https://genshin-impact.fandom.com/wiki/Kaeya#articleComments  <br/>
--[[User:GKPlight|GKPlight]] ([[User talk:GKPlight|talk]]) 19:37, 30 July 2021 (UTC)


== Item filter list ("moderated") ==
== broken russian(?) links? ==
a lot of pages have broken russian links at the bottom of them. Do they serve some purpose? Can they be deleted? <!-- Template:Unsigned --><small>—Preceding [[Help:Signatures|unsigned]] comment added by [[User:Bloonpauper|Bloonpauper]] ([[User talk:Bloonpauper#top|talk]] • [[Special:Contributions/Bloonpauper|contribs]]) 03:47, 23 September 2021‎ (UTC)</small>


I see people adding their own [[item filter]]s to the current page. I've had the thought for a while, but I believe we should separate item filters into their own page.
:Just leave them in the wiki. Ru-poe wiki is still in fandom. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 14:05, 23 September 2021 (UTC)
::Good day everyone, and who should I contact with the question of transferring the Russian-language project, to you?[[User:Kordloperdlo|Kordloperdlo]] ([[User talk:Kordloperdlo|talk]]) 05:44, 15 April 2024 (UTC)


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).
::Last time i heard [[User:Ruba159753]] is not that interested to transfer to new wiki. For tech support i guess you better ask the question again in discord [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 14:11, 16 April 2024 (UTC)
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
::If i have time i probably interested to write Traditional Chinese POE wiki. The realm has some interesting thing such as WTF with that translation. e.g. [[The Coast (Act 1)]] somehow swapped name with [[The Twilight Strand (Act 1)]]. But i don't have time. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 14:13, 16 April 2024 (UTC)
* 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:
==Skill lists category==
* ingame screenshots/examples
[[:Category:Skill lists]] should really be renamed to "Lists of skill gems", or at least "Skill gem lists". The name is misleading, and there's already [[:Category:Lists of skills]] that does what [[:Category:Skill lists]] ''sounds'' like it does. [[User:KickahaOta|KickahaOta]] ([[User talk:KickahaOta|talk]]) 21:08, 12 November 2021 (UTC)


: I'm fine with renaming [[:Category:Skill lists]] to [[:Category:Lists of skill gems]]. —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 15:30, 1 February 2022 (UTC)


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.
== Location information for keystone passive skills ==
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.
Most articles in [[:Category:Keystone passive skills]] have location information:
--[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 03:35, 18 July 2015 (UTC)
* A description of where the keystone skill is in the passive skill tree.
* Often, a table of how many nodes the skill is away from the starting area of each class.
All of this is handcrafted. As of 3.16, basically all of it is wrong.
We need to decide whether to update this information for 3.16, or delete it. I would tentatively suggest "delete".
* Description of where the skill is in the tree: There's already Ctrl+F in the PoE passive tree screen. Yes, it kind of sucks, because you've got to zoom out and scroll around and try to spot the slowly-pulsing thing. But that still seems like it's not likely to be slower than a text-based description.
* Table of how many nodes away each class starting area is: This is potentially useful information. But even if it were correct, it's not expressed in the form that would make it most useful. Someone isn't likely to say "What's the class that's closest to this skill?" (And if they did say that, they could just look at the tree.) They're more likely to say "I'm planning out a Marauder; what keystone skills are within, say, 15 nodes?"
In theory, someone could use the connection information in the Cargo tables to write a really impressive data-driven module to show tables like "What other nodes of a given type are within X connections of this node?" That would be much more useful and would eliminate the need to handcraft this stuff. But given all the other to-dos on the pile, I don't see it happening. And in the absence of that, the handcrafted information seems like more trouble than it's worth. [[User:KickahaOta|KickahaOta]] ([[User talk:KickahaOta|talk]]) 23:10, 14 December 2021 (UTC)


: I need to understand what the issue is, exactly. There are already two pages (at least?) pertaining to loot filters. [[Item filter|One of them]] is a general overview and missing some critical information. [[Item filter guide|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. —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 04:03, 18 July 2015 (UTC)
== How do you edit the infobox of a unique item? ==


:: My post was basically about expanding section [[Item filter#Popular item filters]] into it's [[List of item filters|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.
When editing an item's page, there are data keys representing values, something like |explicit1 = SomeKeyName1. How or where do I edit this value?
:: 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. --[[User:OmegaK2|OmegaK2]] ([[User talk: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.
Also, the Signature help page should be created. <!-- Template:Unsigned --><small>—Preceding [[Help:Signatures|unsigned]] comment added by [[User:Wicke|Wicke]] ([[User talk:Wicke#top|talk]] • [[Special:Contributions/Wicke|contribs]]) 09:20, 29 December 2021‎ (UTC)</small>
: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. &mdash;[[User:TheFrz|TheFrz]] ([[User talk:TheFrz|talk]]) 16:38, 18 July 2015 (UTC)
:use [https://www.poewiki.net/w/index.php?search=&title=Special%3ASearch&profile=advanced&fulltext=1&ns10004=1 adv search], untick main and tick modifier only , search using mod text as keyword, see are there any matching mod with "unique" as an affix in its id / page name. Alternatively , use cargo query in your user page sandbox. Also in case there is more than one result, usually new mod is for new unique so that new unique not likely using old mod id. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 10:34, 29 December 2021 (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.
:Also, except unique atlas region watchstone or the unique cluster jewel with random notables, the unique mod of the unique are in mod domain "3" despite the domain also contains implicit [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 05:02, 31 December 2021 (UTC)
: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. --[[User:Qetuth|Qetuth]]-([[User talk: Qetuth|talk]]) 23:38, 18 July 2015 (UTC)
:: I spoke with [[User:Iamacyborg|Iamacyborg]] and he mentioned something about having the wiki's own loot filter. That could be an option. —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 01:58, 19 July 2015 (UTC)
::: Yeah, I think it could be a fun project. [[User:Iamacyborg|Iamacyborg]] ([[User talk: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? --[[User:OmegaK2|OmegaK2]] ([[User talk: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]] --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 05:52, 21 July 2015 (UTC)
== Legacy variants section for fated unique items ==
:: 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? [[User:Iamacyborg|Iamacyborg]] ([[User talk: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. --[[User:OmegaK2|OmegaK2]] ([[User talk: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 [[User:Qetuth|Qetuth]], [[User:Vinifera7|Vinifera7]], [[User talk:Iamacyborg|Iamacyborg]] :) --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 14:07, 25 July 2015 (UTC)
:: Sounds good to me. --[[User:Qetuth|Qetuth]]-([[User talk: 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. [[User:Iamacyborg|Iamacyborg]] ([[User talk:Iamacyborg|talk]]) 22:23, 26 July 2015 (UTC)


== Move to remove redundant boss videos on map pages ==
On some of the articles about [[fated item]]s, the [[legacy variant]]s section is currently overloaded with other pseudo-variants that could theoretically exist if a legacy variant of the base unique item was upgraded to its fated counterpart during a later time period. I propose removing these pseudo-variants and providing an explanation about their existence instead. An example of this treatment can be seen on the [[Doomfletch's Prism]] article ([https://www.poewiki.net/w/index.php?title=Doomfletch%27s_Prism&type=revision&diff=1142766&oldid=1142724 diff]). This ''does'' mean removing information from an article, but sometimes that can be a good thing if it makes the article read better. In this case, I don't think it's necessary or good at all to list every possible pseudo-variant that might exist in Standard. If someone is really interested in, for example, a Doomfletch's Prism that has the current explicit modifiers but no implicit, they can go search for it on trade. It doesn't need to be listed if it means sacrificing the article's readability. —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 01:03, 1 February 2022 (UTC)


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. —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 19:26, 21 July 2015 (UTC)
:It is worse as some how some legacy mod are retained and sometimes it does not after 3.14~ish patch (aka ninja nerf). +6 {{il|Frostferno}} must be created in perma league as the base item going to legacy before the release of fated item and there is only one entry so that this quasi-legacy fated item does not clutter the page. While {{il|Shavronne's Gambit}}, due to the ninja 3.14~ish change, i was told in the official forum, there are more than 4 variants. So that may be case by case? [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 01:12, 1 February 2022 (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. [[User:Iamacyborg|Iamacyborg]] ([[User talk: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 --[[User:Qetuth|Qetuth]]-([[User talk: Qetuth|talk]]) 03:44, 22 July 2015 (UTC)


== Master Page change request ==
:: That's interesting. I never knew about that change. Does that mean it became impossible to craft a +6 Frostferno in Standard after version 3.14.X? —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 15:35, 1 February 2022 (UTC)


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. 
:::Too expensive to tell, as least i just break my legacy {{il|Kaom's Way}} only. So that probably GGG treated it as ninja bug fix. Yes the list is way too long if adding those legacy and double legacy fated mix and match, but i don't have a good solution in my mind, as some item like {{il|Kaom's Way}} and {{il|Frostferno}} have only one more entry for these quasi-legacy / double legacy mix and match , but {{il|Shavronne's Gambit}} or Doomfetch potentially more than 4 entries if we insist to doc all. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 02:53, 2 February 2022 (UTC)


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. 
== Captured Soul page names ==


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?
The [[Pantheon soul|captured soul]] items change names with the Atlas shuffle every league, but they retain the same flavor text and metadata ids. In order to reduce some of the workload for each league, I suggest using a more generic naming scheme for these items' pages:
[[User:SpamNinja|SpamNinja]] ([[User talk: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. [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 10:35, 30 July 2015 (UTC)
[[Captured Soul of Arachnoxia]] [[Captured Soul (Arakaali upgrade 1 of 3)]]


: When posting on the talk page, please do not forget to sign your posts with <nowiki>~~~~</nowiki>.
[[Captured Soul of The Forgotten Soldier]] → [[Captured Soul (Ryslatha upgrade)]]


: 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.
—[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 17:21, 23 March 2022 (UTC)


: 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. --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 11:30, 30 July 2015 (UTC)
:Yeah i agree to have a static name. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 00:18, 24 March 2022 (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. --[[User:Qetuth|Qetuth]]-([[User talk: Qetuth|talk]]) 11:40, 30 July 2015 (UTC)
:GGG made a merry-go-round in 3.17 for Arakaali 's upgrades. So that probably redirect (the Captured Soul of "map boss name") to [[Captured Soul]] or [[Pantheon soul]] or [[The Pantheon]] may be better.
::: 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 --[[User:OmegaK2|OmegaK2]] ([[User talk: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. [[User:TheMipchunk|TheMipchunk]] ([[User talk: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? [[User:SpamNinja|SpamNinja]] ([[User talk: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. [[User:TheMipchunk|TheMipchunk]] ([[User talk:TheMipchunk|talk]]) 01:05, 31 July 2015 (UTC)
{{outdent|::::::}}
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. --[[User:Qetuth|Qetuth]]-([[User talk: 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. [[User:SpamNinja|SpamNinja]] ([[User talk: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). --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 12:01, 31 July 2015 (UTC)


== Templating Pages ==
:Sometimes the map boss is for this god in this league, but a few leagues before it is for another. So that redirect is tricky to handle


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).
:(copy my comment from discord) [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 10:52, 24 March 2022 (UTC)
: Yeah, static name makes sense to me too [[User:Iamacyborg|Iamacyborg]] ([[User talk:Iamacyborg|talk]]) 10:46, 24 March 2022 (UTC)


The point is that most pages are setup in a very similar fashion, e.g. most skill pages go like this essentially:
== Adding the various Archnemesis mod 'rarity' colours to the system ==
* 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.  
Its boring work and I would do it myself if I knew how, but considering we support the {{c|bloodline|Bloodline}} and {{c|nemesis|Nemesis}} 'rarities', could we add them for each of the new Archnemesis mods as it would probably help users identifying the mod that gave them trouble by it's colour, or in the situation where they were killed too fast to read the modifier's text. — [[User:RubyAxe|RubyAxe]] 07:49 5 August 2022 (UTC)


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.
:It does not really help to identify the mod , as GGG did not announced in their website which color of the each mods. You either read the actual mod text or just one shot. For visualization it may be good to copy the in-game mod text color to wiki , but not really help on mod  identification. (Unless people did not use Shadowplay, and just remembered killed one shot by color X mod , and try to narrow down the possible mods by color. ) [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 10:03, 5 August 2022 (UTC)


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.
== Updating passive skill info ==
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.
I noticed that the skill description for [[Shadow Shaping]] was incorrect, and hunted down how to edit the info box. I found my way to [[Passive Skill:Atlas~keystone~disfavoured~maps]] and edited that, however it seems the update didn't propagate to any of the pages referencing it ([[Shadow Shaping]], [[Atlas keystone]], [[List of atlas keystone passive skills]] etc). How would I do that? -- [[User:CandyCorvid|CandyCorvid]] ([[User talk:CandyCorvid|talk]]) 01:39, 13 August 2022 (UTC)
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.  
:Looks like it's been updated now. Not sure if I just needed to wait for it to propagate, or if someone pressed a button somewhere, but I'm happy now. -- [[User:CandyCorvid|CandyCorvid]] ([[User talk:CandyCorvid|talk]]) 01:43, 20 August 2022 (UTC)
--[[User:OmegaK2|OmegaK2]] ([[User talk: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
== Signature Help Page ==
'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. --[[User:Qetuth|Qetuth]]-([[User talk: Qetuth|talk]]) 05:40, 2 August 2015 (UTC)
:: Well, people can still edit sections. It's just that the <nowiki>[Edit]</nowiki> 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). --[[User:OmegaK2|OmegaK2]] ([[User talk:OmegaK2|talk]]) 00:20, 6 August 2015 (UTC)


==Bandwidth-Heavy Ads==
I came here to make the above question about passive skills, but quickly realised that the [[Help:Signatures]] link was just a broken redirect to [[Gphelp:Signatures]]. Best I could do to fix it was just revert to a previous version before the redirect. Hopefully that's good enough for now; at least it has enough info that I was able to learn how to use signatures from it, but it might need some more work to fix the other broken links. -- [[User:CandyCorvid|CandyCorvid]] ([[User talk:CandyCorvid|talk]]) 01:55, 13 August 2022 (UTC)
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. [[User:TheMipchunk|TheMipchunk]] ([[User talk: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 [[User:Iamacyborg|Iamacyborg]] ([[User talk:Iamacyborg|talk]]) 14:17, 5 August 2015 (UTC)


== Damage per second calculations (Weapon lists etc.) ==
== Skill level missing data ==


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.
How does one go about of adding/updating missing data from skill gem levels? At the moment [[Intensify Support]] is missing the stat_text for "Supported Skills deal x% more Area Damage with Hits per Intensity" at each level (and [[Vile Toxins Support]] is also missing a levelling stat_text). I am hesistant to update it manually in the info box, since it looks like the info boxes are automatically generated and a new export will probably undo the changes. [[User:Dreddie|Dreddie]] ([[User talk:Dreddie|talk]]) 08:05, 16 August 2023 (UTC)


Reasoning:  
:It is something [[pypoe]] issue. Post it in discord or github. [[User:Neokowloon|Neokowloon]] ([[User talk:Neokowloon|talk]]) 10:49, 16 August 2023 (UTC)
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.
== Suggestion: Remove Template:Stub from the wiki ==
<small>—The preceding [[gphelp:Signatures|unsigned comment]] was added by [[User:Lame4Fame|Lame4Fame]] ([[User talk:Lame4Fame|talk]] • [[Special:Contributions/Lame4Fame|contribs]]) 14:25, 6 August 2015‎ (UTC)</small><!-- Template:Unsigned -->


: This seems pretty reasonable. Any objections to this change? —[[User:Vinifera7|Vini]]&nbsp;([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 19:13, 6 August 2015 (UTC)
I would like to propose the removal of {{tl|Stub}} from the wiki. The intended purpose of this template is to flag articles that are created as placeholders so that editors can find them more easily. However, I don't know that any editors actually use it this way. [[:Category:Stubs]] ought to be empty or nearly empty most of the time, yet there are hundreds of articles flagged as stubs. Most of these aren't even flagged correctly. What tends to happen is that someone will create an article and flag it as a stub, and then no one will ever remove the stub template, even after the article is expanded. That makes this template not very useful in my opinion, so I would rather not have it at all. What do others think? Do you frequently view the stubs category to find pages that need to be expanded? Once you expand a page flagged as a stub, do you remove the stub template? —[[User:Vinifera7|Vini]] ([[User talk:Vinifera7|t]]|[[Special:Contributions/Vinifera7|c]]) 19:54, 16 April 2024 (UTC)

Latest revision as of 19:54, 16 April 2024

Hybrid gem

The hybrid gems i really think need to rework the infobox

Either remove the parameter for the secondary skill and migrate to skill namespace instead. Or rework the infobox to display the two skills (active and support) correctly

I think these gems are Hybrid (may miss a few):

  • Infernal CryInfernal CryWarcry, AoE, Duration, Fire, Attack, Trigger, Melee
    Level: (1-20)
    Cost: (15-19) Mana
    Cooldown Time: 8.00 sec
    Can Store 1 Use(s)
    Use Time: 0.80 sec
    AoE Radius: 60
    Requires Level 24Performs a warcry, taunting nearby enemies to attack the user and exerting subsequent attacks. Covers enemies in ash, causing them to move slower and take increased fire damage. Affected enemies explode when they die, dealing fire damage in an area.Base duration is (5.00-5.90) seconds
    (0-38)% increased Warcry Speed
    Damage cannot be Reflected
    Explosion deals Fire Damage equal to 8% of the Monster's maximum Life
    Counts total Power of Enemies in Range
    Covers Enemies in Ash, causing 3% increased Fire Damage taken per 5 Power, up to 20%
    Exerts the next 6 Melee Attacks you perform
    Exerted Attacks Trigger Combust the first time they deal a Melee Hit
    60% of Physical Damage Converted to Fire Damage
    This Skill is Triggered by Attacks Exerted by Infernal Cry

    Additional Effects From 1-20% Quality:
    (2-40)% increased Cooldown Recovery Rate
    Place into an item socket of the right colour to gain this skill. Right click to remove from a socket.
    (contains Combust)
  • General's CryGeneral's CryWarcry, AoE, Duration
    Level: (1-20)
    Cost: (15-19) Mana
    Cooldown Time: 3.00 sec
    Can Store 1 Use(s)
    Use Time: 0.80 sec
    AoE Radius: 60
    Requires Level 24Performs a warcry, taunting nearby enemies to attack the user, and summoning Mirage Warriors from nearby corpses. The Mirage Warriors each use a linked attack skill once before dissipating.Base duration is (4.00-4.90) seconds
    (0-38)% increased Warcry Speed
    Maximum 5 Summoned Mirage Warriors
    Counts total Power of Enemies and Corpses in Range
    Summons Mirage Warriors from 2 corpses per 5 Power, minimum 1 corpse
    Supported Strike Skills cannot target additional Enemies
    Attacks with Supported Skills count as Exerted
    Supported Skills deal (45-36)% less Damage
    Supported Skills are used by Mirage Warriors Summoned by General's Cry
    Supported Skills count as Triggered

    Additional Effects From 1-20% Quality:
    Maximum +(0.05-1) Summoned Mirage Warriors
    Place into an item socket of the right colour to gain this skill. Right click to remove from a socket.
    (contains General's Cry Support)
  • SpellslingerSpellslingerTrigger, Spell
    Level: (1-20)
    Reservation: (30-25)% Mana
    Cooldown Time: 0.60 sec
    Can Store 1 Use(s)
    Cast Time: Instant
    Requires Level 24Reserves mana based on the supported spells to cause those spells to trigger when you fire projectiles from a wand attack.This Skill's Mana Reservation is the total of the Mana Reservations of Supported Skills, and cannot be further modified
    Trigger Supported Spells when you fire Projectiles from a Non-Triggered Wand Attack
    Supported Skills have (0-38)% increased Cooldown Recovery Rate
    Supported Skills have Added Spell Damage equal to (60-174)% of Damage of Equipped Wand
    If two Wands are Equipped, each contributes half as much Added Damage
    Supported Skills deal (37-31)% less Damage with Hits and Ailments

    Additional Effects From 1-20% Quality:
    Supported Skills have Added Spell Damage equal to +(1-20)% of Damage of Equipped Wand
    If two Wands are Equipped, each contributes half as much Added Damage
    Place into an item socket of the right colour to gain this skill. Right click to remove from a socket.
    (contains Spellslinger Support)
  • Arcanist BrandArcanist BrandTrigger, Spell, Duration, Brand
    Level: (1-20)
    Cost: (18-32) Mana
    Cast Time: 0.80 sec
    Requires Level 38Creates a magical brand which can attach to a nearby enemy. It periodically activates while attached, triggering linked spells. The brand will detach if the enemy dies.Activates every second while Attached
    Increases and Reductions to Cast Speed also apply to this Skill's Activation frequency
    Can be Detached for a total Duration of 5.00 seconds
    Can be Attached for a total Duration of 3.00 seconds
    Supported Skills have 40% reduced Chaining range
    Projectiles from Supported Skills have 4.8 metres maximum range
    Supported Skills have 40% less Area of Effect
    Supported Skills deal (69-63)% less Damage
    Supported Skills Deal (40-59)% more Damage with Hits against Branded Enemy
    Supported Skills are Triggered by Arcanist Brand, from the Brand's location

    Additional Effects From 1-20% Quality:
    (0.5-10)% increased Activation frequency
    Place into an item socket of the right colour to gain this skill. Right click to remove from a socket.
    (contains Arcanist Brand Support)
  • Predator SupportPredator SupportSupport, Minion, Spell, Duration
    Icon: h
    Level: (1-20)
    Cost & Reservation Multiplier: 130%
    Cooldown Time: 0.80 sec
    Can Store 1 Use(s)
    Cast Time: Instant
    Requires Level 18Supports skills which create Minions.Minions from Supported Skills deal (6-12)% more Damage
    Minions from Supported Skills deal (15-24)% more Damage to the Prey with Hits and Ailments
    Minions from Supported Skills always target the Prey if possible
    Base duration is 8.00 seconds

    Additional Effects From 1-20% Quality:
    Minions from Supported Skills deal (0.5-10)% increased Damage
    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 Skill Gem you wish to augment. Right click to remove from a socket.
    (contains Signal Prey)
  • Shockwave SupportShockwave SupportSupport, Melee, Attack, AoE
    Icon: s
    Level: (1-20)
    Cost & Reservation Multiplier: 140%
    Cooldown Time: 1.00 sec
    Can Store (1-4) Use(s)
    Requires Level 18Supports melee attack skills. Cannot support triggered attacks, attacks used by things other than you, or skills which create minions.Supported Skills will Trigger Shockwave on Melee Hit
    Supported Skills can only be used with Maces, Sceptres or Staves
    +(0-0.3) metres to radius
    (0-38)% increased Cooldown Recovery Rate

    Additional Effects From 1-20% Quality:
    Supported Skills deal (0.5-10)% increased Melee Damage
    (0.5-10)% increased Melee Damage
    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 Skill Gem you wish to augment. Right click to remove from a socket.
    (contains Shockwave}}
  • ...
  • Vaal Skill currently has no problem as there are two articles and vaal skill does not interact with base version of the skill.

-- Neokowloon (talk) 04:28, 9 June 2021 (UTC)

I'm thinking part of the solution is migrating all skills to the Skill namespace. That way each gem can simply specify its primary and secondary skills, which are then queried from the skill namespace. —Vini (t|c) 04:49, 9 June 2021 (UTC)
Done the easy gem Predator SupportPredator SupportSupport, Minion, Spell, Duration
Icon: h
Level: (1-20)
Cost & Reservation Multiplier: 130%
Cooldown Time: 0.80 sec
Can Store 1 Use(s)
Cast Time: Instant
Requires Level 18Supports skills which create Minions.Minions from Supported Skills deal (6-12)% more Damage
Minions from Supported Skills deal (15-24)% more Damage to the Prey with Hits and Ailments
Minions from Supported Skills always target the Prey if possible
Base duration is 8.00 seconds

Additional Effects From 1-20% Quality:
Minions from Supported Skills deal (0.5-10)% increased Damage
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 Skill Gem you wish to augment. Right click to remove from a socket.
, despite i guess the original infobox already missing the stat id behind the mod Base duration is 8 seconds. Neokowloon (talk) 12:26, 2 July 2021 (UTC)
General's CryGeneral's CryWarcry, AoE, Duration
Level: (1-20)
Cost: (15-19) Mana
Cooldown Time: 3.00 sec
Can Store 1 Use(s)
Use Time: 0.80 sec
AoE Radius: 60
Requires Level 24Performs a warcry, taunting nearby enemies to attack the user, and summoning Mirage Warriors from nearby corpses. The Mirage Warriors each use a linked attack skill once before dissipating.Base duration is (4.00-4.90) seconds
(0-38)% increased Warcry Speed
Maximum 5 Summoned Mirage Warriors
Counts total Power of Enemies and Corpses in Range
Summons Mirage Warriors from 2 corpses per 5 Power, minimum 1 corpse
Supported Strike Skills cannot target additional Enemies
Attacks with Supported Skills count as Exerted
Supported Skills deal (45-36)% less Damage
Supported Skills are used by Mirage Warriors Summoned by General's Cry
Supported Skills count as Triggered

Additional Effects From 1-20% Quality:
Maximum +(0.05-1) Summoned Mirage Warriors
Place into an item socket of the right colour to gain this skill. Right click to remove from a socket.
also done. Neokowloon (talk) 20:20, 2 July 2021 (UTC)

Cat, again

I wonder is there a need of Category:Bosses and Category:Boss monsters (the latter is auto populated by template)?

As well as should Category:Boss monsters also a subcat of Category:Unique monsters? I know act boss of an area are skippable and technically a bid different with Category:Map bosses (which has Monsters grant 100% increased Experience (Hidden), 15000% increased Rarity of Items Dropped (Hidden)MonsterMapBoss
Intrinsic
Monsters grant 100% increased Experience (Hidden)
15000% increased Rarity of Items Dropped (Hidden)
) and probably rogue exile should be called unique monster only as well as Beyond boss has different monster mods IsBeyondBossIsBeyondBoss
Intrinsic
, 300% increased Quantity of Items Dropped (Hidden), 800% increased Rarity of Items Dropped (Hidden)MonsterInvasionBoss
Intrinsic
300% increased Quantity of Items Dropped (Hidden)
800% increased Rarity of Items Dropped (Hidden)
.

Another duplicated cat tree is Category:Corrupted areas and Category:Vaal areas.

Neokowloon (talk) 02:57, 11 June 2021 (UTC)

Let's start with addressing Category:Corrupted areas and Category:Vaal areas, since it should be fairly straightforward. I propose to remove Category:Corrupted areas using a bot, since this category was added to pages manually. Category:Vaal areas is populated automatically through the template, but I think it should be renamed to Category:Vaal side areas. —Vini (t|c) 03:07, 11 June 2021 (UTC)
Yeah, Vaal side area is the current common name and the name used in patch note. Neokowloon (talk) 03:09, 11 June 2021 (UTC)
I have depopulated Category:Corrupted areas as all the article in that cat is also belongs to Category:Vaal areas. I think the Category:Vaal areas cat is associated with Module:Area thus need to edit the module first. Neokowloon (talk) 05:50, 12 June 2021 (UTC)
And i have done migrated all boss from Category:Corrupted area bosses to Category:Vaal side area bosses. Neokowloon (talk) 06:26, 12 June 2021 (UTC)

Version history – Unknown introduction to game

There are articles that state the subject's introduction to the game came in an unknown version. Examples of such articles include Crude Bow, Chill and Buff. Many of these articles describe game mechanics that were introduced to the game in very early versions, before GGG even publicly released patch notes. The problem that this poses is that it clutters up the tracking category Category:Pages with version history for unknown versions. That category is meant to indicate problems that need to be corrected, but there is no way to know exactly which version buffs were introduced to PoE, for instance. What can we do to resolve this? —Vini (t|c) 03:50, 11 June 2021 (UTC)

Can we set at 0.10.0 and add footnote it probably exist before that? There is lots of basetype are without release_version for the same reason. Neokowloon (talk) 03:54, 11 June 2021 (UTC)
There are two other possibilities that I have in mind:
1. When it is impossible to know when something was added to the game, leave it out entirely. It's not that useful to state that something was added to the game in an unknown version if it was added before the earliest patch notes that we have.
2. Modify the template so that it accepts another special value. Let's say the value is "old". When the template sees this value, it displays "Before 0.10.0".
Vini (t|c) 04:03, 11 June 2021 (UTC)
Yeah that will do "Before 0.10.0", or before open beta. Neokowloon (talk) 04:06, 11 June 2021 (UTC)
Demo: Template:Version_history_table_row#UsageVini (t|c) 06:35, 11 June 2021 (UTC)

Level requirements for low level gear

I never noticed this before, but it seems that the game doesn't enforce the level requirements of low-level gear. According to poedb, Fishscale GauntletsFishscale GauntletsArmour: (9-12)
Evasion: (9-12)
require level 4, yet they display no level requirement in game and can be equipped by a level 2 character right after entering Lioneye's Watch. Even the official trade site considers them to have no level requirement – You can see this by setting the max level requirement to 1 in the filters. It's as if the game ignores the level requirement of any piece of gear that requires level 4 or below, even though the data (poedb and pypoe) clearly shows that these items have level requirements. —Vini (t|c) 09:02, 12 June 2021 (UTC)

After further investigation, it appears that an item's base level requirement is waived completely if it is below a threshold value of 5. However, modifiers can still add a level requirement. For example, a HummingHumming
Prefix
Adds 1 to (5-6) Lightning Damage
Nailed FistNailed FistClaw
Physical Damage: 4-11
Critical Strike Chance: 6.20%
Attacks per Second: 1.60
Weapon Range: 1.1 metres
Grants 3 Life per Enemy Hit
requires level 2 to equip. I have updated Module:Item2 to account for this. —Vini (t|c) 00:44, 13 June 2021 (UTC)

Obsolete monster articles

There are some articles that describe monsters from older versions of the game – in particular, monsters that were present in Tora and Elreon missions. Is there any reason to preserve these articles? In most cases they contain very little information. —Vini (t|c) 20:41, 12 June 2021 (UTC)

I think some of the monster articles are untouched like over 3~4 years . For those legacy monster i am not sure it can be improved or not. Sometimes datamined infocard contain all info or may be more than the article counterpart. Neokowloon (talk) 07:05, 13 June 2021 (UTC)
And currently Module:Area has a parameter to switch from jpg to png , which Module:Monster does not . Except outsider may have no idea on monster skill id means (sometimes it is very different from its actual skill effect) Monster:Metadata/Monsters/GemMonster/DexMissionIguanaBoss seems contain the same info as Twisted Chimeral. Neokowloon (talk) 07:48, 13 June 2021 (UTC)

Monster in Item acquisition template

Currently drop_monsters in {{Item acquisition}} is linked to the infocard in monster namespace. Is it due to Special:CargoTables/monsters does not have main_page parameter? Neokowloon (talk) 07:02, 13 June 2021 (UTC)

We are checking Special:CargoTables/main_pages according to:
        local results = m_cargo.query(
            {'monsters', 'main_pages'},
            {
                'monsters._pageName',
                'monsters.metadata_id',
                'monsters.name',
                -- 'monsters.main_page',
                'main_pages._pageName',
            },
            {
                join='monsters.metadata_id=main_pages.id',
                where=string.format('monsters.metadata_id IN ("%s")', table.concat(monster_metadata_ids, '","')),
                orderBy='monsters.name',
                groupBy='monsters.metadata_id',
            }
        )
But right now we don't store any monster ids there. For this to work we need to update {{MonsterBox}} (and maybe {{Monster infobox}}?) to store the metadata_id to main_pages.id if metadata_id has been defined. The passives uses this method, see Ghost Reaver for an example. --Illviljan (talk) 08:25, 13 June 2021 (UTC)
We maybe should start considering replacing {{MonsterBox}} with {{Monster infobox}}, but right now I don't think {{Monster infobox}} doesn't look as good as the old one still so it could use some styling touch ups before we go all in on it. --Illviljan (talk) 08:34, 13 June 2021 (UTC)
I've added the parameter to {{MonsterBox}} now. It only supports one id per template however since it's just a simple template where you can't split and loop the string that easily. That's a bit of a problem since many bosses have several versions of themselves, probably why I didn't add it before. --Illviljan (talk) 10:46, 13 June 2021 (UTC)
There is not much boss drop left BTW. I knew the metadata id with "Standalone" suffix apparently for The Maven's Crucible and apart from Elder (which have 2 articles) i think only Breachlord have more than one id (one id probably for wild , one for in the Breach domain) . And also the prophecy bosses have two id. I think we can just use the id for the main encounter. The thin and fat Doedre of Act 9 encounter (and the map version), we can just choose one for {{Item acquisition}} . {{Monster item drops}} also only support one id. Neokowloon (talk) 11:59, 13 June 2021 (UTC)
(And it seem i forget Atziri, Queen of the Vaal have 3 ids for 3 fights ) Neokowloon (talk) 12:38, 13 June 2021 (UTC)

Charan

The POE account Foreverhappychan claims the account is the new account (or account name) of Charan (aka CharanJaydemyr, 鬼殺し), the signature also indicated that the account also own the reddit account "The_Scourge", which is confirmed to be Charan's reddit username. However, the new account does not have the custom designed avatar anymore. So, is it safe to add this new account name to the unique and mtx designed by Charan? Neokowloon (talk) 13:32, 2 July 2021 (UTC)

It seems believable that this is Charan's new account, but I don't see the need to continue playing musical chairs with linking to his latest account all the time. In a way it almost feels like stalking. The supporter attribution can simply state that the item was created by Charan without providing a link to the account. Only mention his alternate account names if it's absolutely necessary to provide context to a citation to the forums or reddit. Do you see what I mean? —Vini (t|c) 13:49, 2 July 2021 (UTC)
Yeah, "Charan" is probably sufficient as we never know he would change his username once again. And only the sword article need to mention his previous name as a context for the citation's author. Neokowloon (talk) 20:47, 4 July 2021 (UTC)

Is it possible to activate the wide version by default on this wiki ?

This wiki was designed for a display on all the page, but since it has been transfer from Gamepedia to Fandom, the display is not anymore wide.
There is an option in the personal parameter to make it wide : https://i.imgur.com/oUCNOvI.png but it is only for me, most user don't know this option, and will have a bad display. So it would be good if you activate it by default for everyone.
--GKPlight (talk) 19:06, 30 July 2021 (UTC)

I have requested this, but so far Fandom hasn't given us the option. —Vini (t|c) 20:37, 30 July 2021 (UTC)

This wiki would be better if the comment section was not deactivate.

It allow people to ask question when something is not clear in an article, so we can then improve the article.
"The talk page existe" is not a good argument : near nobody use it. and if it exist, why a comment section could not exist ?
It is also much better for a community aspect. Even if most discussion will not be use to improve the page, it is a way to discus of the game, the builds, ...
Some exemples of comment section from other wikis : https://warframe.fandom.com/wiki/Oberon#articleComments https://genshin-impact.fandom.com/wiki/Kaeya#articleComments
--GKPlight (talk) 19:37, 30 July 2021 (UTC)

broken russian(?) links?

a lot of pages have broken russian links at the bottom of them. Do they serve some purpose? Can they be deleted? —Preceding unsigned comment added by Bloonpauper (talkcontribs) 03:47, 23 September 2021‎ (UTC)

Just leave them in the wiki. Ru-poe wiki is still in fandom. Neokowloon (talk) 14:05, 23 September 2021 (UTC)
Good day everyone, and who should I contact with the question of transferring the Russian-language project, to you?Kordloperdlo (talk) 05:44, 15 April 2024 (UTC)
Last time i heard User:Ruba159753 is not that interested to transfer to new wiki. For tech support i guess you better ask the question again in discord Neokowloon (talk) 14:11, 16 April 2024 (UTC)
If i have time i probably interested to write Traditional Chinese POE wiki. The realm has some interesting thing such as WTF with that translation. e.g. The Coast (Act 1) somehow swapped name with The Twilight Strand (Act 1). But i don't have time. Neokowloon (talk) 14:13, 16 April 2024 (UTC)

Skill lists category

Category:Skill lists should really be renamed to "Lists of skill gems", or at least "Skill gem lists". The name is misleading, and there's already Category:Lists of skills that does what Category:Skill lists sounds like it does. KickahaOta (talk) 21:08, 12 November 2021 (UTC)

I'm fine with renaming Category:Skill lists to Category:Lists of skill gems. —Vini (t|c) 15:30, 1 February 2022 (UTC)

Location information for keystone passive skills

Most articles in Category:Keystone passive skills have location information:

  • A description of where the keystone skill is in the passive skill tree.
  • Often, a table of how many nodes the skill is away from the starting area of each class.

All of this is handcrafted. As of 3.16, basically all of it is wrong. We need to decide whether to update this information for 3.16, or delete it. I would tentatively suggest "delete".

  • Description of where the skill is in the tree: There's already Ctrl+F in the PoE passive tree screen. Yes, it kind of sucks, because you've got to zoom out and scroll around and try to spot the slowly-pulsing thing. But that still seems like it's not likely to be slower than a text-based description.
  • Table of how many nodes away each class starting area is: This is potentially useful information. But even if it were correct, it's not expressed in the form that would make it most useful. Someone isn't likely to say "What's the class that's closest to this skill?" (And if they did say that, they could just look at the tree.) They're more likely to say "I'm planning out a Marauder; what keystone skills are within, say, 15 nodes?"

In theory, someone could use the connection information in the Cargo tables to write a really impressive data-driven module to show tables like "What other nodes of a given type are within X connections of this node?" That would be much more useful and would eliminate the need to handcraft this stuff. But given all the other to-dos on the pile, I don't see it happening. And in the absence of that, the handcrafted information seems like more trouble than it's worth. KickahaOta (talk) 23:10, 14 December 2021 (UTC)

How do you edit the infobox of a unique item?

When editing an item's page, there are data keys representing values, something like |explicit1 = SomeKeyName1. How or where do I edit this value?

Also, the Signature help page should be created. —Preceding unsigned comment added by Wicke (talkcontribs) 09:20, 29 December 2021‎ (UTC)

use adv search, untick main and tick modifier only , search using mod text as keyword, see are there any matching mod with "unique" as an affix in its id / page name. Alternatively , use cargo query in your user page sandbox. Also in case there is more than one result, usually new mod is for new unique so that new unique not likely using old mod id. Neokowloon (talk) 10:34, 29 December 2021 (UTC)
Also, except unique atlas region watchstone or the unique cluster jewel with random notables, the unique mod of the unique are in mod domain "3" despite the domain also contains implicit Neokowloon (talk) 05:02, 31 December 2021 (UTC)

Legacy variants section for fated unique items

On some of the articles about fated items, the legacy variants section is currently overloaded with other pseudo-variants that could theoretically exist if a legacy variant of the base unique item was upgraded to its fated counterpart during a later time period. I propose removing these pseudo-variants and providing an explanation about their existence instead. An example of this treatment can be seen on the Doomfletch's Prism article (diff). This does mean removing information from an article, but sometimes that can be a good thing if it makes the article read better. In this case, I don't think it's necessary or good at all to list every possible pseudo-variant that might exist in Standard. If someone is really interested in, for example, a Doomfletch's Prism that has the current explicit modifiers but no implicit, they can go search for it on trade. It doesn't need to be listed if it means sacrificing the article's readability. —Vini (t|c) 01:03, 1 February 2022 (UTC)

It is worse as some how some legacy mod are retained and sometimes it does not after 3.14~ish patch (aka ninja nerf). +6 FrostfernoFrostferno
Leather Hood
Evasion: (555-762)Requires Level 60, 46 Dex+2 to Level of Socketed Fire Gems
+2 to Level of Socketed Cold Gems
Socketed Gems are Supported by Level 30 Cold to Fire
(450-500)% increased Evasion Rating
60% increased Mana Regeneration Rate
+(20-30)% to Fire and Cold Resistances
Embrace your burning ambition.
Embrace your frozen heart.
You will be transformed.
must be created in perma league as the base item going to legacy before the release of fated item and there is only one entry so that this quasi-legacy fated item does not clutter the page. While Shavronne's GambitShavronne's Gambit
Scholar Boots
Energy Shield: (46-60)Requires Level 32, 59 Int+10 to Dexterity
+(20-30) to Intelligence
(100-140)% increased Energy Shield
(150-200)% increased Stun and Block Recovery
15% increased Movement Speed
20% increased Movement Speed when on Full Life
Regenerate 1% of Energy Shield per second
The Karui boats were closing the gap,
but Shavronne had laid for them one final trap.
, due to the ninja 3.14~ish change, i was told in the official forum, there are more than 4 variants. So that may be case by case? Neokowloon (talk) 01:12, 1 February 2022 (UTC)
That's interesting. I never knew about that change. Does that mean it became impossible to craft a +6 Frostferno in Standard after version 3.14.X? —Vini (t|c) 15:35, 1 February 2022 (UTC)
Too expensive to tell, as least i just break my legacy Kaom's WayKaom's Way
Coral Ring
Requires Level 32+(20-30) to maximum Life+(10-20) to Strength
Regenerate 0.2% of Life per second per Endurance Charge
Gain (2-4) Life per Enemy Hit with Attacks
+1 to Maximum Endurance Charges
2% increased Area of Effect per Endurance Charge
Kaom guided his Karui across the sea
and spilled their blood on foreign soil
only. So that probably GGG treated it as ninja bug fix. Yes the list is way too long if adding those legacy and double legacy fated mix and match, but i don't have a good solution in my mind, as some item like Kaom's WayKaom's Way
Coral Ring
Requires Level 32+(20-30) to maximum Life+(10-20) to Strength
Regenerate 0.2% of Life per second per Endurance Charge
Gain (2-4) Life per Enemy Hit with Attacks
+1 to Maximum Endurance Charges
2% increased Area of Effect per Endurance Charge
Kaom guided his Karui across the sea
and spilled their blood on foreign soil
and FrostfernoFrostferno
Leather Hood
Evasion: (555-762)Requires Level 60, 46 Dex+2 to Level of Socketed Fire Gems
+2 to Level of Socketed Cold Gems
Socketed Gems are Supported by Level 30 Cold to Fire
(450-500)% increased Evasion Rating
60% increased Mana Regeneration Rate
+(20-30)% to Fire and Cold Resistances
Embrace your burning ambition.
Embrace your frozen heart.
You will be transformed.
have only one more entry for these quasi-legacy / double legacy mix and match , but Shavronne's GambitShavronne's Gambit
Scholar Boots
Energy Shield: (46-60)Requires Level 32, 59 Int+10 to Dexterity
+(20-30) to Intelligence
(100-140)% increased Energy Shield
(150-200)% increased Stun and Block Recovery
15% increased Movement Speed
20% increased Movement Speed when on Full Life
Regenerate 1% of Energy Shield per second
The Karui boats were closing the gap,
but Shavronne had laid for them one final trap.
or Doomfetch potentially more than 4 entries if we insist to doc all. Neokowloon (talk) 02:53, 2 February 2022 (UTC)

Captured Soul page names

The captured soul items change names with the Atlas shuffle every league, but they retain the same flavor text and metadata ids. In order to reduce some of the workload for each league, I suggest using a more generic naming scheme for these items' pages:

Captured Soul of ArachnoxiaCaptured Soul (Arakaali upgrade 1 of 3)

Captured Soul of The Forgotten SoldierCaptured Soul (Ryslatha upgrade)

Vini (t|c) 17:21, 23 March 2022 (UTC)

Yeah i agree to have a static name. Neokowloon (talk) 00:18, 24 March 2022 (UTC)
GGG made a merry-go-round in 3.17 for Arakaali 's upgrades. So that probably redirect (the Captured Soul of "map boss name") to Captured Soul or Pantheon soul or The Pantheon may be better.
Sometimes the map boss is for this god in this league, but a few leagues before it is for another. So that redirect is tricky to handle
(copy my comment from discord) Neokowloon (talk) 10:52, 24 March 2022 (UTC)
Yeah, static name makes sense to me too Iamacyborg (talk) 10:46, 24 March 2022 (UTC)

Adding the various Archnemesis mod 'rarity' colours to the system

Its boring work and I would do it myself if I knew how, but considering we support the Bloodline and Nemesis 'rarities', could we add them for each of the new Archnemesis mods as it would probably help users identifying the mod that gave them trouble by it's colour, or in the situation where they were killed too fast to read the modifier's text. — RubyAxe 07:49 5 August 2022 (UTC)

It does not really help to identify the mod , as GGG did not announced in their website which color of the each mods. You either read the actual mod text or just one shot. For visualization it may be good to copy the in-game mod text color to wiki , but not really help on mod identification. (Unless people did not use Shadowplay, and just remembered killed one shot by color X mod , and try to narrow down the possible mods by color. ) Neokowloon (talk) 10:03, 5 August 2022 (UTC)

Updating passive skill info

I noticed that the skill description for Shadow Shaping was incorrect, and hunted down how to edit the info box. I found my way to Passive Skill:Atlas~keystone~disfavoured~maps and edited that, however it seems the update didn't propagate to any of the pages referencing it (Shadow Shaping, Atlas keystone, List of atlas keystone passive skills etc). How would I do that? -- CandyCorvid (talk) 01:39, 13 August 2022 (UTC)

Looks like it's been updated now. Not sure if I just needed to wait for it to propagate, or if someone pressed a button somewhere, but I'm happy now. -- CandyCorvid (talk) 01:43, 20 August 2022 (UTC)

Signature Help Page

I came here to make the above question about passive skills, but quickly realised that the Help:Signatures link was just a broken redirect to Gphelp:Signatures. Best I could do to fix it was just revert to a previous version before the redirect. Hopefully that's good enough for now; at least it has enough info that I was able to learn how to use signatures from it, but it might need some more work to fix the other broken links. -- CandyCorvid (talk) 01:55, 13 August 2022 (UTC)

Skill level missing data

How does one go about of adding/updating missing data from skill gem levels? At the moment Intensify Support is missing the stat_text for "Supported Skills deal x% more Area Damage with Hits per Intensity" at each level (and Vile Toxins Support is also missing a levelling stat_text). I am hesistant to update it manually in the info box, since it looks like the info boxes are automatically generated and a new export will probably undo the changes. Dreddie (talk) 08:05, 16 August 2023 (UTC)

It is something pypoe issue. Post it in discord or github. Neokowloon (talk) 10:49, 16 August 2023 (UTC)

Suggestion: Remove Template:Stub from the wiki

I would like to propose the removal of {{Stub}} from the wiki. The intended purpose of this template is to flag articles that are created as placeholders so that editors can find them more easily. However, I don't know that any editors actually use it this way. Category:Stubs ought to be empty or nearly empty most of the time, yet there are hundreds of articles flagged as stubs. Most of these aren't even flagged correctly. What tends to happen is that someone will create an article and flag it as a stub, and then no one will ever remove the stub template, even after the article is expanded. That makes this template not very useful in my opinion, so I would rather not have it at all. What do others think? Do you frequently view the stubs category to find pages that need to be expanded? Once you expand a page flagged as a stub, do you remove the stub template? —Vini (t|c) 19:54, 16 April 2024 (UTC)