Player.Face "ID"[, "gender"]

[Matt]

[EDIT: Instead of 3 properties, an additional optional variable was suggested so you'd have something like
Player.Face "STF"
Player.Face "SFF",female
Player.Face "SMF",male
Player.Face "S3F",nonbinary
etc.
which makes a lot more sense on multiple levels, though the core of my suggestion in my post below should still apply, mutatis mutandis.]


I'm going to start a new thread on this and delete my response to that 5-year-old thread as it was asking for/assuming some rather different things and also contained some remarks that could be read as transphobic.

Since SBARINFO can no longer be used to determine a mugshot, can we get a feature so that gender can be handled for mugshots in a simple, non-skin-requiring, non-playerclass-reduplicating way in a similar manner to player sounds in SNDINFO?

The way I imagine it to work, you'd have 3 actor properties:

Player.Face (as current)
Player.FaceMale
Player.FaceFemale

implemented as follows:

• If only .Face is defined, then that's used no matter the player's gender selection.*
• If .FaceMale is defined along with at least one other, .FaceMale will be used only if the gender is male. Same goes for .FaceFemale, mutatis mutandis.
• If only .FaceMale is defined and nothing else, no mugshot will appear unless the gender is male.*
• If both .FaceMale and .FaceFemale are defined but not .Face, no mugshot is shown if the gender is other/cyborg/nonbinary/etc. (hereinafter "nonbinary").
• *Possible alternative: If only one of the properties is defined, then that face is used for everything.

Thoughts?

[TheMightyHeracross]

I'd go for the alternative. Seems weird to have no status bar face just because you're female or a "cyborg." Better to have a default.

[Abba Zabba]

Same as what Heracross said. Also, thread in question?

[FDARI]

Or have 3 actor properties:
Face.Male
Face.Female
Face.Neutral (not sure this is the right word to use)

And have "Face" as a shorthand for assigning a value to all unspecified face properties. Same amount of data, more flexibility, and the option of not having a default face. If you do want a default face, use "Face". No reason to force that. If you do use "Face.Male" or any other specific face property, it makes little sense to assume that you want it to serve as a default face.

[Edward-san]

What would it happen to 'Face.Female' and 'Face.Neutral' if I just assign 'Face.Male'? What would they be defaulted to?

[Gez]

Well, I imagine it'd go this way in order of priority, stopping at the first found:

Player.Face<ProperGender>
Player.Face
Player.Face<AnyGenderAtAll (Male, Female, Neutral)>
Vanilla DoomGuy mug
Black Square of Emptiness


Player.Face cannot be removed for backward compatibility reasons.

[Matt]

Assuming the gender will only have 3 options in the foreseeable future, all you really need is

1. The default that will appear in the absence of any marked option
2. The first marked option
3. The second marked option

If we were just building on Doom without thinking about it, 1. would be male, 2. would be female, 3. would be nonbinary.

My suggestion on the top of this thread would have 1. nonbinary, 2. male, 3. female

so there's no real need for a Player.FaceNonbinary, just Player.Face.
(EDIT: And to be absolutely clear on this, my desire is not erasure of nonbinary identity but in fact to elevate that identity to the position of the unmarked, privileged norm.)

For the rest, I think the way Gez has it works the best, though I'd rather see nothing at all (no rendering, =TNT1A0) than an ugly black square!

[NeuralStunner]

Why not expand the current property, instead of adding new ones?

Player.Face "ID"[, "Gender"]

[Matt]

That is a significantly better idea!