Utility Overseer 03/29/2026

• Revert logic to create directory only on-demand

Testing worked for me locally, so obviously I am still misunderstanding something with the package manager and LFS.
Will work better on this.

• 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:

• Follows LS Level Bump to 125
• F2P will cap at 115
• TLP, etc.. will cap at current max level per expansion unlocked

On next run, if set to 120 previously, will enable "Follow Max Level".

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

• Added "Feast Of Giving" To List of Specific Quests
  • First time running will automatically add these to the active list
• Increased retry limit on global configurations
  • Thanks to @Xavierix
• Optimized creating default directory if already exists
  • Thanks to @Kcsdman
• Removed invalid Imgui Flag usage

• Corrected crash when done claiming rewards

Previously, if the script had to load the MQ2Rewards plugin, the plugin would be unloaded when done.
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
    1. Conversion
    2. Recovery
    3. Recruitment
    4. 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