-
-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sending player model only in modelindex field (stop use userinfo for this) #342
Comments
hmm, i've tried changing the player's modelindex before with AMXModX on AddToFullPack, but i wasn't able to get it working. I got it to change other entities into different models(grenades for example), but i wasn't able to change players into different models. Not sure why, is there something forcing the player models based on the model userinfo? |
@spark512 you need to remove model field from userinfo. |
Just be aware, in HL (and probably some other games), in mp_teamplay 0 mode players are not forced to specific models and can set them to "bla-bla-bla" and "whatever". And in mp_teamplay 1 mode player models are not precached. |
@LevShisterov yep, therefore there will be a cvar for that. |
You can also prevent the use of such software as: ExtraMirror(https://github.com/shelru/ExtraMirror/blob/master/MiniBase/client.cpp#L214), Ct-Shield, Cardinal, who use the форумулы to calculate SteamId players received in svc_extrainfo |
|
Изначально забыл правильно написание formules, пару раз буквы местами перепутал и забил. Написал по 'русски', и даже так перепутал. Хех. |
I have found some cool feature - player model can be send only via modelindex, you can stop use userinfo for this.
What are benefits of this?
models/player/X/X.mdl
, also you can use spritesWhere we can implement this? We can implement this not only in ReHLDS, but in ReGameDLL and AMXModX.
What we need to implement this in ReHLDS? We need 3 things:
model
field in userinfomodel
field from userinfo when transmitting it to clientsmodel
field, userinfo is totally unchanged, because we removing themodel
field)The text was updated successfully, but these errors were encountered: