Monster spoiler page

[takkaria]

Originally Posted by Thraalbee

That is a good thing. I would love if you also added
variant: angband
version: 4.0.5
in the beginning as well

I use regexp so easy to adapt to your changes.
I willl also propose adding my file to json converter to the tools once it is in a decent state

The edit files used to have a version number in them but I removed them. I think they're a bad idea, because it's yet another place to update the version number when a new release happens especially now there's so many edit files.

[kandrc]

Originally Posted by takkaria

The edit files used to have a version number in them but I removed them. I think they're a bad idea, because it's yet another place to update the version number when a new release happens especially now there's so many edit files.

With the makefile + sed (or awk or any number of other tools), this update can be automated. I'd pull the version number from the git metadata and write it into the appropriate files as part of the build process. If you want to avoid shipping git metadata with official releases (sensible enough), then you have a rule to build the release distribution that queries git and does the file update(s) before the code ever goes to the consumers. It may be that git contains some methods to do this automatically when you check out; CVS did, back in the day (or maybe I'm thinking of perforce...?).