Suggestion: allow forcing the same model both in cl_forceenemymodels and cl_forceteammatesmodels

[gundogfan]

When setting the same model (in this case "numodel") to both cl_forceenemymodels and cl_forceteammatesmodels this is printed on console:

"numodel" is excluded from cl_forceenemymodels because it is in cl_forceteammatesmodel.

My friends and I use a model whose colors can be changed through cl_forceenemycolors and cl_forceteammatescolors, so we'd like to simply set the same model to both enemies and teammates and just change their colors. In the client's current state, we have to create 2 folders in Half-Life\valve\models\player named numodel and numodel2 and set them as different models for both commands in order to use it.

[Lazarettoo]

When setting the same model (in this case "numodel") to both cl_forceenemymodels and cl_forceteammatesmodels this is printed on console:

"numodel" is excluded from cl_forceenemymodels because it is in cl_forceteammatesmodel.

My friends and I use a model whose colors can be changed through cl_forceenemycolors and cl_forceteammatescolors, so we'd like to simply set the same model to both enemies and teammates and just change their colors. In the client's current state, we have to create 2 folders in Half-Life\valve\models\player named numodel and numodel2 and set them as different models for both commands in order to use it.

Hi, how i contact to u for error bugfixed mod ?

[tmp64]

This is a very specific use case. I think it should be left as-is and making a copy of the model is an acceptable work-around.