kyussinchains wrote:
Leave as-is..... the tau list are an exception in that they have an approved list and a separate develpmental one being tested, if this happens with other lists it's not a big deal to accomodate them as we have done with the tau
Well, how it works for Tau is exactly how it should work for every approved list... the only difference is it's actually properly versioned, and then labelled as "developmental" whereas most other playtest lists exist in some sort of limbo without a label. Whether you call it developmental/playtest/whatever makes no difference, any Approved army can (and should) have both a stable version - the version in the compendium or tournament pack - and a playtest version.
At present I think Tau is the only playtest version of an approved list represented in armyforge. If there is no impetus to add them then there's no real need to make any changes, but I suppose it could be that no impetus exists because previously it has not been possible
It seems there was a reason to do it for Tau after all.
Personally though I don't see why in particular it is necessary to clobber old versions when updating a list - just copy it instead (XENOS_tau_NETEA_6.6.json). The index can just point the default (i.e. the latest stable version) and the interface have a drop-down to allow you to change to whichever version you want. This seems like almost a "might as well" situation. By the way as a bonus, versioning the save links would mean reloading old saved lists could be made to work properly.
