Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

some more docs that we could use #199

Open
RojjaCebolla opened this issue Oct 8, 2021 · 7 comments
Open

some more docs that we could use #199

RojjaCebolla opened this issue Oct 8, 2021 · 7 comments
Assignees
Labels
documentation putting info where people can find it good first issue Good for newcomers help wanted Extra attention is needed

Comments

@RojjaCebolla
Copy link
Collaborator

@RojjaCebolla RojjaCebolla added help wanted Extra attention is needed good first issue Good for newcomers documentation putting info where people can find it labels Oct 8, 2021
@RojjaCebolla RojjaCebolla self-assigned this Oct 8, 2021
@RojjaCebolla
Copy link
Collaborator Author

@Neko-chan448 ? you did a lot of experimenting with transmuters in prior games

@mobi-leuser
Copy link

rules for forging, especially what it does for armour (it doesn't seem to provide intrinsics?). Standard recipes.

@mobi-leuser
Copy link

status "afraid" and how to prevent/cure it.

@RojjaCebolla
Copy link
Collaborator Author

rules for forging, especially what it does for armour (it doesn't seem to provide intrinsics?). Standard recipes.

https://nethackwiki.com/wiki/Furnace#Imbuing

@RojjaCebolla
Copy link
Collaborator Author

RojjaCebolla commented Oct 10, 2021

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.

@RojjaCebolla
Copy link
Collaborator Author

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

@copperwater
Copy link
Contributor

My methodology is:

  1. 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.
  2. Whenever updating the wiki, put the most recent commit hash in the edit summary (e.g. "Latest changes: since d729fba")
  3. 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...)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation putting info where people can find it good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants