Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Conversation

@greg-kennedy
Copy link
Contributor

This PR adds two bits to monsters that track gender preferences - a 90% chance for "opposite" and a separate 10% for "same" - and these preference bits are checked in could_seduce() during a "seduction attack" against the defender's gender to determine whether the monster will seduce or not.

From the player's perspective, this simply means that 9/10 opposite gender foocubus will make a pass and 1/10 of the same will - same overall odds, just not 10/10 to 0/10.

Gay incubus?
Yes. It makes any foocubus (or nymph) 81% hetero, 9% homo, 9% bi and 1% asexual. Happy Pride!

But I'm not into men?
Grow up.

@copperwater
Copy link
Contributor

The issue I see with this is that a monster's ability to seduce you is determined by the player character's sexuality, not the foocubus's. Currently, in-game, the hero is always heterosexual relative to their current sex, and is therefore vulnerable to seduction from the opposite sex while being immune to the same sex because that's not their orientation. I imagine that the foocubi themselves are always down for seduction and draining, and would gladly seduce a same-sex hero if the hero could ever be homosexual.

Several years ago, I and a few others came up with a solution that I implemented into xNetHack. I believe the impetus was to avoid player discomfort from having seductions that don't match them in real life (or otherwise: let players play as a sexuality that matches their own), and the solution was to make sexuality a setting in the config file.

The broad strokes:

  • There's an "orientation" option that accepts "straight", "gay", "heterosexual", "homosexual", or "bisexual". Configuring any of these in the file sets it for your character when you start a new game. It's not presented as a choice during character creation.
  • Default orientation is heterosexual, not because of heteronormativity but so the game behaves the same to players who never set the option.
  • Sexuality remains relative to the hero's current sex. I.e. a gay male hero who uses an amulet of change will now be seducable by succubi but not incubi.
  • The foocubus summoned from a sink will always be compatible with your orientation (same as before).
  • To compensate for bisexual characters being seducable by all foocubi, they roll twice for the chance of a severe headache.
  • Asexuality doesn't exist mainly for gameplay reasons: it would allow a player who doesn't intend to take advantage of foocubi for levels or other benefits to turn off foocubi as a hazard. (For instance, in tournaments or for speedrunning this would probably be an optimal choice.) There's no change to the 'seduce' sysopt that removes seduction attacks from the install.

The commit, with some more design notes: copperwater/xNetHack@e41489c

@greg-kennedy
Copy link
Contributor Author

greg-kennedy commented Sep 15, 2025

Several years ago, I and a few others came up with a solution that I implemented into xNetHack. I believe the impetus was to avoid player discomfort from having seductions that don't match them in real life (or otherwise: let players play as a sexuality that matches their own), and the solution was to make sexuality a setting in the config file.

I did consider this actually, but decided against it, because the idea of magical demonic seduction seemed (to me) deliberately not respective of the player's wishes - i.e. it's not about what the player wants but what the demon wants :) certainly imagining myself (a straight guy) faced with an ancient male sex demon using magical hypnotism powers in a dungeon, let's be real, I'm not getting out of that with my clothes on if that's his preference.

So what this does is simply makes the demons not 100% heterosexual, as they were before.

But I'm not opposed to the xNethack solution either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Morty Proxy This is a proxified and sanitized view of the page, visit original site.