Skip to content

chore(shortestpath): remove MoA audit temp debug plugin#1752

Closed
runsonmypc wants to merge 2 commits intochsami:developmentfrom
runsonmypc:chore/remove-moa-audit
Closed

chore(shortestpath): remove MoA audit temp debug plugin#1752
runsonmypc wants to merge 2 commits intochsami:developmentfrom
runsonmypc:chore/remove-moa-audit

Conversation

@runsonmypc
Copy link
Copy Markdown
Contributor

Summary

Removes the MoaAuditPlugin and the runMoaAudit() / closeMoaWidgetIfOpen() helpers in Rs2Walker.

These were an offline landing-coord audit tool — the plugin file itself is self-labelled [TEMP] and comments say "Delete when done". They were intended to live on a separate debug branch and never be merged. They slipped into upstream via PR #1750 because the local amend that removed them was never pushed before that PR was merged. Apologies for the noise.

Scope

  • runelite-client/src/main/java/net/runelite/client/plugins/microbot/moaaudit/MoaAuditPlugin.java — deleted
  • Rs2Walker.runMoaAudit() — deleted (~80 lines)
  • Rs2Walker.closeMoaWidgetIfOpen() — deleted

Not in scope

No functional changes to MoA handling. handleSeasonalTransport, lockedMoaRegions, blacklistedMoaDestinations are untouched.

Test plan

  • ./gradlew :client:compileJava — clean build (no refs to the removed symbols).
  • Load plugin list — the "MoA Audit" plugin entry is gone.
  • MoA teleport handling still works for a normal walkTo / nearest bank flow.

MoaAuditPlugin and the runMoaAudit()/closeMoaWidgetIfOpen() helpers in
Rs2Walker were intended as a temporary offline landing-coord audit tool
(self-labelled [TEMP] "Delete when done") and were supposed to be held
on a separate debug branch, not merged. They slipped into upstream with
PR chsami#1750 because the amend that removed them locally was never pushed
before the PR was merged.

Scope: delete-only. No functional changes to MoA handling —
handleSeasonalTransport, lockedMoaRegions, and blacklistedMoaDestinations
are untouched.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Apr 19, 2026

Warning

Rate limit exceeded

@runsonmypc has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 21 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 2 minutes and 21 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: d5eb48a7-fa8c-40f1-8301-76618b478014

📥 Commits

Reviewing files that changed from the base of the PR and between a910d88 and d14db7b.

📒 Files selected for processing (3)
  • runelite-client/src/main/java/net/runelite/client/plugins/microbot/moaaudit/MoaAuditPlugin.java
  • runelite-client/src/main/java/net/runelite/client/plugins/microbot/util/walker/Rs2Walker.java
  • runelite-client/src/test/resources/threadsafety/client-thread-guardrail-baseline.txt

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Removing the MoA audit methods shifted lambda indices in Rs2Walker.java,
invalidating exact-index baseline entries like lambda$handleTransports$47.
Regenerate to match current indices.
@runsonmypc
Copy link
Copy Markdown
Contributor Author

Superseded by #1751, which now bundles the audit removal to avoid a baseline-regen conflict if these two PRs merged separately.

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.

1 participant