User talk:Chieftain Alex/Archive 4

first--Relyk ~ talk < 00:00, 31 October 2013 (UTC)

Statues

Shouldn't they also be considered as animations, really? Because, you know, they are animated... MalGalad 19:23, 29 October 2013 (UTC)

looks like pretty clean cut images taken from ingame though.. which would be renders... and they're animated.. so they're both. (hence it categorizes them into both categories). Perhaps animated render would have been a better name for it though. -Chieftain Alex 19:31, 29 October 2013 (UTC)

hi.

Following the protocol laid out on the RfA page, I'm supposed to ask whether you wish to undergo an RfA. I can write up a pretty decent paragraph as to why I think you're a solid pick, but I figured I can just wait until the RfA launches to do that. Are you interested? -Auron 14:16, 7 November 2013 (UTC)

I'm spending 10+2 hours a day keeping up with my uni stuff (major deadlines start hitting me in 2 weeks - and I mean like 4 courseworks making up 8% of an entire degree), and I don't get weekends off. anything that keeps me here is damning my £60k education. sure I check RC twice a day, but I don't usually expect to find anything..

sure I'll do it. >.> -Chieftain Alex 18:20, 7 November 2013 (UTC)

baha xD poke | talk 14:15, 8 November 2013 (UTC)

weapon set table

I don't want to sound pushy, but can we implement {{Weapon set table}} as I implemented on User:Relyk/sandbox/weapon table. One reason being we should be able to reuse the template elsewhere, like in arbitrary tables such as {{Weapon stats row}}. I have a hard time looking at the code because you use variables and checks everywhere to make it work on a single template and some extra stuff. It shouldn't track what weapons are available in the set automatically and omit the section if it doesn't have one-handed weapons or aquatic weapons. The table should note if a certain weapon isn't in the set or a parameter for hiding aquatic weapons like we've been doing.

On another subject, we can start implementation with [[Property:Is part of equipment set]] and grab all the weapons in the set in one query like

