Pillars of Eternity Wiki

In response to patch v1. to Pillars of Eternity (June 6, 2024), the random loot tables shown on the wiki have been updated. These changes may take time to propegate.

As a result, random loot data is no longer accurate to old versions of the game, including all console ports. We'll be working to provide a mechanism to switch between pre-patch and post-patch loot for console players.


Pillars of Eternity Wiki

The Admin noticeboard is one way through which users can notify administrators of issues needing administrative attention. While users are welcome to directly contact specific administrators (especially if they are seen to be active), posting here can be an easier and quicker way of ensuring that at least one admin will notice an issue and respond to it promptly. Remember to sign (using four tildes: ~~~~) when posting an issue.

Before posting an issue here, please consider the following:

  • This page is for reporting wiki issues. Please post discussions on the talk page.
  • Post only issues that require administrative action, i.e. blocking vandals, protecting pages, restoring deleted pages etc.
  • Do not post deletion requests here. Deletion requests should be made by adding {{delete}} to the top of the target page, which will then automatically mark the page as a candidate for deletion.
  • Do not post issues regarding content disputes. Try making a request for comment instead.
  • Mediation requests between users should only be made once a resolution could not be reached between users.
  • For issues regarding the use of this wiki, please see our help center.

In case of vandalism, posting about it here is low priority. Revert it first, anyone can do so. If the vandal created a new page, tag it for deletion. Assume good faith and consider leaving a message on that user's talk page to explain the reason. Post here only if the user has made several disruptive edits and/or persists despite a warning. Always avoid a revert war with the vandal; it is far better to wait until an admin has a chance to intervene. If a user must be reported here, please use {{user}}, preferably as the topic subject/headline.

Archived Issues[]

Resolved Issues[]

Pages not getting added to categories[]

I've noticed a few times that when I make an edit which changes a category of a page, or adds a new one, the page doesn't appear in the category. The few examples I've seen first hand are Mega Boss Battles, Mega Boss - The Voracious Mountain and a number of edits I just made to place some templates into Category:Abbreviation templates (see recent changes log). These pages don't show up in the associated category, no matter what I try - cache purge, null edit, nothing. Is there any solution to this? Macklin (talk) 15:57, 13 December 2018 (UTC)

This also has occurred with pretty much every item under Category:The Forgotten Sanctum. Macklin (talk) 21:01, 14 December 2018 (UTC)
Is this still the case? -- UserCCCSig -- You talkin' to me? -- cCContributions -- 15:58, 2 January 2019 (UTC)
This happens very often - especially when adding many new pages at once. I've found it solves itself over time. I think it's just a case of letting the server catch up. Macklin (talk) 16:09, 2 January 2019 (UTC)
It's said, time heals all wounds. ;) Thought, it might be something like this … -- UserCCCSig -- You talkin' to me? -- cCContributions -- 16:25, 2 January 2019 (UTC)
This was a bug that occurred a while back. It was resolved, so I just moved it to resolved. :P Tagaziel (talk) 15:32, 3 January 2019 (UTC)

Current Issues[]

Request to add a few SQL functions[]

Recently I was fine tuning Template:Cargo enchantment item poe2, as I found an oversight in the retrieval of enchantments. I don't want to get into it too much (I cover this here), but the problem is the need to merge two cargo list fields into one in order to display both weapon_bonuses and curr_enchantments in the "Enchantments" field of the generated row. An example of the need for this can be seen in Unstoppable Shot, where only the enchantments in the that field are shown, instead of all enchantments on the weapon.

In cargo, they want you to use the CONCAT function to accomplish this, for example:

CONCAT(Weapon_poe2.weapon_bonuses__full, ';', Weapon_poe2.curr_enchantments__full)

However one stupid behaviour of CONCAT is that it returns null if any parameter is null, and would require a complex query just to circumvent that behaviour (this possible with the subset of enabled keywords in the wiki). A solution I've found online is to use CONCAT_WS, however I can't confirm that it's going to work.

So I'd like to ask if the following function be enabled, just to cover some of the possible solutions:


It looks like the setting wgCargoAllowedSQLFunctions in LocalSettings.php holds the allowed values.

Otherwise if anyone has a better solution than adding keywords, I'm up for suggestions. Of course, moving to a universal field would solve this issue entirely.

