Clan Spam Filter v1.8 – Fixed an issue with regular drops#11450
Merged
Conversation
Merge with main
We now support PK broadcasts and we can now decide ourselves which collection log to filter out
Merged with RL
Merged with RL
Pulled to latest master branch
Fixed bugs which was coursed by Jagex messing broadcast messages. We now always remove a broadcast if the setting is set to true and we couldn't find the right indexes to search by Also I updated to latest RuneLite version
Updated to master
It is now possible through CSV to select which player names should always be allowed for broadcasts. Also updated to latest version of RL.
The Clan Spam Filter now correctly filters XP drops, level-ups, and combat level-ups. Additionally, combat tasks are now filtered using the Combat Achievement filter options.
Updated my internal collection log dictionary to include newest bosses such as Yama
Updated my internal Collection Log data string (the previous commit had a bug)
1. Cleaned up my code to make it easier to maintain the plugin 2. Added a icon for my plugin 3. Updated names and descriptions of different configuration settings 4. Added new setting "Filter Combat Diary Tasks"
Fixed a bug where we didn't extract the correct total level up
Fixed "Clan Spam Filter" to work with ObjectStack instead of StringStack
1. Fixed a bug where if the player optained a pet and it got into their backpack it wouldn't be filtered by "filterPets()" function 2. Updated the internal collection log map to contain the new bosses
Updated PB broadcast message to match the new jagex text
1. Updated the total level message and default value to match the new total level of 2376 2. Updated the internal collection log data string to contain the new sailing collection logs
Fixed an issue where broadcast messages included image tag prefixes
Fixed an issue where raid drops now include coin value for the item received
Fixed a bug where regular drops (e.g. "Onyx bolts (e) (xxx,xxx coins)") caused the parentheses check to fail
|
Internal use only: Reviewer details Maintainer details |
iProdigy
approved these changes
Apr 10, 2026
Infinitay
pushed a commit
to Infinitay/plugin-hub
that referenced
this pull request
Apr 26, 2026
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
2 participants
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.
Fixed a bug where regular drops (e.g. "Onyx bolts (e) (xxx,xxx coins)") caused the parentheses check to fail