Talk:Leather Armor (Deadfire)

From Pillars of Eternity Wiki
Jump to: navigation, search

Leather Armor is also in Pillars of Eternity I not just only in PoE II it would be best to separate this a lil bit better.

--Arawn76 (talk) 19:14, 30 September 2018 (UTC)

Good point! Perhaps just by moving it to Leather Armor (Deadfire) without redirect? This also highlights a bigger issue with pages like Leather armor - which talk about leather armor as a type of armor in poe1 and not poe2. I think this is fine, since the article contains stats that only apply to that game. My two cents is to make a new page Leather armor (Deadfire), which talks about leather armor as a type of armor in poe2, and then also change the name of this page to add the disambiguation.
Armor types in poe2 don't yet have their own page. Looking at Armor (Deadfire), it contains the following links, all of which link to the pages for the specific items in poe2. Drop the "(Deadfire)" and capitalization, and you get the page for the armor type in Pillars of Eternity.
I think my suggestion of creating similar pages to this for poe2 makes sense. However, we run into issues when it comes to single-word armors like Robe and Brigandine - where the name of the proposed page "Robe (Deadfire)", would conflict with the item page of the same name. While the current poe1 pages deal with this by incorporating the base item into the armor type page itself, I think this isn't good design - since it makes the listing of information about the specific item seem unrelated and out of place. I'm not sure what the best option is for this, but here are some options:
  • Change the name of the armor page, e.g. "Robes (Deadfire)", "Robe (armor in Deadfire)", "Robe (armor type in Deadfire)", "Robe (armor type) (Deadfire)", and keep the item page "Robe (Deadfire)".
  • Change the name of the item page, e.g. "Robe (armor in Deadfire)", "Robe (item in Deadfire)" and keep the armor page "Robe (Deadfire)".
Another option is to change the existing armor pages for poe1 to be more generalized and include the information about armor types in both games. This option might make sense since every armor and item page already links to the poe1 type page, and would prevent us having to change the infobox to fix this issue. We also wouldn't have to worry about the issue as described above (other than for the base poe1 items). On the flip side, we then introduce conflicting information. The page would probably devolve into a stats table of every single armor of that type in both games, which isn't always a bad thing.
We could also change all armor pages to something like "Robe (armor type in <game>)" or "Robe (armor in <game>)", making the page "Robe" a disambiguation page which all current robe items already link to.
I try to avoid making changes like this by myself, since it becomes difficult without unanimous decision making.
--Macklin (talk) 07:10, 1 October 2018 (UTC)
I figure it's better to ask forgiveness than permission. A plural, followed by the subtitle, feels like the right choice. Tagaziel (talk) 17:31, 1 October 2018 (UTC)
You're right, this is a community driven site after all. But it's still good to get opinions. In this case, the single word armor type pages would be "Robes (Deadfire)", "Breastplates (Deadfire)" and "Brigandines (Deadfire)", the rest would be "Xyz armor (Deadfire)" - since the plural form of armor is the same. The infobox links can probably be handled later, as they should link to the type page for the specific game. --Macklin (talk) 11:04, 2 October 2018 (UTC)


Arawn76 wrote:

But back to the topic. I think easiest way is to separate one item in two games of a serie when you try following structure:

For example

[Main Page] https://pillarsofeternity.gamepedia.com/Leather_Armor

Leather Armor is a leather armor in Pillars of Eternity and Pillars of Eternity II: Deadfire.

Description[edit source]

Items in italics are quoted directly from the game.
Insert the description here, without quotation marks.

Leather Armor in Pillars of Eternity I[edit source]

Stats:[edit source]

Template:Text

Acquisition:[edit source]

Template:Text

Leather Armor in Pillars of Eternity II - Deadfire[edit source]

Stats:[edit source]

Template:Text

Acquisition:[edit source]

Template:Text

Gallery[edit source]

Template:Empty

References[edit source]

References[edit source]

And the Infobox need to be out of two windows one for POE I and one for POE II

The advantage is you need no redirect, can still use the same link in both games and you have an overview what changed.

Arawn76 (talk) 16:31, 3 October 2018 (UTC)


I'm guessing you're talking about having the one page contain content related to the specific item in both poe1 and poe2. I understand your reasoning, since it would make looking up content easier, would remedy the structural issues that we're seeing, and would benefit to the overview of an item - but I have to disagree with this approach.

Using a single page works for characters, factions and other lore-related things that span across both games (and would therefore benefit from having the information centralized). Items don't really have the need for this, since their use is specific to the game they exist in. I doubt many people who are looking for where to buy Leather Armor in Deadfire would care about where to buy Leather Armor in Pillars of Eternity. There isn't much connecting the two besides the name - and for that we can just use a DisambigMsg pointed at the other page, telling the user that the item also exists in the other game.

Not to mention, this approach introduces a ton of clutter, and would require changing potentially thousands of pages.

Perhaps in the future when there are a few more games, this will be necessary - but I don't think we'll have to worry about it for a while, and by then it'll probably be someone else's problem :p

--Macklin (talk) 04:45, 4 October 2018 (UTC)


Hmm it depends would i say, cause if a game starts to be consisting of more then one part, you need to keep the structur easy, to avoid complex references. Especially if more then one person works on it. Changes are minimal and not worse if done in predictable advance right. ^_^ But so far let's just see how far this child grows. XD

Arawn76 (talk) 13:18, 4 October 2018 (UTC)