Pillars of Eternity Wiki:Admin noticeboard

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.

Please post new topics at the bottom of the page by clicking this link to add a new section.

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:

IFNULL, CONCAT_WS, COALESCE

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. :) -- -- 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! -- -- 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 upgrades 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.

Weapons

• Blightheart - Cargo
• Marux Amanth - Cargo
• Magistrate's Cudgel - Cargo
• Lord Darryn's Voulge - Cargo
• Modwyr - Cargo
• Seeker's Fang - Cargo
• Slayer's Claw - Cargo
• The Weyc's Wand Cargo

Armor

• The Changeling's Mantle - Cargo
• Guardian's Plate - Cargo
• Robes of the Weyc - Cargo

Other

• Wintertide Bulwark - Cargo
• Survivor's Tusks - Cargo

---

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 …) -- -- You talkin' to me? -- cCContributions -- 16:21, 5 January 2019 (UTC)

Resolved Issues

Adding Extension:Array

Hi there, I am planning to do some work on SMW and add new semantic properties to items and enchantments. But to do this I need to use property value arrays and parse them.

Would it be possible to add and install Extension:Arrays?
I think that if we want to start making this wiki more semantic, we will need that extension sooner or later anyway. In particular, it is needed to solve this question I asked on StackOverflow. Which, basically, is really a generic need, if we want to depend heavily on SemanticWiki at some later time.

—FurloSK (talk) 14:34, 1 November 2016 (UTC)

Currently Array is not an approved extension for use on Gamepedia. In discussing with our developers, it could take a while to get added and may include some additional dev time since the extension is outdated. We are currently looking at Cargo as a replacement for SMW. You're welcome to check that extension out and see if it might suit your needs instead. --Alianin T •  C 22:07, 1 November 2016 (UTC)

Hi Alianin, after some reading & local testing, I can confirm that Cargo seems to be (almost) full replacement for Array extension. It is little more complicated, but I have found workarounds for everything I wanted to use originally. Drop me a message when the extension will be installed & available for use ;-) —FurloSK (talk) 06:17, 6 November 2016 (UTC)

Upload file: Licensing generates error

When choosing (at least) the game as license during the upload process, the following error is generated and the file not uploaded:

Exception encountered, of type "InvalidArgumentException"

[03af409b2960386721ec62d4] /Special:Upload InvalidArgumentException from line 246 of /home/hydra/stable_public_html/includes/Message.php: $key must be a string or an array

Backtrace:

#0 /home/hydra/stable_public_html/includes/GlobalFunctions.php(1391): Message->__construct(NULL, array)

#1 /home/hydra/stable_public_html/includes/context/RequestContext.php(457): wfMessage(NULL, ApiMessage)

#2 /home/hydra/stable_public_html/includes/specialpage/SpecialPage.php(705): RequestContext->msg(NULL, ApiMessage)

#3 /home/hydra/stable_public_html/includes/specials/SpecialUpload.php(697): SpecialPage->msg(NULL, ApiMessage)

#4 /home/hydra/stable_public_html/includes/specials/SpecialUpload.php(472): SpecialUpload->processVerificationError(array)

#5 /home/hydra/stable_public_html/includes/specials/SpecialUpload.php(206): SpecialUpload->processUpload()

#6 /home/hydra/stable_public_html/includes/specialpage/SpecialPage.php(479): SpecialUpload->execute(NULL)

#7 /home/hydra/stable_public_html/includes/specialpage/SpecialPageFactory.php(576): SpecialPage->run(NULL)

#8 /home/hydra/stable_public_html/includes/MediaWiki.php(282): SpecialPageFactory::executePath(Title, RequestContext)

#9 /home/hydra/stable_public_html/includes/MediaWiki.php(745): MediaWiki->performRequest()

#10 /home/hydra/stable_public_html/includes/MediaWiki.php(519): MediaWiki->main()

#11 /home/hydra/stable_public_html/index.php(43): MediaWiki->run()

#12 {main}

Adding the license later manually works.

While searching for the reason of the error, two additional things came into my mind:

