Map: Kitsune
Environment: Ubuntu 22.04, CS dedicated server running in Docker
Software: CounterStrikeSharp V50 (Available at: CounterStrikeSharp V50 Release). Note: This issue was also present in earlier versions.
Issue Description: Occasionally, the speed cap in the starting zone, which I believe is set at 400, becomes uncapped. This allows players to exploit this boost to achieve faster times. Since this behavior is unintended, it leads to confusion among players. For competitive integrity, this should be consistent.
Steps to Reproduce: This issue can typically be reproduced on a server using WS Timer + CounterStrikeSharp V50 with an uncapped max speed setting.
Expected Behavior: For fairness and based on the consensus among most surfers, the speed should consistently be capped at 400 within the starting area.
Map: Kitsune Environment: Ubuntu 22.04, CS dedicated server running in Docker Software: CounterStrikeSharp V50 (Available at: CounterStrikeSharp V50 Release). Note: This issue was also present in earlier versions.
Issue Description: Occasionally, the speed cap in the starting zone, which I believe is set at 400, becomes uncapped. This allows players to exploit this boost to achieve faster times. Since this behavior is unintended, it leads to confusion among players. For competitive integrity, this should be consistent.
Steps to Reproduce: This issue can typically be reproduced on a server using WS Timer + CounterStrikeSharp V50 with an uncapped max speed setting.
Expected Behavior: For fairness and based on the consensus among most surfers, the speed should consistently be capped at 400 within the starting area.