Exposed stamina pot usage and auto run settings inside the main microbot setting menu#1789
Exposed stamina pot usage and auto run settings inside the main microbot setting menu#1789Besevse wants to merge 3 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughThis PR adds a new Movement configuration section to MicrobotConfig with two boolean settings: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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. Comment |
Adds two toggles to the Microbot plugin config panel under a new Movement section:
Why?
To give the user more control over this behaviour without needing to install any additional plugins - the logic for this is inside (https://github.com/chsami/Microbot/blob/main/runelite-client/src/main/java/net/runelite/client/plugins/microbot/Script.java#L96) the client and it automatically triggers and some users may wonder whats causing this despite all plugins being disabled, it also gives user feedback on whether a specific plugin has enabled/disabled it without needing seperate UI for it in the plugin.
How it works
Both settings map to the existing
Microbot.enableAutoRunOnandMicrobot.useStaminaPotsIfNeededstatic fields that plugins in the hub already read/write. The config is kept in sync with the runtime state on every script tick, so if a plugin overrides either value the checkbox in the UI will reflect that automatically.Notes
combat/agility). This PR doesn't change that behaviour — it just makes the current state visible to the user.