Skip to content

fix: restore agility mark of grace looting#501

Merged
chsami merged 2 commits into
developmentfrom
codex/fix-agility-mark-of-grace-looting
Jun 25, 2026
Merged

fix: restore agility mark of grace looting#501
chsami merged 2 commits into
developmentfrom
codex/fix-agility-mark-of-grace-looting

Conversation

@chsami

@chsami chsami commented Jun 25, 2026

Copy link
Copy Markdown
Owner

Summary

  • Query the current tile item cache directly for marks of grace instead of depending on the built-in Agility plugin's static mark list.
  • Pick up the exact reachable mark within the course loot distance using the current tile-item interaction API.
  • Bump MicroAgilityPlugin to 1.2.7.
  • Update QoL smooth camera tracking to use Client#getCameraYawTarget() and bump QoLPlugin to 1.8.14, fixing the CI compile break against Microbot client 2.6.9.

Root Cause

The hub agility script depended on AgilityPlugin.getMarksOfGrace() and then reselected loot by item id through deprecated Rs2GroundItem.loot(id). That path can miss marks when the built-in Agility plugin has not populated its static list, and it can target the wrong item because it re-resolves by id instead of clicking the specific reachable mark.

The PR build also exposed an unrelated existing compatibility break: QoLPlugin still called removed client API Client#getMapAngle(). The plugin already sets yaw through setCameraYawTarget(...), so reading getCameraYawTarget() is the matching current API.

Validation

  • ./gradlew build -PpluginList=MicroAgilityPlugin -PmicrobotClientPath=/home/mimosa/IdeaProjects/microbot/Microbot/runelite-client/build/libs/microbot-2.6.7.jar
  • ./gradlew clean build -PmicrobotClientVersion=2.6.9 (local Gradle still resolved the untracked local 2.6.7 jar via gradle.properties, but full compile/test/build passed)

@chsami chsami merged commit fa24319 into development Jun 25, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants