Template talk:Cargo armor

Cargo Item Doubles
Hello, is there any way to get rid of doubles in cargo tables?

For example, I found that there is no "location" stat in declared armor infobox on all poe1 armors. So I added "location" to Elryn's Jacket and now we have 2 copies of Elryn's Jacket in Cargo Armor (You can check this template, there is a test Cargo Table with that problem) (and "location" seems still not working at all, though Template:Infobox_armor declaration have it). And that's sad. It seems that there is similar situation with Ryona's Vambraces, Cloak of the Tireless Defender, Nightshroud and others. I wanted to make armor lists same as lists for Deadfire, because there is slightly a mess in there and custom tables without using Cargo at all. That's why I started actually to deal with "location", but looks like Cargo is not so good as I mentioned before. If only there is a way to delete doubles. -- Preceding unsigned comment was added by Rinkata Prime (talk|contribs). Please sign your posts with -- .


 * This is a very common issue with cargo, with no real solution other than to wait for Cargo to resolve itself (which does eventually happen). I'm able to "regenerate" tables, but this rarely fixes the issue, and is not a very good solution if it has to be done all the time. I will try this tomorrrow. On affected pages, you can try "null edit" the page (submit an edit with no changes and no change summary), which sometimes can convince cargo to update and delete older entries. If you've ever edited a page with a cargo query, and have had it break after saving, this will also ensure that changes correctly display for you.


 * Regarding cargo lists, this is something I have planned to do after writing the ones for Deadfire (Template:Cargo weapons poe2, Template:Cargo armor poe2, etc.), but to do so requires a ton of re-sorting and cleaning beforehand. I'm already well into the process, so if you were thinking of starting to do the same, don't worry about it. The goal is to replace all the manually-entered data with queries from the cargo tables, but as I said this requires the pages to actually have locations in the infoboxes, which is not the case for many weapons and items (the field isn't even declared in Template:Infobox armor)


 * I was hoping to write a script to automate this, but there are so many unknowns it would be difficult to ensure its reliability. I'd ask that if you come across locations in any armor, weapon, item or shield page that aren't in the infobox, please move them to the "location" field of the infobox, creating one if needed. Macklin (talk) 22:04, 7 August 2019 (UTC)