Anyway, I hope this was the right place for this. I never know where to post certain topics. If not, feel free to move it to wherever is more suitable. Macklin (talk) 15:57, 13 December 2018 (UTC)

Place is okay.
I have to admit that I'm currently too out-of-the-game (and don't see high chances of getting back into it in the near future, due to PC issues and more) to have a real opinion on the merge of those fields. As Tagaziel already suggested a merge of the fields – why not?
As for the functions to be enabled … I think, I've seen some settings for Cargo somewhen, somewhere, but can't find them again. However, I think this can only be done by our wiki manager, not by a simple sysop, so it's good I pinged Tagaziel in the above lines. :) -- UserCCCSig -- You talkin' to me? -- cCContributions -- 17:04, 2 January 2019 (UTC)
To be honest I'm just annoyed by the issues that having separate fields has brought up (to where we need to be doing fancy SQL stuffs in order to get the right results). You did mention that you'd come back with an opinion on the universal field stuff - but the more I think about it, the more problems it would solve. As I mention in the link, perhaps we can do this with a redesign of the enchantment infobox, updating it for poe2. Of course it won't be a small undertaking, but one that I think is necessary. I will make a point to draft something up. In the meantime, adding these SQL functions would be more of a temporary fix than a permanent one, but I'm sure there are other future uses that enabling them will serve. Macklin (talk) 17:22, 2 January 2019 (UTC)
I thought of another solution to the initial problem (I used it in the cargo weapon/armor/shield templates), and just added it. Not as clean, but it works at least. Macklin (talk) 11:44, 4 January 2019 (UTC)
I'm not sure I understand all what you have done there. I also don't understand why this wouldn't be "as clean". But to me it at least looks good – very good. (I like especially the new list of unique armor (Deadfire).) I think, you're doing some really great work here, Macklin! -- UserCCCSig -- You talkin' to me? -- cCContributions -- 16:04, 4 January 2019 (UTC)

Soulbound items never being updated in Cargo[]

Close to every single soulbound item in Deadfire refuses to update in Cargo. I observed this issue a couple of months ago, but it hasn't since fixed itself. The issues aren't seen on the pages themselves, but in any cargo queries that retrieve data from the tables e.g. List of unique armor (Deadfire), with the top two items. I'm not certain, but I think this also carries over to poe1, as well as the cargo table Special:CargoTables/Soulbound_upgrade_poe1.

It's difficult to say exactly what the cause is without looking at any logs or anything behind-the-scenes, but I have a theory - albeit based on zero evidence - that it is because of the use of multiple Cargo stores in a single page. This is really the only thing that differs from regular pages, so I think it's a good guess.

Some others have recently been having problems with Cargo not updating tables, but their issues seem to span across an entire table, while this is limited to specific pages. Maybe that link will help, maybe it won't.

Here's what I would suggest in a brute-force attempt to fix it:

  • Remove Template:Soulbound upgrade from each of the pages (I tried this with Robes of the Weyc, but doing this alone made no difference)
    • The above, then recreate the associated Cargo table AND/OR recreate the Soulbound upgrades table.
  • Delete, then re-make the pages (loses edit history on the page itself, but should still be listed in user contributions - not sure). Might make duplicate rows in cargo.
    • Delete, then recreate the table, then re-make the pages.
  • ...

The following is a list of soulbound items and links to their pages - as well as a query which demonstrates missing data.


Some initial thoughts about this from me:

  • First, a deleted page can be restored – together with its history.
  • Wouldn't it make sense to split the Template:Soulbound upgrade (you used the deprecated one, with "s", in your post, Macklin) into versions for both games? Though I guess, this alone wouldn't change much on that topic …
  • I could verify that recreated Cargo tables include later changes to the items, but still don't update if another edit is made. (There's still an issue with populating replacement tables – way too few items in them, and null edits apparently don't help always …)
    • But always recreating data can't be a solution.
  • If you're right with your assumption of the root of the problem, Macklin, then would it possibly help to use different parameters in the soulbound template, ones that use other names than the infobox for e.g. value – naming it sb_value, for example? (You've far more knowledge about Cargo than me …) -- UserCCCSig -- You talkin' to me? -- cCContributions -- 16:21, 5 January 2019 (UTC)

I meant literally copying the source text out, deleting the page, creating a new page with the same name, and then pasting it back in. Understandably the history would be erased.

Personally I never really liked Template:Soulbound upgrade (didn't even know there was a previous one "upgrades"). It's sort of just another cargo table that doesn't need to be there. I much prefer the idea of this data not even being stored in any way, since the only thing that uses the table is Template:Cargo enchantment item poe2 (and only because the enchantments aren't stored in the infobox). If I were to think about a better solution, it would be to incorporate soulbound upgrades into the infobox itself, either fully and make the table dynamically generated from the infobox, or just use a manual table and store the soulbound upgrade enchantments in the infobox so that the aforementioned template can know what item the upgrade enchantment belongs to. poss_enchantments isn't really used often enough, so I say change it's type to a List (;) of Page and use it in the same way curr_enchantments is. But this discussion isn't really about how to better Soulbound upgrade, and I very much doubt changing it in any way - like the names of the fields as you said - would do anything. Though in saying that, things have been fixed over weirder quirks, so who knows.

Recreating the tables isn't a fix in the slightest, I agree, but since there's a low chance of any more content being released, taking this option can't hurt if it means not having to worry about it for a while. I know a bit about how to use cargo from the user end, but nothing if it's inner workings and exactly how and when rows are updated, created and deleted to know what kind of outcome doing certain things has (or at least should have). This makes pinpointing exactly what to do next to impossible. In addition to this (and not to be rude), but I don't think any admins with the sort of permissions to do so will see this as a serious enough problem to warrant even looking into on a more technical level, so a "shotgun" approach is all I can suggest (feel free to prove me wrong!) Macklin (talk) 17:15, 5 January 2019 (UTC)

[…] incorporate soulbound upgrades into the infobox itself […]

This one sounds very VERY good. ;)

What's the difference between recreating an article, as you described, and restoring it?

"there's a low chance of any more content being released" – the issue is not only about new items (are they all complete on the wiki?) – it's about updates. And besides possible future patches, there are always updates to the articles, such as the locations …

Why do you think I've more than end user knowledge about Cargo? The only thing – as far as I know – that I am able to do else than you is (re)creating the tables … And sometimes I'm a bit naive when it comes to "rudeness" – you'd have to elaborate that last sentence for me to catch the meaning. -- UserCCCSig -- You talkin' to me? -- cCContributions -- 17:44, 5 January 2019 (UTC)

Oh, sorry I read "First, a deleted page can't be restored" instead of can be. Ignore my comment.

And yes, I know that all items aren't complete - but this problem is restricted to soulbound items, and I'd say that those are generally complete (aside from location). Regardless, you are right - we never know when a something might be updated for whatever reason and shouldn't assume.

