Skip to content

add damage-history [Updated] #10485

Merged
riktenx merged 6 commits intorunelite:masterfrom
QuestingPet:damage-history
Feb 14, 2026
Merged

add damage-history [Updated] #10485
riktenx merged 6 commits intorunelite:masterfrom
QuestingPet:damage-history

Conversation

@QuestingPet
Copy link
Contributor

[UPDATE] After some discussion on the previous PR, it seems like there were concerns about future abuse of new content being the problem.

the problem is a denylist is difficult if not impossible to moderate and doesn't account for new content. we already have this problem with watchdog where it gets abused within the first 5 seconds of any new content release until the plugin is manually updated to disable it.

To address this I've banned any future NPC from working with this plugin (see commit), until manually updating the plugin pending confirmation of no abuse. This explicitly puts the control of new content working with this plugin back in the hands of the hub maintainers, instead of waiting on the plugin author to update the plugin.

The rest of this description is copied from the previous PR, for context

Previous PR: #10359


New plugin that tracks damage history for yourself and your party members. Also shows the weapon you used, who you hit, and your tick delay from your last hit.

  • Initial plugin release
  • Track damage history for yourself and party members
  • Display damage statistics in dedicated panel
damage-history-panel

@runelite-github-app
Copy link

@runelite-github-app
Copy link

This plugin requires reviews from Plugin Hub reviewers. The reviewer will request any additional changes if needed.


Internal use only: Reviewer details Maintainer details

@riktenx riktenx merged commit d61aa7f into runelite:master Feb 14, 2026
3 checks passed
@QuestingPet
Copy link
Contributor Author

Thank you @riktenx !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments