Difference between revisions of "User talk:Edsrzf"
(Created page with "You might be interested in knowing about [http://crawl.akrasiac.org/scoring/players/edsrzf.html this] based on your record keeping.") |
(→no longer obsolete monster files?!: new section) |
||
| Line 1: | Line 1: | ||
You might be interested in knowing about [http://crawl.akrasiac.org/scoring/players/edsrzf.html this] based on your record keeping. | You might be interested in knowing about [http://crawl.akrasiac.org/scoring/players/edsrzf.html this] based on your record keeping. | ||
| + | |||
| + | == no longer obsolete monster files?! == | ||
| + | |||
| + | Hi Edsrzf<br> | ||
| + | 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. -- [[User:Bwijn|Bwijn]] ([[User talk:Bwijn|talk]]) 15:25, 12 December 2015 (CET) | ||
Revision as of 15:25, 12 December 2015
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)
