#CPS/Combo
1 messages · Page 1 of 1 (latest)
@rain granite
@rain granite just use my script
Here's the script for CPS / reach/combo counter
Yes, reach will be difficult since it's an after-event. This means that the location of the players during the attack and their location afterward can completely alter the reach distance, leading to potentially inaccurate values. As a result, calculating it isn't straightforward in this instance.
erm no? just because it's an afterEvent doesn't mean the values are gonna be wrong
it'll give you the right locations
it's just the calculation that's hard
Have you done the testing or are you just assuming?
it's obvious
you're not gonna get two different time frame locations
its either:
- location after the hit
- location on the hit
after event just means the evnet is called after it happens
I promise my script will working
Location after the hit.
If player A hits Player B and Player B remains still, the distance between A and B will not be accurate if A is moving during combat. The distance between the two will not properly reflect the true distance at the time of the hit. Instead you will get the distance between the two after the hit. Both are not the same.
To put it more simply, you could assume they are the same, but I assure you that if you used that same logic to prevent hackers from over reaching for what is allowed in a vanilla setting, you would have numerous false flags as a result of it.
You can use this script to monitor the behavior.
Written on Mobile but should work out of the box 🤪
@rain granite try to use my script
It should be work
Your code should be fine. The reach will have inconsistency from non stationary players though. Since the value is purely for display only it's a matter of whether or not that's a concern. If it's being used for Moderation then it will lead to problems. Vyse will need to make that determination.