User talk:Edsrzf
You might be interested in knowing about this based on your record keeping.
no longer obsolete monster files?!
Hi Edsrzf,
you are very busy in automatizing the monster info files by transforming them into template-driven tables. For the moment this works nicely, giving the most recent parameters by interpreting the newest code. But even if we should praise your diligence there are problems to be considered. Will there be no longer obsolete monster files? How should they be constructed when there is no table body left? The templates will always show only the newest code version. I've encountered the same problem with spell set tables for spell books. It was very tedious to reconstruct the necessary obsolete files (which are necessary to play/understand any of the older versions!!) by searching for the wiki version history. Well, but your change will make even that path impossible: there will be no longer version history data produced once the monster info template is set up working. Please tell me and the others what solution you propose to avoid that. -- Bwijn (talk) 15:25, 12 December 2015 (CET)
- I'll crystalize monsters that were removed in 0.17 when I update their articles, and I'm happy to do the same before I update Module:Table of monsters for 0.18.
- In my opinion the preservation of obsolete information is a bigger problem across all types of pages in the wiki. If you really want to be able to play old versions of the game using the wiki, there needs to be a version of the wiki for every version of the game. There are not only obsolete things to consider, but things that have changed greatly. For example, death cobs in 0.17 are quite different from death cobs in 0.16. (And there are even bigger differences than that between versions.) And why should we only preserve obsolete pages as they most recently existed?