1. Why is here no MediaWiki:Hydradark, as I know it from The Vault?
2. There has to be a bunch of un-licensed files – why is there no category for this? (And at the moment I don't know how to create it the way, it works automatically…)

CompleCCity (talk) 10:36, 14 December 2016 (UTC)

The file error is something we've been trying to chase down, but it's been hard to duplicate since it's so random. For now, just try re-uploading and the file should go through, if it hadn't already.

1. There's no MediaWiki:Hydradark because this wiki uses a light theme and The Vault uses a dark theme. That's the difference between the two.
2. I need to do an image roundup to tag all of the unlicensed images. I'll work that in with my other image stuff. --Alianin T •  C 20:13, 25 December 2016 (UTC)

Okay, I try again next time. Until now I simply added lic and cat already to the file description before uploading.

And thanks for pointing me to the visual – and also clearly visible - difference between the Vault and here. That's something that could have come to my mind by itself… :rolleyes: --CompleCCity (talk) 20:45, 25 December 2016 (UTC)

Interwiki

I suggest adding http://www.falloutwiki.com/$1 to the Interwiki list. The Vault has http://eternity.gamepedia.com/$1 on its own since October 2013 and lists this wiki as an affiliate in the main left navbar – I think, because VaultAusir is the founder of both wikis, and there's many parallels between both games' developers.

Also I suggest to add http://tyranny.gamepedia.com/$1, as it is from Obsidian and somehow related to Pillars of Eternity. --CompleCCity (talk) 18:06, 21 December 2016 (UTC)

Those were added to the interwiki. --Alianin T •  C 20:13, 25 December 2016 (UTC)

Thanks. Now I head on for the Tyranny Wiki and ask Tagaziel to add us to them… ;o) CompleCCity (talk) 20:30, 25 December 2016 (UTC)

Template:{{Quote}}

I've done some changes to this template – for a better look, I hope. What still bothers me is that much space between the quote itself and its author. Example:

“

There's so much emptiness here…

”

~ CompleCCity

But as far as I understand, a change would have to be done in the MediaWiki – where I haven't access to. So could please an admin take care of this? Thanks. CompleCCity (talk) 11:36, 25 December 2016 (UTC)

Pillars of Eternity II: Deadfire

Now that the sequel has been officially announced, we should support information and news about it appropriately. Hey – we're the Official Wiki! ;o)

• Adding the official forum to the main nav bar.
• Implement the game's Twitter and news from the forum on the main page, though the latter isn't a feed, yet.
• …

I haven't done such a thing before, always came into wikis much time after a game's release. So I have no experience on such a topic or how to do it and what more could/should be done. I suppose this would be a task for Alianin. ;o) -- -- You talkin' to me? -- cCContributions -- 13:34, 27 January 2017 (UTC)

User:Tagaziel has taken over as wiki manager here, so he should be alerted too, probably ;-)

—FurloSK (talk) 10:33, 28 January 2017 (UTC)

He already has been. ;o) -- -- You talkin' to me? -- cCContributions -- 10:41, 28 January 2017 (UTC)

Presumably there will also be some challenges in how to structure the wiki once Deadfire is out, and eventual more sequels. For instance, take class pages, like Ciphers. Bound to be changes to Powers and whatnot, so how should the pages be structured in the future? Divided by each game, or separate pages for POE1-ciphers and POE2-ciphers? Presumably the latter is a nightmare, and the former will lead to longer pages, but I suppose the former is better. I see that is how they have done it on the Witcher wiki (although I don't like how almost everything leads to category pages there, instead of a 'proper' Items page and so forth). Pangaearocks (talk) 02:44, 17 August 2017 (UTC)

String functions limits

As of recent wiki update, some pages are throwing "Error: String exceeds 1,000 character limit." or, worse, not executing properly without showing error.

Examples being:

• Gyrd_Háewanes_Sténes#Upgrades
• calling some templates that operate on strings, like Template:Property_values, fails silently, if some string they operate on is longer than 1000 characters.

I suggest increasing limits of these three variables:

• $wgPFStringLengthLimit to 5000
• $wgStringFunctionsLimitSearch
• $wgStringFunctionsLimitReplace

I know the limits are set for security reasons, but I am working for a long time on semantizing the wiki and 1000 string limit is too low for some specific scenarios.

According to discussion here, it is possible that increasing limit of $wgPFStringLengthLimit alone will suffice—please, test the mentioned Gyrd_Háewanes_Sténes#Upgrades page to see if the error disappeared.

—FurloSK (talk) 09:07, 3 July 2017 (UTC)

Dynamic tables: Formatting issues

Dynamic tables for various items is a very good idea, it's much easier to maintain, and they are sortable, but there is a problem with them: on almost all rows a "SEPARATOR" text field appears. I don't know how to fix this. Would also be grand if it was possible to remove Enchantments column for some tables, like in the Gems page. Pangaearocks (talk) 02:38, 17 August 2017 (UTC)

Preparing the Wiki for Pillars of Eternity II: Deadfire

With Deadfire (hopefully!) coming out in about 6 months, I think we need to think about how to structure the wiki for when there will effectively be boatloads (heh) of double info about weapons, armour, classes, items, creatures, even NPCs. I've looked into templates, but the coding there gives me a headache. I know a bit of coding, but the syntax is completely different to what I'm used to. Have also looked into templates because I find it odd the wiki doesn't have bestiary pages. Leaning on the Witcher wiki, because these are the two game series I've played recently, they essentially have an infobox for each game. So there is infoboxbestiary, infoboxbestiary2, infoboxbestiary3, and same for locations, weapons etc etc. I think we need something similar.

Starting looking into it with a mind to lay out needed properties, but tbh it looks like a Gordian knot with all that coding, and I don't know how different templates interact either. Below are two examples (don't know how to quote code without running it).

• https://pillarsofeternity.gamepedia.com/index.php?title=Template:Item_infobox&action=edit
• https://witcher.gamepedia.com/index.php?title=Template:Infoboxbestiary2&action=edit

Pangaearocks (talk) 20:07, 17 August 2017 (UTC)

I have created a category for restructuring the wiki: Category:Wiki_restructure. Didn't hear anything for over a week, so I've started the process now; in short making categories with Pillars of Eternity and Pillars of Eternity II prefix. Naturally this means current pages and categories must be edited too, so they point to the correct categories, but once this whole thing is done, the structure should be better for moving forward as a multi-game wiki. Some of the changes can be observed from the category root: Category:Contents Pangaearocks (talk) 20:26, 22 August 2017 (UTC)

I have moved the Categories restructure discussion to a more appropriate place – and will take part in it. -- -- You talkin' to me? -- cCContributions -- 08:37, 10 November 2017 (UTC)

P.S. Oh, and sorry for being this late. -- -- You talkin' to me? -- cCContributions -- 08:38, 10 November 2017 (UTC)

Cargo has been installed

User:Game widow was kind enough to install Cargo on the Wiki, which I'm very pleased about. It should be no problem to run both SMW and Cargo concurrently. The syntax of Cargo is less complex than SMW's, it generates tables automatically, and it's pretty straightforward to query the Cargo tables and generate output in whatever format you like.

There is an example page here, which queries a few examples and puts them into an example table. It uses this template (I had to put it in the main namespace, otherwise Cargo didn't recognise the template as a template; see here.

Important aspects to consider

There are a few differences from SWM that we need to consider when designing/updating templates and managing the data. Please check this migration guide for more information.

• Cargo does not allow spaces in field names
• Text values within queries need to be enclosed within quotation marks - single quotes (i.e., apostrophes) are preferred. See example below, with emphasis on the apostrophes around '{{PAGENAME}}'
  • {{#cargo_query:tables=Cities|where=Country = '{{PAGENAME}}'}}
• Some data types have been split up to enable more options, while others have been created
  • File → New datatype
  • Wikitext → New datatype
  • Datetime → New datatype
  • SMW's Number has been split into → Integer and Float.

I'm quite excited about this because it should make handling all the templates and data on this fairly big wiki easier. I'd love to hear what you guys think about this though, and whether we should, in time, aim to migrate the whole wiki to Cargo. I know especially User:FurloSK has put a lot of work into items and their templates. I'm new to this place, but it looks like he has been very active, and I noticed there was brief talk about Cargo earlier, so I'm looking forward to feedback :)

Since I've been working on creatures, I'm going to implement Cargo in the template as a start. Pangaearocks (talk) 15:04, 27 August 2017 (UTC)

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? -- -- 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 … -- -- 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)