User:Phol ende wodan - Revision history

Phol ende wodan: this is not a preferred place for xnethack bug reports

2022-03-08T01:50:33Z

this is not a preferred place for xnethack bug reports

Phol ende wodan: add nethackscoreboard template

2021-04-10T16:28:10Z

add nethackscoreboard template

Phol ende wodan: /* Projects */ xnethack hasn't been a 3.6.1 variant for a long time

2020-08-24T14:30:00Z

‎Projects: xnethack hasn't been a 3.6.1 variant for a long time

Phol ende wodan: add 'quality over quantity' design principle

2020-04-30T15:46:02Z

add 'quality over quantity' design principle

Phol ende wodan: remove links to wiki YANI Archive, link the one on github instead

2020-04-06T22:18:18Z

remove links to wiki YANI Archive, link the one on github instead

Phol ende wodan: /* Design */ link to etherpads

2020-01-28T02:38:51Z

‎Design: link to etherpads

Phol ende wodan: /* Design */ link to writing system proposal on reddit

2020-01-15T18:08:32Z

‎Design: link to writing system proposal on reddit

Phol ende wodan: clarify the sort of patches I was referring to

2019-02-20T16:20:52Z

clarify the sort of patches I was referring to

Phol ende wodan: link to ward proposal

2019-01-08T17:11:31Z

link to ward proposal

Phol ende wodan: /* Kitchen sinkiness */ This idea's been bouncing around my head for a while, wanted to put it up here

2018-10-18T02:54:11Z

‎Kitchen sinkiness: This idea's been bouncing around my head for a while, wanted to put it up here

← Older revision		Revision as of 01:50, 8 March 2022
Line 4:		Line 4:

	If you want to contact me, messaging me on IRC is a good bet, but you can also <span class=plainlinks>[{{fullurl:{{TALKPAGENAME}}\|action=edit&section=new}} leave a message on my talk page]</span> and I'll probably see it soon after.		If you want to contact me, messaging me on IRC is a good bet, but you can also <span class=plainlinks>[{{fullurl:{{TALKPAGENAME}}\|action=edit&section=new}} leave a message on my talk page]</span> and I'll probably see it soon after.
		+
		+	If you want to submit an xNetHack bug or feature report, Github is preferred; see the [https://github.com/copperwater/xNetHack/blob/master/CONTRIBUTING.md CONTRIBUTING.md file].

	== Design ==		== Design ==

← Older revision		Revision as of 16:28, 10 April 2021
Line 1:		Line 1:
−	Hi there, I'm Phol ende wodan, more commonly known as {{NAOplayer\|aosdict}} (and also on [https://www.hardfought.org/userdata/a/aosdict/ hardfought.org]) and on [[IRC]] as '''aosdict''' or '''aos'''.	+	Hi there, I'm Phol ende wodan, more commonly known as {{NAOplayer\|aosdict}}, {{NethackScoreboard\|aosdict}} (and also on [https://www.hardfought.org/userdata/a/aosdict/ hardfought.org]) and on [[IRC]] as '''aosdict''' or '''aos'''.

	I'm the author of [[xNetHack]] and also maintain the [https://nethack-yanis.github.io YANI Archive].		I'm the author of [[xNetHack]] and also maintain the [https://nethack-yanis.github.io YANI Archive].

@@ Line 36: / Line 36: @@
 == Projects ==
-* A variant of 3.6.1 called [[xNetHack]]. [https://github.com/copperwater/xNetHack GitHub]
+* A variant of 3.7.0-dev called [[xNetHack]]. [https://github.com/copperwater/xNetHack GitHub]
 * Food overhaul proposal intended to address the overabundance of food in NetHack.
 * Even more vague weapons and fighting rebalance proposal, separate from the combat system proposal.

← Older revision		Revision as of 15:46, 30 April 2020
Line 60:		Line 60:

	'''The DevTeam Thinks Of Everything''': Provide non-standard behavior in every conceivable situation where the player might expect non-standard behavior.		'''The DevTeam Thinks Of Everything''': Provide non-standard behavior in every conceivable situation where the player might expect non-standard behavior.
		+
		+	'''Quality Over Quantity''': A few well-thought-out features are better than a lot of poorly-thought-out features.

	'''Fair Deaths Only''': In reasonable circumstances, it should not be possible for the player to be killed with no prior warning and no opportunity to prevent it.		'''Fair Deaths Only''': In reasonable circumstances, it should not be possible for the player to be killed with no prior warning and no opportunity to prevent it.

@@ Line 1: / Line 1: @@
 Hi there, I'm Phol ende wodan, more commonly known as {{NAOplayer|aosdict}} (and also on [https://www.hardfought.org/userdata/a/aosdict/ hardfought.org]) and on [[IRC]] as '''aosdict''' or '''aos'''.
-I'm the author of [[xNetHack]] and also maintain the [[User:Phol ende wodan/YANI/IRC archive|YANI Archive]].
+I'm the author of [[xNetHack]] and also maintain the [https://nethack-yanis.github.io YANI Archive].
 If you want to contact me, messaging me on IRC is a good bet, but you can also <span class=plainlinks>[{{fullurl:{{TALKPAGENAME}}|action=edit&section=new}} leave a message on my talk page]</span> and I'll probably see it soon after.
 == Design ==
-I enjoy discussing NetHack game design, and frequently talk about it in the #hardfought channel on Freenode. My biggest ongoing project is listening to the design discussions that happen on IRC and sifting through them to find new ideas, or [[YANI]]s. I maintain several pages on this wiki cataloguing all the ones I know of:
+I enjoy discussing NetHack game design, and frequently talk about it in the #hardfought channel on Freenode. My biggest ongoing project is listening to the design discussions that happen on IRC and sifting through them to find new ideas, or [[YANI]]s. [https://nethack-yanis.github.io The YANI Archive is the curated collection of these ideas].
 I've also gotten into the habit of writing long-form proposals that focus on overhauling one specific (but usually significant) part of the game.

@@ Line 23: / Line 23: @@
 * [[User:Phol ende wodan/WardProposal|Proposal to replace Elbereth with a dnethack-like-but-simplified ward system (complete)]]
 * [https://old.reddit.com/r/nethack/comments/d8nihe/ Proposal to revamp the chance of writing unknown scrolls/spellbooks, and the effects for failing to write them (complete, on reddit)]
 Over time, I've also written some lists/essays about problems I see in vanilla and how they could be addressed.

@@ Line 99: / Line 99: @@
   ^            ^                                                                     ^               ^                    ^
   Vanilla      Fourk                                                        SpliceHack        SLASH'EM         Some patches
-  NetHack4
+  NetHack4                                                                                             (e.g. add 1 new item)

@@ Line 21: / Line 21: @@
 * [[User:Phol ende wodan/BardScratchpad|Proposal to add the Bard as a distinct and well-balanced role (incomplete)]]
 * [[User:Phol ende wodan/SearchingProposal|Proposal to revise searching mechanics for less tedium (complete)]]
 Over time, I've also written some lists/essays about problems I see in vanilla and how they could be addressed.

← Older revision		Revision as of 02:54, 18 October 2018
Line 78:		Line 78:

	'''Flavoring''': Everything in the game should have a justification for why it belongs in the game.		'''Flavoring''': Everything in the game should have a justification for why it belongs in the game.
		+
		+	== "Kitchen sinkiness": a measure of variants ==
		+	This is a whimsical attempt to try and quantify NetHack variants based on how much of a "kitchen sink variant" they are - a term usually associated with adding lots of new stuff to the game. (Of course, NetHack is already famous among roguelikes as containing everything and the kitchen sink.)
		+
		+	The measure I propose for kitchen sinkiness is the amount of "new stuff" changes a variant makes on top of vanilla divided by the total amount of gameplay changes a variant makes on top of vanilla. A "new stuff" change is loosely defined as an added monster, item, trap, terrain, artifact, special level, role, race, intrinsic, damage type, et cetera - the sort of changes that take advantage of NetHack's existing code systems. Only gameplay changes are considered, and things like UI improvements or internal code changes don't count. All "new stuff" changes are, of course, gameplay changes.
		+
		+	To illustrate a bit, adding a race would be "new stuff"; allowing a role to play as a race it can't in vanilla would not. Adding an artifact would be "new stuff"; adding an applied effect to an artifact that doesn't currently have one would not. Un-deferring a feature or resurrecting a defunct feature would be "new stuff", since the feature is not currently in vanilla. It can get murkier if the variant introduces something, and then starts making more complicated changes on top of it, such as the SLASH'EM techniques system, or the object properties system, where it's hard to tell whether each new technique or property in that system should count as "new stuff".
		+
		+	Vanilla, and any hypothetical variant that makes zero gameplay changes on top of vanilla, are defined as having 0 kitchen sinkiness. A hypothetical variant that adds solely new stuff would have 1 kitchen sinkiness. If there were a variant that removed things from vanilla and didn't add anything else for some reason, then I suppose its kitchen sinkiness would go negative.
		+
		+	Importantly, kitchen sinkiness is '''not''' a measure of game balance, and is ignorant of what the actual changes are and how they interact with the other features of the variant.
		+
		+	Without actually going through variant codebases to puzzle out and quantify their amounts of gameplay changes, here is a rough guess at where they fall on the scale of kitchen-sinkiness:
		+
		+	FIQHack DynaHack
		+	\| xNetHack GruntHack UnNetHack dNetHack SLEX
		+	0 v v v v v v 1
		+	\|=============================\|=============================\|=============================\|=============================\|
		+	^ ^ ^ ^ ^
		+	Vanilla Fourk SpliceHack SLASH'EM Some patches
		+	NetHack4