Updating Player Mass

#1 The jittering occurs because the client side prediction is getting out of sync with the server. The client is still using the original mass value and so it can't accurately predict where the player is supposed to go.

You need to send the new mass value to the clients via a ::packUpdate somewhere.

#2 I figured that's what it may be.. But how exactly do I do that? I'm not too familiar with that stuff in the engine..

#3 Heres a basic outline of what you need to do:

Add a mass field to the Player class
-Change player.h
-Add entry to Player::InitPersistFields()
-Initialize value from datablock in ::onAdd
Change player physics code so that it uses the player's mass instead of the PlayerData's mass
Add a new bitmask to the Player Class named PhysicsMask (or whatever you want)
Add function Player::SetMass and a connect it to the console with ConsoleMethod()
-In this function, assign the new mass value and do a setMaskBits(PhysicsMask);
Change Player::packUpdate and ::unpackUpdate to transmit the mass value
-Check for the physics mask with something like this if(stream->writeFlag(mask & PhysicsMask))

Tell me which parts you're not clear on and I can give you more detail when i get home this evening.

#4 Hm.. I think i got most of that... I'll try messin around in a bit, see if I understand it as much as I think..

One small question though is on the second step. -Add entry to Player::InitPersistFields() There is no Player::InitPersistFields(), did you mean PlayerData?

Thanks.

#5 Scratch that, you dont need the initpersist entry at all.