Daven_26d1 suggested UnAngband docs should be brought back to health (and even offered his help) at
which is great idea, but too great for one-time effort of any single person. Therefore I've opened this thread for collaboration. If you have any question about the game mechanics, ask here and somebody will code-dive and answer. If you have pieces of docs ready, publish here for discussion (and please append your license statement --- GNU GPL + old Angband license, preferably).
AFAIK, but Andrew knows best, there are no secret game notes game notes kept by the maintainer. Everything is either in the in-game notes or in the raw code. Or in the current documentation or comments to the script files, which are both very inaccurate and outdated sources of information.
I think the (already seen) in-game notes should be available from a menu, but they should not supplant a (basic, at least) proper documentation (and/or manual). I wonder, if we should base the documentation on the current files (mostly taken from an ancient V release), current V documentation or something else (e.g. something totally original)? I suppose the current ASCII + menus with links format of documentation is enough?
So, since this is the place for Q&A:
1. what text should be base our efforts on?
2. could we put together a list of all files needed, first, and then work file by file?
3. does it make sense, Andrew?
which is great idea, but too great for one-time effort of any single person. Therefore I've opened this thread for collaboration. If you have any question about the game mechanics, ask here and somebody will code-dive and answer. If you have pieces of docs ready, publish here for discussion (and please append your license statement --- GNU GPL + old Angband license, preferably).
AFAIK, but Andrew knows best, there are no secret game notes game notes kept by the maintainer. Everything is either in the in-game notes or in the raw code. Or in the current documentation or comments to the script files, which are both very inaccurate and outdated sources of information.
I think the (already seen) in-game notes should be available from a menu, but they should not supplant a (basic, at least) proper documentation (and/or manual). I wonder, if we should base the documentation on the current files (mostly taken from an ancient V release), current V documentation or something else (e.g. something totally original)? I suppose the current ASCII + menus with links format of documentation is enough?
So, since this is the place for Q&A:
1. what text should be base our efforts on?
2. could we put together a list of all files needed, first, and then work file by file?
3. does it make sense, Andrew?
Comment