Release Xtreme Tasker v2: UI improvements + bug fixes

[AmTrollin]

# Xtreme Tasker Release Notes

## v2.0 — 06.25.2026

### Sync & Task Completion
- Combined Combat Achievement, Collection Log, and Achievement Diary syncing into a single action
- Syncs now require review before applying task completion changes
- Added **Undo** for the most recently completed current task
- Improved syncing for sequential and repeatable tasks
- Added **Mark Incomplete** (✕) in task descriptions

### UI & Performance
- New horizontal layout with improved space utilization
- Added prerequisite, Collection Log, and Achievement Diary icons
- Improved overall responsiveness and reduced lag

### Tasks
- Added Shellbane Gryphon tasks
- Manual task completion is now limited to task rolls and syncs
- Achievement Diaries now have their own task category
- Moved **Get 1 unique from the Hueycoatl** from **Hard** to **Medium**

### Bug Fixes
- Fixed a potential RuneLite crash when used alongside Collection Log Master
- Fixed syncing and tracking for Tea Flask, Karamja Diary, and Giants' Foundry tasks

[runelite-github-app]

xtreme-tasker: 24387c551e6121d277bc50ee92a3e20ae9aae441..8217e030d870173456a8e5b7eb67ab6be4a37102

[runelite-github-app]

This plugin requires a review from a Plugin Hub maintainer. The reviewer will request any additional changes if needed.

---

Internal use only: Reviewer details Maintainer details

[riktenx]

Your plugin has too much code to be reviewed. We have a maximum of 200k tokens and your plugin has ~260k. Only source code in your main source set is counted and comments are excluded. Unit tests are excluded and any resource files are also excluded.

We do not have the capacity to review a plugin of this size, much less a 20k LoC diff, so if you want to be able to update this plugin you will need to substantially shrink the size of your codebase.

Some things that might help

• checking for unused code
• turning any hardcoded "data" you have in java files into .json resources that you load on startup

I am sure you can ask your LLM to help you reduce the size of your codebase (and point it at this comment) and it will be able to do so without compromising the functionality of your plugin.

[AmTrollin]

Sorry about that, wasn't aware of the limits, thanks for letting me know! Will chunk PRs in even smaller units in the future.

Made following updates:
AmTrollin/xtreme-tasker-osrs#29 (comment)

[AmTrollin]

Sigh, with trying to reduce codebase size, increased LoC. Will re-sumbit smaller chunks.

@riktenx can you please point me to documentation regarding LoC size limits (looks like tests, docs, jsons etc are included in this, despite being omitted for token count), as well as how tokens are calculated? LLM only calculated 207K when you said 260K, so I do not have a way to officially check this on my end. Thanks!

[riktenx]

there is no documentation, i would just write a script or something that creates a copy of your main/ source set that strips all comments and then run that through all of the main ai provider tokenizers. i can tell you it 100% only looks at java files (and ignores comments) in your main source set, i am able to read the code that does it but i cannot share that code

we don't really care about LoC fwiw

[riktenx]

to clarify there is no explicit LoC limit. if your code can be bot-reviewed we basically don't care how much actual LoC you have, because the bot operates on LLM tokens.

if your code cannot be bot reviewed then a reviewer's (all of whom are volunteers, and few of which are active at any given time) capability / desire to look at your code is inversely proportional to how big it is, at twenty thousand lines of code that is naturally nonexistent. in the era of generative ai tools we basically don't have the capacity to hand-review code at the scale at which it is being submitted anymore

for all intents and purposes if you want to be updating your plugin you should keep it well under that 200k token limit so the bot can approve it

[AmTrollin]

@riktenx Awesome, I appreciate the insight! Working on getting my codebase below 200K tokens. Reopening PR and will push in update to reduce ASAP!

Thanks again!

[riktenx]

repo size appears to be good now.

all of your file i/o needs to be within a plugin-specific subdir in .runelite, right now you're doing a file walk directly in .runelite which is not allowed

[AmTrollin]

@riktenx awesome, thanks again for guidance on getting codebase to a decent size!

And scan has been removed, I'm only looking through .runelite/xtreme-tasker-states now.