Template talk:Achievement table header

Race condition

I suspect there's a race condition between this template and the row template that routinely messes up our mastery point calculations. Tempted to rewrite to remove dependency on header. -Chieftain Alex 06:41, 28 June 2017 (UTC)

If we start documenting the IDs and type of mastery point as in the API we can filter out the duplicates when counting them. Any idea why we have achievement SMW data created by the row template instead of an infobox like we do with items and skills? J.Tesla (talk) 20:36, 28 June 2017 (UTC)

I don't think every achievement needs its own page. That's the only reason we use a table instead.

I've done a pretty chunky rewrite on the row template which should mean the mastery points no longer bug out with duplicate subobjects, however we need to avoid using #ask or #show to query the current page. This has meant resorting to #var_final instead (which does not allow any parser functions to edit its value). I've removed the mastery point header because it'll display 0  without any mastery variables being set. -Chieftain Alex 21:01, 28 June 2017 (UTC)