That last point was sort of offhanded, I meant an admin that has access to logs and stuff at a low level probably won't see this as serious enough to take a closer look, so as far as I'm concerned actually pinpointing the exact fix (without such an admin's help) is next to impossible unless we just happen stumble across what triggers the problem. So really we're just blindly testing stuff and seeing what happens, not exactly the best way of going about things. Macklin (talk) 18:16, 5 January 2019 (UTC)

Proposal for withdrawal of administrative rights[]

As Pangaearocks isn't a wiki administrator anymore since about a year, I don't see the need for his bot of still being one. Tagaziel, would you please change his rights, or do you think otherwise? -- UserCCCSig -- You talkin' to me? -- cCContributions -- 11:32, 7 January 2019 (UTC)

If it's been a year with no contributions, then we can put him off duty. He'll get them back on requests. Any objections? Tagaziel (talk) 09:16, 8 January 2019 (UTC)
Pangaearocks' last contribution: January 13, 2018
Pangaearockbot's last contribution: December 16, 2017
Why was his bot granted sysop anyway? -- UserCCCSig -- You talkin' to me? -- cCContributions -- 13:26, 8 January 2019 (UTC)

There's another one: ArksBot – bot with sysop rights. I have no idea whose bot that is, and its last (and only) activity was on April 1, 2015. At least sysop should be revoked. -- UserCCCSig -- You talkin' to me? -- cCContributions -- 18:52, 13 January 2019 (UTC)

According to User talk:Alianin#Bot account, it's AnotherArk's bot. Not active since April, 2015, as well. -- UserCCCSig -- You talkin' to me? -- cCContributions -- 20:26, 13 January 2019 (UTC)

Ad testing notice[]

Please note that we are testing an improved ad unit on this wiki starting tomorrow, June 11th. Details can be found here. --Misterwoodhouse (talk) 19:19, 10 June 2019 (UTC)

UCP migration issues (list)[]

Figured I'd list some stuff I've found so far. I'll add more as I find them:

  • Font Manager errors out, local fonts like EBGaramond12-Regular seem to be missing (see MediaWiki:Hydradark.css). CSS fonts loaded from an external site (like in Template:Tooltip ability poe2) work fine.
    • → Removed local fonts from MediaWiki:Hydradark.css and changed styles in Hydradark.css and MediaWiki:Common.css to use external fonts. There are some pages which still define the old font-family in html style attributes, and so far I've changed Official Pillars of Eternity Wiki/Top section and‎ Template:Mapnode. If the Font Manager is fixed at a later date, the existing font declarations can be changed to local ones and just keep the same name. I'm not actually sure if there are benefits to local fonts from the perspective of the end user anyway.
  • User profiles not working. Intermittent, sometimes just takes a really long time to kick in.
  • Achievement data reset, not really an issue.
    • → Working fine now.
  • MediaWiki:Hydradark.js not executing? Need to validate.
    • → Working fine now.
  • "This is a minor edit" / "Watch this page" checkboxes in the source editor are a bit strange.
  • Ad space "btflb" (below the category list) is present on PRO. It doesn't show an ad, just the reserved space.
    • I've added a one-liner to MediaWiki:Hydradark.js to remove this for PRO users only (I've tested to confirm this). If the element with the id "bottom_leaderboard" doesn't have the class "gpt-ad", it will delete its parent element with the id "btflb". gpt-ad seems to only be present on bottom_leaderboard when logged in as a PRO user. I'm sure there are some ways to more properly query whether the logged in user is PRO or not. I couldn't do this in CSS alone since the existing display property on that div has the !important flag (and takes precedence). This solution is kinda hacky and might be against ToS, so it's only really a temporary solution.
    • Improved solution to use proper API checks, but still kinda hacky.
    • → Working fine now.
  • Site in search results is "zoomed out". Seems to be a result of the generated CSS font-size: 14px on the body element cascading down.
    • → Fixed in MediaWiki:Hydradark.css with .mw-special-Search { font-size: inherit; }
    • → Undid above fix, fix was made Fandom-wide.
  • Special:Preferences doesn't use Hydradark styling at all (not even sure if it did previously). This one is a bit beyond me.
    • → Working fine now.
  • "Official Wiki" button in the top bar leads to a page that no longer exists Special:AllSites (&filter=official). Not sure if there's a Fandom equivalent, or if the link should just be removed.

Also yay for Scribunto and other fun stuff! Macklin (talk) 17:23, 23 September 2020 (UTC)

Fandom Mobile issues (list)[]

Issues with the new default mobile interface (FandomMobile) should be listed below. Since these styles can only be changed by the Wiki Manager, more immediate fixes will probably involve substituting complex styles and formatting with those that can better translate to Fandom Mobile.

Some pages will not function properly on mobile at all, and currently cannot be fixed without removing the offending content for both platforms. If you wish to revert to the old MobileFrontend-based skin, you can do so by toggling the pop-up that appears on your user profile.Macklin (talk) 20:07, 31 January 2021 (UTC)

  • Some styles that enable functionality need to be copied over. A lot can be omitted, but pages like Pillars of Eternity world map that rely on classes poe1map, px1map, poe2map, etc currently do not work.
  • jsonly, nojs, mobileonly and nomobile styles should be copied from MediaWiki:Common.css and MediaWiki:Mobile.css for pages which have separated content for mobile and desktop. Right now on mobile both content is shown.
  • img max-width:100% style causes a lot of issues with image sizes in tables, especially if they need to be a fixed size.
  • Some Template:Cols probably need to be adjusted, like in Crafting (Deadfire)
  • Template:Colitem not working properly
  • Template:NPC_infobox probably needs to be updated to the new infobox (it's about time too).
  • Deadfire abilities (Template:Family tree) appearance.
  • Template:Nowrap (and white-space:nowrap) elements overflow table cells.
  • Infoboxes that use multiple columns per cell (like Template:Infobox armor poe2, or those that use hacky formatting tricks) do not translate well.
  • User links don't redirect to UserProfile if a their user-namespaced page doesn't exist.