-
Notifications
You must be signed in to change notification settings - Fork 12
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
Grenades show wrong killerinfo weapon #596
Comments
having it have the same names as in og nt for detpacks and frags will make porting some plugins easier (ex. killstreak sounds plugin uses them, as well as probably log parsers and neotokyo's hlstats:x) |
you mean plugins can actually read this information in this box? |
Plugins generally listen for the It might be cleaner to implement this event with parity, if not done already, and use a client side listener for it. It would be what plugins like Killer info display use, and is presumably what we'd wanna emulate for the feature. Although I should add, personally I don't like having this killerinfo thing as a built-in feature at all - IMO it should remain a SourceMod plugin. edit: I see you already did a PR. Well, these were just some ramblings, maybe for a future round of refactoring. |
you can kill yourself |
frag grenade: |
Build Info
v8.0-prealpha (b2291c5)
Description
Grenade kills incorrectly display the attack weapon as the weapon currently held by the attacker, not the grenade itself.
To Reproduce
bot_mimic 1; bot_attack 0
bot_mimic 0
, throw away your own grenade somewhere safebot_mimic 1
on againExpected behavior
Killerinfo panel shows the name of the weapon currently held by the bot as the attack weapon, and not the grenade's name.
Actual behavior
Killerinfo panel shows the grenade's name as the attack weapon.
Operating System
Version/Distro
Mint 21.3 Cinnamon
Machine's CPU
No response
Machine's GPU
No response
GPU's driver
No response
Build's compiler
No response
Additional context and Screenshots
killerinfo.webm
The text was updated successfully, but these errors were encountered: