SpliceHack
SpliceHack copied to clipboard
NullCGT
some more docs that we could use
- scrolls of warp foo seem to have been changed to scrolls of change material. this could use a writeup on the nethackwiki, the github wiki, the changelog, anywhere really!
- similarly, object materials are not well-documented. some details can be found in the old changelog. putting good deets anywhere would be groovy.
- could improve this page: https://nethackwiki.com/wiki/Skills_(SpliceHack)
@Neko-chan448 ? you did a lot of experimenting with transmuters in prior games
rules for forging, especially what it does for armour (it doesn't seem to provide intrinsics?). Standard recipes.
rules for forging, especially what it does for armour (it doesn't seem to provide intrinsics?). Standard recipes.
https://nethackwiki.com/wiki/Furnace#Imbuing
status "afraid" and how to prevent/cure it.
added to https://nethackwiki.com/mediawiki/index.php?title=Dragon_(SpliceHack) and it maybe wouldn't hurt to make an article for Afraid, but right now only dragons can inflict that status.
https://github.com/NullCGT/SpliceHack/wiki/All-about-multiclassing this is my best-effort summary of how the system currently works, but it does not include the bugs mentioned in #173
My methodology is:
- Every commit that changes behavior updates the changelog describing how behavior has changed (commit msg is more for describing motivations/reasoning behind change). I specify commits that change behavior because this isn't important for e.g. a segfault fix.
- Whenever updating the wiki, put the most recent commit hash in the edit summary (e.g. "Latest changes: since d729fba")
- When coming back to update wiki again, do a git diff of the changelogs with that hash to get a full summary of changed behavior since last wiki update. Refine into wiki contents.
Hasn't failed me yet (apart from some behavior changes in very early xNetHack that didn't put anything in the changelog and got missed...)
