Lsrcr Forum

Where does the bug appear: server
When did the bug appear: today
Describe the bug: BeatEn didn't lose his HP upon falling from the building while using /swclimb command.
Frequency: (rare/always) rare (haven't tested much)
Severity: (major/minor/blocker) minor
Steps to reproduce: https://youtu.be/ozg_CGXJWQs

this isn't related to swclimb but something else, I told doug too that sometimes we don't take damage when we fall from a good height, this was reported before too and it was told that this isn't server sided but client sided

BeaTen. wrote:

this isn't related to swclimb but something else, I told doug too that sometimes we don't take damage when we fall from a good height, this was reported before too and it was told that this isn't server sided but client sided

It would be best if they manually add a script for this, take old bomb as an example, when you use it you get your health lowered by 30,40. Same should be done to /swclimb i.e when you fail from good height your hp should automatically be reduced by 40 HP, only if it is client sided bug.

ackman wrote:

BeaTen. wrote:

this isn't related to swclimb but something else, I told doug too that sometimes we don't take damage when we fall from a good height, this was reported before too and it was told that this isn't server sided but client sided

It would be best if they manually add a script for this, take old bomb as an example, when you use it you get your health lowered by 30,40. Same should be done to /swclimb i.e when you fail from good height your hp should automatically be reduced by 40 HP, only if it is client sided bug.

This is a client sided bug, and while what you are saying is possible, it would require more timers (we'd need to check if the player actually didn't lose health before inflicting damage), I don't think the load on the server would be good for now.

For now I think we need to look into some of the real bugs, because some of them are pretty hard to reproduce or even fix, which makes them hard to understand. Because of this, refactoring and also optimizing/removing some of the ancient code is probably a good idea, but time consuming. For now I don't think adding more timers and such is a good idea until these issues have been resolved though.