 |
It seems like the darker the lightgem is, the less penalty there is for moving. In practical terms, once the lightgem is fairly dark, moving doesn't do anything. This isn't ideal, because it's in low light that our eyes become most dependent on movement to detect things. However, changing it is a math issue that's beyond me. |
 |
Perhaps "tdm_lg_crouch_modifier" "-2" is too strong. We should consider changing "cv_lg_crouch_modifier" to float instead of integer so fractional values like 1.5 can be applied. Eg: returnValue += cv_lg_crouch_modifier.GetInteger(); change to returnValue += cv_lg_crouch_modifier.GetFloat(); in Player.cpp |
|
|
The Lightgem modifier is clamped to integer via idMath::ClampInt. That means that subtle changes to biasing won't show up easily. More study will be needed into whether making the result for lightgem modifier a float will be a feasible approach. One more idea left... bias the movement var directly rather than invoking the crouch var as it's own stage in the process? |
|
|
The most straightforward solution would be to use integers if the player is moving. +1 if moving <= crouch speed, +2 if <= walk speed and +3 if > walk speed. That way the effect would be most noticeable at low light levels, which is more realistic. I don't know that tinkering with key mechanics is a good idea at this point though. |
|
|
Agreed |
- Anonymous
