Player.Gender Property for Player Classes

[NeuralStunner]

Simply put, a way to define the default gender for a PlayerPawn class, like how it's done for skins. Deliberately selecting a different skin / gender from the player menu would likely override it (the former assuming the class does not have +NOSKIN set).

A very basic idea, just thought I'd put it out there. Thanks for reading.

[Graf Zahl]

The gender is part of the user configurable player configuration, not the player class. This makes this a 'no'.

[Xim]

Yeah, I'm pretty sure the whole "gender" thing is more aimed at the person playing the game than the character he/she is playing as.

Then again there is the cyborg choice....

[Xaser]

I still wish there were some way of actually using the player's gender selection for something more than a different set of sounds. I agree that it should be a user-selectable option in such a case, though the only current way to even check for the gender is via GetPlayerInfo and ACS. That's not particularly useful for, say, changing a player's sprite/skin or mugshot to something that's more fitting.

Still, I suppose this is hackable on a per-playerclass basis with some use of ACS_ExecuteWithReturn and GetPlayerInfo, though it's far from an ideal solution. And I don't think there's a thing that can be done for the mugshot at all -- I'm wondering if this is worth feature suggesting at least, as it would be as simple as defining an alternate Player.Face type-thing in a custom playerclass.

[NeuralStunner]

I realize gender is not an especially feature-rich property to begin with, and I don't expect it to become so at this point. Sounds and obituary strings are about all it affects as far as I can see, the former being most easily worked around.

I do agree the player should still be allowed to choose whichever they want. I find it strange tough that this is the one return property from GetPlayerInfo, out of them all, that was used in the example. Even then I believe it could be changed easily from the menu and the door tried again, and thus any check at all looks almost pointless. I guess then the closest solution is to avoid such checks, and only use gender neutral messages.

Then there are skins... Skins are not only able to have default genders, but can be be designed for particular classes. The biggest problem I foresee is what happens to sprites outside of the frame range, but that can be worked around if one is careful. If you're going for unique female classes though this is not very workable, as you can't really ensure that the skin will be used.

Thanks for the feedback.

[TheDarkArchon]

I find it strange tough that this is the one return property from GetPlayerInfo,

Hey, there's nothing in ACS that dictates that the fourth wall has to stay intact.