-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Shot patch #289
New Shot patch #289
Conversation
|
I know, but this information is still not a part of the Shot. It's a parameter of the firearm just like fire rate or max ammo. If plugins want to access the parameters of the Firearm they can do so directly. |
Also i don't think |
CanHurt is useful when you are making a weapon with a custom way of dealing damage and want to cancel the default. It is possible in Hurting, but why not have it here if we can? Also its backward compatibility since this field was there for more than a year. |
@BoltonDev Ready for review |
@BoltonDev Yes, its tested and working correctly |
Description
Describe the changes
Added new Shot patch
What is the current behavior? (You can also link to an open issue here)
Current Shot patch is using Physics.Raycast in its constructor and is missing crucial CanHurt field that is widely used in plugins
What is the new behavior? (if this is a feature change)
Mentioned issues are fixed
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Yes, it removes MaxDistance field from ShotEventArgs. This field is just as relevant as including raycast mask in the event (not at all)
Types of changes
Submission checklist
Patches (if there are any changes related to Harmony patches)
Other