Please be patient
Hey there! I see that you and Nihimon are making a lot of test edits, and I worry that we might we working in opposite directions. I am trying to set up a standard wiki infrastructure to auto-categorize feats and other mechanics using templates so that categories can serve as the primary searchable database. To do so, I need to get the templates established before all the data is imported or it will be more work for everyone down that road. When I get back in the office from recovering from my current bout of Gen Con con crud, I am going to talk to Stephen about getting an output from his master spreadsheet that is formatted for the templates I'm building. I understand the desire to get the data imported, but until there's a sustainable infrastructure for templates that uses named parameters, we're not ready for that step. I've left a similar message on Nihamon's wall. Thanks for your understanding, and sorry I haven't been more present on the site to establish this infrastructure—it's been a busy couple months leading up to Gen Con. — Yoda8myhead (talk) 04:32, 21 August 2014 (UTC)
Indeed we might be working in opposite directions; a key goal that Nihimon and I have is that it should be easy to make automated updates to the game mechanics once the new data is in. That basically requires that there be a data element somewhere that isn't intended to be formatted for or edited by users, and everything else needs to use that.
The ideal solution would be to have several templates that accepted the name of a feat as a parameter and output either a block or a table row containing that the relevant information from that feat's data page. The problem we encountered with that is that templates apparently cannot accept parameters that do that. (The use case would be something along the lines of "Template:Summary|Acid splash", with the Summary template describing the things we want on the summary, and able to pull those from the machine-writable data page for every feat.)
The hack solution that we happened upon would be making each feat's data page -be- a template that starts with a reference to another template; to display the summary information block for Acid Splash would then be "Template:Acid Splash|Summary", with each feat being a template that listed all of the information from the feat, and the Summary template parsing that for the information appropriate for the summary.
In either case, it is not an acceptable or sustainable solution to have to selectively update a large number of pages for each feat updated; If Acid Splash changes cooldown, we should not have to update every page that displays information about the cooldown of Acid Splash. Decius (talk) 00:21, 22 August 2014 (UTC)