Der Wiki

[parcel]

Because information about classes tends to change with every release, I think it's a really good idea to have the wiki available for basic spoiler information and gameplay guides. But what if we doubled down on this reasoning? Would it be a good idea to have the wiki set up so that current version-in-play of a revision is tracked?

[darkgod]

What do you mean ?

[Zireael]

I think he means setting up a tag that would say: "Last updated for version x.x.x" for those wiki pages.

Amirite?

[parcel]

Correctomundo. If you got really ambitious you could build off this, color-coding major point releases and using some keywords in the changelog to help signal which talents/classes/items/etc just got a major overhaul, thus making it likely that the existing wiki pages on these topics are out of date.

[Edit] What may be getting you about the ambiguity in the OP is that I was being deliberately ambiguous. A tgeagging system might be easiest to develop since that's been done elsewhere, but other approaches would work too. When I look at a recent changes page, I get the exact date of edits down to the very second. Similarly, when I look at revisions, I can figure out exactly how long it has been since the page was last updated. But 'how long it has been' is not the information that is relevant to a wiki user. What they want to know is how much the game itself has changed since those last edits. A computer algorithm could efficiently check the date of revisions against a table of dates that the game was updated, and supply a field telling you what version was in use when revisions were made. This would be nice in principle since this spares people the effort. The potential downside is that a lot of new wiki content might be driven by people running the svns in anticipation of a major new release.

Thus a tag is probably the best approach, since it is user-controlled.

[Castler]

Doing this for classes, races, and class guides would be pretty easy. Just add a "Needs Update" category to each one that's affected - it's not a large list for each release, so it could be done manually - and then wiki contributors have a single place to see what needs updating.

Of course, this assumes we have a group of regular wiki contributors. I'm not sure if we do right now; the last effort seems to have petered out.

Manually marking out-of-date talents would be a lot harder, but I'm not convinced that the wiki is the best place to list talent info. Auto-generated spoilers can be automatically updated, can present more information, and can do so in a bit nicer format than a (stock / generic) MediaWiki setup can. I realize I'm biased here, since I made some auto-generated spoilers, but there are just so many talents, and ToME changes so often (and all of that is awesome), that it's hard to keep them manually updated in the wiki.

[Zireael]

Those auto-generated spoilers are great!

[chronomancer]

Those auto-generated spoilers are great!

Ditto! Is there a link to them somewhere in the Wiki or main TOME page? This is the first time I've seen them, but I think they're awesome. (For bonus convenience, could we link to them with each patch along with the patch notes?)

Stamping wiki entries with a version number seems like a good idea. It could be tricky on large entries however, if someone were to update just part of the page. We could optionally date stamp each page (in a visible location) with a "last revised" date? Or a combination; version numbers are more useful, where practical, such as on talent entries.