{{#arraymap:{{#ask:[[Is part of equipment set::{{{set}}}]]|link=none|format=list}}|,|@@@|{{#vardefine:{{#ask:@@@|?Has weapon type|link=none}}|@@@}}}}

so it would only define a variable for the weapon types that exist in the set. We can already do this with the weapon set category too.--Relyk ~ talk < 00:19, 11 November 2013 (UTC)

the point is probably moot since Weapons stats table is barely used anywhere, and dr ish has said previously that he doesn't see a purpose to displaying weapon strength.

But really, the version I wrote could probably be rewritten to use one query, i.e.

{{#ask: [[Category:{{{1|{{PAGENAME}}}}}]][[Has weapon type::+]]
 | ?Has weapon type
 | ?Has canonical name
 | ?Has game icon
 | ?Has weapon strength | +index=1
 | ?Has weapon strength | +index=2
 | link = none
 | format = template
 | template = Weapon set stats table result format
}}

it would likely still need to use variables to count the number of entries that are aquatic / main hand / offhand / one hand etc, but you could do that with some inline queries instead I suppose.

If we used your version, we'd need a parameter to hide empty set types.. (example: {{User:Relyk/sandbox/weapon table|Aetherized Nightmare}} )

tl;dr version: both need rewrites. mainspace version is complex, but works perfectly. -Chieftain Alex 09:07, 11 November 2013 (UTC)

forgot something. I'd be very easy to do this if we had a property for sorting weapon sets into Axe, Dagger, Mace..... Spear, Speargun, Trident. (i.e. Axe=1, Dagger=2, Mace=3... Speargun=18, Trident=19) - this would allow us to sort the results. --Chieftain Alex 09:15, 11 November 2013 (UTC)

Now that I've seen the conversation on your talk page which occurred shortly after this one (should have linked me there!), I've removed the strength column from the table. I do agree with psycho-robot in that it is a long vertical table with not much point. I'd propose removing the table for pages with complete galleries (i.e. pages that already link to the individual weapons), or completely reconfiguring the table. --Chieftain Alex 09:24, 11 November 2013 (UTC)

By removing weapon strength (and adding an index property to sort by), it allow us to use <br> instead of rowspans, removing the need for all of the existing variables. -Chieftain Alex 10:17, 11 November 2013 (UTC)

I already said we should have a parameter to hide aquatic weapons if they aren't present and that we already do that elsewhere. We also don't need to have counters or rowspan variables or whatever, the weapon sets will always have all the weapons +/- the aquatic weapons. If it doesn't for whatever reason, we would say not available instead of removing the entry. I do not think we will ever need a parameter for terrestrial weapons because it's the primary game mode and most profession access most of the weapons, it just complicates the code.

The index property isn't necessary. Ishmael pointed out with Property:Has profession sort order we can use #arraymaps to sort it instead. I would love to sort the weapons alphabetically, but differentiating by terrestial/aquatic and handedness is still important. I would rather ignore handedness, but the weapons need to be grouped by terrestial/aquatic. A major reason is the aquatic weapons are missing from many sets and they are different game modes (obviously). I don't see the misgivings with a vertical table, it's a list of weapons. Not sure how much better a horizontal design is because of the look and issues that come with it.--Relyk ~ talk < 13:35, 11 November 2013 (UTC)

That did sounds pretty whingey/pushy :p , but it did respond to the stuff that took me four comments to make..

• If we're to reduce this template to only the icon, name and the weapon (/skin) type, then we can apply the same template to skin pages. Not all skins, e.g. Winter's weapon skins have every weapon.
• I'm fine with a parameter to hide the aquatic blocks, I was agreeing with you. I think that type "not available" however would be an ugly + lazy way of doing it.
• I'd love to see an arraymap sorted table. Can you give me an example of how do this? oh right. you're referring to User_talk:Relyk/Archive_3#Profession_sort_order.. which is cheating by doing the query 19x instead of once.
  • (the index property has the main advantage of being able to sort the initial query, and it can assist in calculating the rowspan for the one-handed/two-handed bit no wait we agreed we don't need that.)

-Chieftain Alex 14:02, 11 November 2013 (UTC)

What's ugly to me is coding to address edge cases like Winter's weapon skins when 95% of weapon sets/skins have all the weapons +/- aquatic weapons. Displaying terrestrial/aquatic/handedness isn't useful for weapon skins either. Having code that is really clever to address cases were there isn't a full weapon set is cool, but getting used maybe 2-3 times isn't worth it. If we had handedness and game mode properties on the weapon type pages, we could be a little more creative.--Relyk ~ talk < 14:44, 11 November 2013 (UTC)

(Reset indent) So I rewrote it completely. thoughts now? inbetween revision - I had a version with no variables and a parameterised off/on switch for aquatic weapons, but it didn't seem like a great leap to put it in a variable and check if its there or not instead. -Chieftain Alex 17:42, 11 November 2013 (UTC)

If you do it each section individually, you can skip the variables. I'm not sure on the double arraymaps, but that should be one arraymap (literally an if statement instead of having arrraymap do it in a second loop). Also, I'd like to switch handedness and game mode. It makes more sense to organize by game mode and the the handedness of the weapon types within the game modes. Because we are doing that, we end up with the redundancy that all aquatic weapons are two-handed, which is good as the original table is abusing that fact to simplify the table with no clear organization. Personally, it confused me somewhat.

Some new code: User:Relyk/sandbox/weapon table example. Because it's the same code for all the cells, #arraymaptemplate to format it correctly ({{#arraymaptemplate:<weapon types>|Weapon table cell format|,}}) maybe. We need the weapon set parameter and weapon skin parameter so that doesn't work.--Relyk ~ talk < 02:21, 12 November 2013 (UTC)

Ok I changed the double arraymap to single as sugested. Instead of "large icon" I used "Template:Weapon set stats table icon" because there should be a smw icon appearing - otherwise we get newfiles needed on sets with shared icons.

I think ultimately it should be a maximum of one query per weapon, whereas by using smw icon templates we're doing 19*3 = 57 queries, so we'd probs do something like

{{#ask: [[Category:{{{1|{{PAGENAME}}}}}]][[Has skin type::@@@]]
 | ?Has game icon
 | ?Has canonical name
 | link=none
 | format=template
 | template=Weapon set stats table item
 | outro=<br style="margin-bottom:1em">
 }}

Template:Weapon set stats table item:
{{#if: {{{1|}}} | <span style="white-space:nowrap">[[{{{2}}}|20px|link={{{1}}}|{{{3}}}]] [[{{{1}}}|{{{3}}}]]</span> }}<!-- same code as using {{item icon|large=y}} -->

for each row, I'd still really prefer it if it worked out if there were any entries, and then displayed the line

{{Weapon set stats table row|Off hand|<arraymap from above>}}

Template:Weapon set stats table row
{{#if: {{{2|}}}
 | {{!}}-
! rowspan="1" {{!}} {{{1|row header}}}
| {{{2}}}
}}

I've not used "outro" before. that appears between entries or just at the end? (quite happy with current version tbh) -Chieftain Alex 08:46, 12 November 2013 (UTC)

57 queries is not a significant issue. If we really cared, we'd create a {{item icon result format}} template with a userparam for whether it's a large icon. Outro is generated at the end only if there are results. There is only one entry for each query. This is all to avoid creating a formatting template when we don't need to. The if statement in Weapon set stats table item is redundant as the template is only called if there are results (First parameter always exists).--Relyk ~ talk < 09:11, 12 November 2013 (UTC)

not sure how useful this is, but we can put a pipe on the end of item icon and can get the large smw template by doing {{#ask:[[Category:Seraph weapons]][[Has skin type::@@@]] | link=none |format=template |template=item icon{{!}}large=y |outro=<br style="margin-bottom:1em"> }} -Chieftain Alex 13:06, 12 November 2013 (UTC)

(Reset indent) so, I did some testing on the unexpected success of passing the "large" parameter to {{item icon}} within the #ask. Disappointingly I can't change the names of the semantic output parameters, but I can pass page variables parameters whoops to it - which is still useful. -Chieftain Alex 15:47, 12 November 2013 (UTC)

That's almost like having arbitrary code execution as it's designed to have a formatting template and a userparam. I was using large icon as a dummy for a template we would use to format it.--Relyk ~ talk < 20:55, 12 November 2013 (UTC)

this conversation is stalling in terms of productivity. conclusions:

• existing "Weapon set stats table" has been simplified greatly - good.
  • accidentally learnt about a sneaky way to pass parameters to templates in the output of ask queries
• neither of us likes the other's formatting :P alex likes using 4 variables, relyk likes row templates.
• Might be worth seeing what other folk think about putting Aquatic weapons in a section below the other two handed weapons. GW2WT:WEAPONS?

one thing I hadn't thought of, now that the table only displays icons and names, should we rename the template to "Weapon set table" like in your heading above? -Chieftain Alex 21:05, 12 November 2013 (UTC)

I don't understand why you are using variables, you're simply transplanting code to the head and obfuscating what the code is doing. I'd say we don't need a template if it were obvious what it's doing, which it's not (One of the reasons you are using variables). I wanted to name it weapon set table from the start, so yup.--Relyk ~ talk < 01:24, 13 November 2013 (UTC)

missed this, thought the trigger was the comment below. I'm using variables since it allows me to test if the line has any icons in it before displaying it - removing the need for the "no aquatic" parameter. sure it could do the SMW query twice, but that'd be worse. I moved the variables out from the line since then the table looks much neater. -Chieftain Alex 00:17, 16 November 2013 (UTC)

I prefer having the parameter. you can explicitly show and hide the section, it won't confuse players on how to add the section, and allows it to appear by default even if the entries for the weapon set aren't added. It's worth having an explicit parameter rather than adding code to generate the section dynamically.--Relyk ~ talk < 03:16, 16 November 2013 (UTC)

In other news

{{#if: <!-- hide whitespace -->
{{#arraymap: 1h main, 1h offhand, 2h terrestrial, 2h aquatic |,|@@@|
 {{#vardefine:@@@|{{#arraymap: {{#switch:@@@
                                | 1h main = Axe, Dagger, Mace, Pistol, Scepter, Sword
                                | 1h offhand = Focus, Shield, Torch, Warhorn
                                | 2h terrestrial = Greatsword, Hammer, Longbow, Rifle, Short bow, Staff
                                | 2h aquatic = Harpoon gun, Spear, Trident
                               }} |,|$$$| {{#ask: [[Category:{{{1|{{PAGENAME}}}}}]][[Has skin type::$$$]]
                                           | link = none
                                           | format = template
                                           | template = item icon{{!}}large=y
                                           | outro = <br style="margin-bottom:1em">
                                           }} |}}
 }}
|}}
}}

teaching people to use arraymaps for everything since 2013. -Chieftain Alex 16:04, 12 November 2013 (UTC)

arraymaps have spoiled us.--Relyk ~ talk < 20:55, 12 November 2013 (UTC)

Houstone, we got problems

Recent release added two achievements with the same name. Wiki concatenates their fields with comma, resulting in breaking achievement header tl. Any ideas? MalGalad 00:29, 13 November 2013 (UTC)

yay fixed by adding a parameter to pad out the name of the subobject... (1 & 2) -Chieftain Alex 00:48, 13 November 2013 (UTC)

The whole point of using the achievement name of the subobject name was the assumption that the names were unique. /sigh--Relyk ~ talk < 01:50, 13 November 2013 (UTC)

Salvage Research

Some guy is interested in researching ectoplasm salvage rates (here) and I was thinking we could set up a standard template for that like we have with container drop rates. I understand it would vary based on the level of salvage kit, so we could separate them by level 2 headers. I tried to look at Template:SDRH to adapt it for this purpose, but its way over my head. What I imagine is something like:

Ectos salvaged	Crystalline dust	Luck (fine)	Luck (masterwork)	Luck (rare)	Luck (exotic)	Signature
1000	500	300	100	75	25	blahblah

Is that something that can be accomplished easily? Psycho Robot (talk) 00:23, 24 November 2013 (UTC)

Assuming that the user is only recording the items in the inventory after salvaging 1k items.. I guess we're automating a total row at the end. Additionally I'd say that we would have an additional row to calculate the amount of lucky pts the user could gain from the respective totals + use that to calc the average lucky pts gain for salvaging 1k ectos.

This will be WAY easier to do if we don't base it on SDRH btw :P (formatting is ok to copy, but the number of variables in SDRH + co is quite frightening) - meaning it'd only be used on the ecto page. -Chieftain Alex 00:44, 24 November 2013 (UTC)

Is there anywhere that gives a tutorial about how to actually add up entries in a table? If so I could give that a read and probably manage to do a not embarrassing job myself. Psycho Robot (talk) 01:01, 24 November 2013 (UTC)

The points to luck type of salvage kit is unnecessary, the quality of the Essence of Luck doesn't depend on the quality of the salvage kit. We do need a template for ratios, because people are interested in averages rather than probability to receive an item.--Relyk ~ talk < 01:16, 24 November 2013 (UTC)

(Edit conflict) Nope there isn't a tutorial. Here is what its doing:

Entry 1: {{/line|4}}
         {{#vardefine:Item1 running total|{{#expr: {{#var:Item1 running total|0}} + {{{1}}} }}}}
         Add 4 (the value of parameter 1) to running total, which is zero the first time that it is encountered.

Entry 2: {{/line|3}}
         {{#vardefine:Item1 running total|{{#expr: {{#var:Item1 running total|0}} + {{{1}}} }}}}
         Add 3 to running total, which was previously 4, so its now 7.

Total  : {{#var:Item1 running total}}
         This value is equal to 7.

this was way more obvious before we converted everything to use arraymaps in the SDRL template.

I've drafted something at Glob of Ectoplasm/salvage research. thoughts? -Chieftain Alex 01:19, 24 November 2013 (UTC)

The luck might not change with each type of salvage kit, but your chance to get luck vs. crystalline dust might be affected, and also the quantity of dust you receive might be affected too. As far as the draft, I like it but I don't think its important to note the ratios for each individual type of luck, just sum together all the luck which is received from salvaging x amount of ectos and divide by the amount of ectos salvaged, thereby returning a total average luck per ecto. Psycho Robot (talk) 01:22, 24 November 2013 (UTC)

Ok added the average luck per ecto count.

Splitting the table into kits makes it more complicated, but its manageable. You'd end up with (number of kits + 1) total rows at the bottom, each displaying different totals, e.g. grand totals + mystic salvage kit totals + basic salvage kit totals. I'd renumber the line parameters + require users to put signature in the first parameter, and kit in the second.

{{/line|~~~~|mystic|1000|300|100|75|25}}

| {{{3|0}}} {{#vardefine:Pile of Crystalline Dust_total         |{{#expr: {{#var:Pile of Crystalline Dust_total         |0}} + {{{3}}} }}}}
            {{#vardefine:Pile of Crystalline Dust_{{lc:{{{2}}}}}|{{#expr: {{#var:Pile of Crystalline Dust_{{lc:{{{2}}}}}|0}} + {{{3}}} }}}}

@relyk, we can make a generic version after doing 1 properly. -Chieftain Alex 01:37, 24 November 2013 (UTC)

I was just imagining that we'd have 5 separate tables, because the results from one kit has absolutely nothing to do with results from a different kit (except for mystic/masters which we would obviously combine). Psycho Robot (talk) 01:39, 24 November 2013 (UTC)

Variables tend to leak through the page, meaning if you use more than one table you have to delete all the variables individually at the end of each table. could do either tbh. -Chieftain Alex 01:42, 24 November 2013 (UTC)

We could put them on subpages and transclude them to the main page if that would be easier still, and would shirk the leaking issue. I think putting them in separate tables would be best both for reading the data and adding data to the table. Psycho Robot (talk) 01:45, 24 November 2013 (UTC)

that would transclude the variables ^_^ -Chieftain Alex 01:47, 24 November 2013 (UTC)

My life is over. Well in that case whatever you think is best. It certainly wouldn't be the end of the world if it was all in one table. Psycho Robot (talk) 01:51, 24 November 2013 (UTC)

I'm going to sleep. I've implemented my idea. reckon you can arraymap that template relyk? -Chieftain Alex 02:06, 24 November 2013 (UTC)

@psychorobot, variables are stored on the page. You have to design the templates to initialize the values.--Relyk ~ talk < 04:39, 24 November 2013 (UTC)

@alex, why do I have to arraymap it? you do it!--Relyk ~ talk < 04:40, 24 November 2013 (UTC)

I realised as I switched off that we could separate the tables if you like. I was stuck thinking about SDRH's issues, but since each variable has been annotated with the kit, we can have a table per kit if you want. -Chieftain Alex 09:39, 24 November 2013 (UTC)

[[User:Chieftain Alex/Templates/SSRH#Example]] - up and working generic version. funnily enough, because we've got those entries with luck in them, its a bit more complex than intended :p -Chieftain Alex 11:20, 24 November 2013 (UTC)

I think we can just have the guy estimate how many exos, rares, and masters he got, then fill in the rest with fine to reach the recorded amount of luck. We're not going to have a case where someone only knows the luck they got again, so no need to worry about it. Psycho Robot (talk) 16:44, 24 November 2013 (UTC)

the amount of luck per salvage might be interesting to know, there isn't really any reason not to let it be displayed there -Chieftain Alex 17:24, 24 November 2013 (UTC)

(Reset indent) Any opinions on how I put the header data in this time? Its not using the same layout as SDRH. -Chieftain Alex 17:24, 24 November 2013 (UTC)

I think it looks fine. I would say its easier to understand than the SDRH header stuff. Though I will say I think its redundant to include the full "basic salvage kit" in the salvage kit column, we could just have 'basic', and that would be fine. Who wants to type out salvage kits? That's for chumps. Psycho Robot (talk) 17:53, 24 November 2013 (UTC)

True, it doesn't matter what people call the kit, as long as all the people call the same item the same name.. e.g. you can't have one guy saying "Mystic Salvage Kit", another guy saying "Mystic kit" and another saying "mystic" + expect it to work :) -Chieftain Alex 18:16, 24 November 2013 (UTC)

Mystic and Master is the same thing, is there any way to combine those two, or shall we just instruct people to put "master" if they use mystic? Psycho Robot (talk) 18:25, 24 November 2013 (UTC)

They could type "Master/Mystic"... or "M".. or we could put an instruction at the top. (probably best) -Chieftain Alex 18:27, 24 November 2013 (UTC)

Can you apply whatever change you made to the salvage template in your sandbox to the ecto salvage template at Glob of Ectoplasm/salvage research/footer? I intend to post on reddit requesting people to add data and I don't think I should do that until I can remove the test entries without getting errors. Also note that currently the copper fed salvage o matic salvages with the efficiency of a master salvage kit. Is it a bug or not? Who knows... Psycho Robot (talk) 02:32, 30 November 2013 (UTC)

turing test

I don't suppose you could get AWB Alex registered as a bot, so recent changes would be less cluttered? (...not that there's a lot of traffic anyway...) Vili 点 00:45, 25 November 2013 (UTC)

If he passed the turing test, he would be not a robot. So you are asking him to be a failure. That's very unkind. Psycho Robot (talk) 00:47, 25 November 2013 (UTC)

granted it looks like most of the edits are entirely automated. would you believe me if I said that every edit with "prefix = ..." was filled in by hand from within AWB? (4 hours of buggy parameter fixing ><)

I doubt I'd be given a bot flag anyway. -Chieftain Alex 00:57, 25 November 2013 (UTC)

Regarding RFA

Don't break anything. - Tanetris (talk) 00:22, 29 November 2013 (UTC)

the wonderful thing about vector is it hides all the admin tools, meaning I didn't notice. Thanks guys! -Chieftain Alex 00:25, 29 November 2013 (UTC)

See? I told you, right? Welcome to the GW2W team! ;) poke | talk 00:46, 29 November 2013 (UTC)

Icon not updating

Hey, gz for the promote ^^ So right to the subject: I have been uploading and editing all weapons that don't have id neither icons, but now they are not updating lol for example this one Gear Assisted Longbow and the icons from this page are not updating too Rancher Jenneth. What can I do? ^^ --W.Wolf (talk) 00:53, 29 November 2013 (UTC)

Lol. perhaps write id and not icon :D -Chieftain Alex 00:56, 29 November 2013 (UTC)

Faiiiil lol I'm tired, already did a lot of icons today. Anyway Quickshot Short Bow not updating here Rancher Jenneth too. Ty lol -- W.Wolf (talk) 01:05, 29 November 2013 (UTC)

Yeah no worries. The issue with the short bow was that using two infoboxes generates a stored icon of "File:Crude Short Bow.png, File:Crude Short Bow.png"... when its only expecting one file. Use {{Fm table}} if you come across karma reward weapons with fine and masterwork variants of the same item. -Chieftain Alex 01:07, 29 November 2013 (UTC)

Ok. Thank you! --W.Wolf (talk) 01:09, 29 November 2013 (UTC)

Do you know how do I get skill icons having the id of the skill? --W.Wolf (talk) 00:43, 30 November 2013 (UTC)

well api doesn't do skills, so I don't know how to correlate the skill id with the icon id.

Its a long route, but if you can recognise the icon, then it'll be in User:Dr ishmael#Icon archives (128x128 files) (bottom of folder = most recently added icons) -Chieftain Alex 00:48, 30 November 2013 (UTC)

Ok, will do! Ty! --W.Wolf (talk) 01:03, 30 November 2013 (UTC)

Uploaded icons and edited all the 150 items that were missing the icons, only 1 remaining (will do it later). -Category:Missing icons Ty for the help ^^ --W.Wolf (talk) 08:25, 30 November 2013 (UTC)

I hadn't quite understood that the first time you wrote that (1AM..). Now I see that the category is entirely empty I'm impressed. well done!

Also, in the future when you move pages + leave redirects, could you just add the delete tag at the top + leave the redirect below (rather than removing the redirect) - this makes it easier for me :P -Chieftain Alex 23:50, 30 November 2013 (UTC)

Ok, I will do it in the next time lol --W.Wolf (talk) 02:17, 1 December 2013 (UTC)

given that when you delete files, they still hang around on the server, there isn't really a purpose to deleting all the duplicates + its really tedious for you to tag + I to delete. theres hundreds of the buggers :/ -Chieftain Alex 00:59, 2 December 2013 (UTC)

I think it's ridiculous to have hundreds of duplicates images e.g. [[:File:Wurm_Lodge_Longbow.png]] -20 icons with the same image. But if it's not usefull to clean all the duplicates, I stop then. Thank you for the typ!--W.Wolf (talk) 01:26, 2 December 2013 (UTC)

Congrats

I am pleased that you have reached the dizzy heights of adminship. Maybe if the scots go their own way then they'll have to change it to England. --Claret (talk) 08:56, 29 November 2013 (UTC)

I'd rather they didn't since anything that makes the frog faced politician sad is superb. But thanks for the vote of confidence :) -Chieftain Alex 09:35, 29 November 2013 (UTC)

If you don't delete shit I tag immediately, you're losing brownie points.--Relyk ~ talk < 12:32, 29 November 2013 (UTC)

If you don't delete stuff that I tagged for deletion 5 months ago… --Claret (talk) 12:44, 29 November 2013 (UTC)

195 down. The remaining ones ([[User:Chieftain Alex/CFD]]) are trickier.

The content of Template:Attributes nav (historical) + Daily Activity Participation can be reused.

Ectoplasm weapons / Category:Ectoplasm weapons / Category:Spirit weapons don't have a clear answer other than "delete and forget it ever happened"

List of vistas in Divinity's Reach - highlighted lack of city vistas linked from vista page.

File:Steam creature concept art.jpg may or may not be gw2.. -Chieftain Alex 19:52, 29 November 2013 (UTC)

Well done anyway. --Claret (talk) 19:54, 29 November 2013 (UTC)

We can't store multiple records in subobjects

User:Relyk/SDA is basically done but being able to use the sum format to generate those totals would be fantastic.--Relyk ~ talk < 06:18, 30 November 2013 (UTC)

dizzying numbers of arraymaps, subobjects and #ask you have there... so its fully working at the moment, but the footer would be simpler if you could use records in subobjects?

I've got my own drop rate problems at Form talk:Glob of Ectoplasm salvage research.. where I'm trying to put a formatted signature (like yours or mine) in a field + keep it without it screwing up upon the next form entry. -Chieftain Alex 15:10, 30 November 2013 (UTC)

I have a subobject for the header and one for each entry. I only make three different queries in the templates. That's enough to make your head spin? :P--Relyk ~ talk < 18:07, 30 November 2013 (UTC)

And yes, the point of the subobjects is so we can generate forms automatically and dynamically as well as remove the need for variables and the totals subobject like in {{SDRL}}and {{SDRF}}.--Relyk ~ talk < 21:44, 4 December 2013 (UTC)