Slayer Block Lists

A RuneLite plugin that shows your slayer block list for every master in a side panel, not just the one you're standing next to. Blocked creatures, masters and your current task are all buttons that open the right OSRS Wiki page.

This plugin is largely designed for me for a personal project, but I can see this type of tool is likely useful to others as well. If you have any suggestions, please open an issue or PR.

If you enjoy my work, feel free to buy me a coffee:

Every slayer master's block list in one side panel. A current-task card and your points/streak sit up top, then a collapsible card per master; the master who gave your current task is highlighted and opened automatically. Features Per-master block lists - Turael, Mazchna, Vannaka, Chaeldar, Konar, Nieve, Duradel and Krystilia, each with all seven block slots. Wiki links everywhere - every blocked creature, the current task and each master name opens its OSRS Wiki page. Empty & locked slots - unlocked-but-unused slots are shown, and locked ones say what unlocks them (slot N needs N x 50 quest points; the seventh slot needs the Elite Lumbridge & Draynor diary). Both can be hidden in the config. Current task - your active assignment with the remaining count, assigning master, and Konar's required kill location when applicable. Slayer points & task streak at the top. Everything updates live as you play - block a task, skip one, or gain quest points and the panel follows the same tick.

Reads game state only (vars and the game's own data tables).

./gradlew run        # launch a development client with the plugin loaded
./gradlew shadowJar  # build a side-loadable jar

This tool was absolutely built with AI (claude) however I am also a software engineer by day.

• I have tried to guide the AI to produce code that is correct, readable, and maintainable in a way that I /think/ I would have written it myself, but I cannot guarantee that the code is perfect or free of bugs - "works for me".

• If you would like to submit a PR and you use AI, please be transparent about it in your PR description. I will not reject PRs that use AI, but I do want to know about it, as it helps me review the code.
• But please write your own PR or issue descriptions, and do not use AI to write it for you. I want to know your thoughts and reasoning, not an AI's; its too easy to throw up a bunch of waffle with AI.