You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2021. It is now read-only.
I have searched existing issues (https://github.com/topaz-next/topaz/issues) to see if the issue has already been opened, and I have checked the commit log to see if the issue has been resolved since my server was last updated
This issue occurs on release branch. If other branch, please specify:
Additional Information (Steps to reproduce/Expected behavior) :
I noticed that sometimes when you use a ranged WS, you can get weird damage/tp returns, so I did a bit of digging. In weaponskills.lua, the function doRangedWeaponskill calls upon calculateRawWSDmg, which calls upon getMultiAttacks. That last function is always called, and has no check for whether or not it's a ranged weaponskill. This should not be the case; ranged weaponskills should not get any extra hits from those traits.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
release
branch. If other branch, please specify:Additional Information (Steps to reproduce/Expected behavior) :
I noticed that sometimes when you use a ranged WS, you can get weird damage/tp returns, so I did a bit of digging. In weaponskills.lua, the function doRangedWeaponskill calls upon calculateRawWSDmg, which calls upon getMultiAttacks. That last function is always called, and has no check for whether or not it's a ranged weaponskill. This should not be the case; ranged weaponskills should not get any extra hits from those traits.
The text was updated successfully, but these errors were encountered: