Repository navigation
fix: sm_banspray crosshair trace and duplicate log line - #73
Merged
Merged
Conversation
Rushaway
force-pushed
the
fix/audit-followup-fixes
branch
from
November 3, 2026 20:26
3c06a04 to
984a1e5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #69.
Stacked on #70, this plugin's translation PR: merge #70 first. GitHub then retargets this PR to
master; refresh it by mergingmaster(overlapping lines: keep this branch's side).Changes
sm_banspraywith no argument now traces the spray under the admin's crosshair, as the code was written to do. The usage text (sm_banspray <target>) is still shown when the command comes from the server console without a target, since the console cannot aim.LogActionin the trace branch, so one line with the hash is logged, as in the target branch.Checks
smtranslatecheck in CI: 0 errors, 0 warnings.