Closed kai-li-wop closed 1 year ago
@mgerhardy: There are still issues in UI_PlayerSettings_Update
. The second condition if (s_playersettings.chosenskins[0] < SKINSPERPAGE)
does not seem to work properly. In the current model constellation the code seems to work fine, but if a model with more than 3 skins is added further down the menu, the arrows (skin up/down) are not displayed, but should be. Maybe s_playersettings.chosenskins[0] is not the right condition at this point. Actually, it should check if the number of skins (without color variants) for the selected model is less than or equal to SKINSPERPAGE (=3), then the arrows should be hidden.
The issue is fixed and the enhancement should work like expected. It could cause some issues when custom model skins do not align to the default naming scheme (default, red, blue, _red, _blue) at the end of the file name.
After Testing with the recent Codebase everything seems to work like it should.
What i haven't tried yet is to use custom models or skins.
But what is the Sex Option doing?
I guessed first that it will change the pronouns in the frag messages Like "PadPlayer blew themselves up" for None but nope.
The skin selection option is probably not always working with custom models and will probably be reverted with the introduction of the wide screen menu. There will be more skin Icons shown, so default, red and blues skins can be selected more easy.
The gender selection option is still without influence but in fact the idea is like you assumed. With this option the user should be able to overwrite the gender given by the selected model in future.
The selection of a player model with a corresponding skin requires a lot of clicks and especially with Padman with currently 27 available skins (incl. color variants) it is hard to keep track.
Further thoughts
Current state of implementation: