Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Players can fire two kinds of tracers. The first is used to check for a target and e.g. gray out your quivered spell if it has no target. The second is fired by functions like
player_tracer
and warns when there are bad targets (e.g. yourself or an ally). Instead of choosing between these two by setting a combination of flags on a bolt before firing it, choose between them by passing a different tracer class to the bolts fire method.when firing a tracer with the
player_tracer
function don't just warn about one of your allies that would be hit, instead warn about all of them in the same way that melee attacks do (e.g. when using the singing sword). Also, don't spam warnings when firing a starbust that will target you multiple time, instead just say up to how many times the starbust can hit you.Fixes #4151