Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
- Minor cleanup of some logging and logic
- Honor Characters Maximum Level
- Track Overseer Achievements
Maximum Level
Enhances option to "Claim Overseer EXP up to a certain level" do be dynamic for level, rather than specified by user.
Benefits:
On next run, if set to 120 previously, will enable "Follow Max Level".
- Follows LS Level Bump to 125
- F2P will cap at 115
- TLP, etc.. will cap at current max level per expansion unlocked
![]()
Else will leave is open to setting custom values. (i.e. "I want to stay at level 90 for now")
![]()
Option can be toggled by the (slightly verbose): runCompletedAchievementQuests
i.e. /bcaa //mqoverseer runCompletedAchievementQuests on
Track Overseer Achievements
This replaces the core concept of "Specific Quests" to run achievement quests when available. Makes things much simpler to track.
NOTE: The TLO Achievement system does not report reliably - so we need to maintain a specific file identifying tasks. Will be maintained until an alternative is figured out.
![]()
By default, maintains existing functionality to run any achievement quests - even if completed.
Unchecking "Run Completed Achievements" will only run the achievement tasks not yet run.
![]()
* Due to not playing nicely with recent changes, temporarily reverted IO improvement
Previously, if the script had to load the MQ2Rewards plugin, the plugin would be unloaded when done.
- Corrected crash when done claiming rewards
That was causing a conflict.
This logic has been removed - so MQ2Rewards will be loaded and left loaded whenever rewards must be claimed
* Change to match latest patch's removal of the Confirmation Dialog prompting when a new quest was run
- Add retry logic to loading global settings.
- Handles situation when too many characters loading at once
- Add option to run recovery quests
- Purpose of this is purely to work the Recovery Quest Experience
![]()
- There is no special logic when to run or not run these. If available, one will be run.
- Quests run in the following priority
- Conversion
- Recovery
- Recruitment
- All Others
- Defaults to 'Ignore'
![]()
Currently I am not aware of a logical set of rules to programmatically determine when running Recovery would be beneficial versus not.
If anyone can outline any such thing, I'd be curious to hear it.
Note: The following features have been in the script for quite some time but apparently broke along at some point
- Script will abort if launched on a character under level 85
![]()
- Automatic running of a full cycle will be paused it:
- Character is switched to an < 85
- e.g. logging to a bazaar mule
![]()
- Character is switched to an 85+ but Settings > General > Pause on Char Change is selected
- e.g. Switch temporarily to a rogue char to make poisons
![]()
![]()
Personally, I use "Pause on Char Change" as I only want things to automate under the character I explicitly launch the script under.
In cases I want a different char at that time, I will explicitly stop and restart the macro.
- Corrected issue where next rotation wouldn't kick off a new cycle.
- A full check will occur on next rotation or next quest completion; whichever is first
- Better handle when all "10/10" available quests have been run for the current cycle
- Properly claim "Scorched Sky" Event recruit rewards
- Added ability to add sets of quests for Events
- Frostfell, Nights of the Dead, Stone Cold Summer, Scorched Sky
To allow characters to properly process a given event, add all quests for that event to the MQ Overseer system
Two mechanisms can be used:
UI
Settings > Specific
New options exist to add or remove all quests for a given Event.
This results in those quests being run after conversion & recruitment but before any others.
![]()
Command Line
Allows bulk addition across one or many characters
- addAllSpecificQuests - add all quests for all events
- removeAllSpecificQuests - remove all quests for all events
- addSpecificQuest [questName] - add all quests for a specific event
- e.g. addSpecificQuest Frostfell
- removeSpecificQuest [questName] - removes all quests for a specific event
- e.g. removeSpecificQuest Frostfell
Note: Terminology use of "Quest" in places should have been "Event" to remove confusion.
This will be corrected in a subsequent release.