Utility Overseer 01/27/2026

Note: Existing Overseer Functionality Still Exists

• /lua run overseeer: Run the existing (v. 2.x) Overseer.lua script
• /lua run overseerBeta: Runs the updated (v. 3.0 beta) routine.

Do not run both at the same time, they'll both try to do their thing. Messy.


Changes:

• Added UI which will display first time run
  • /mqoverseer toggles this display
  • /mqoverseer [show/hide] directly controls it
• Configuration files automatically migrated to new format.
  • Formats are almost identical but allow consolidation or obsoleting functionality
  • Overseer.ini -> OverseerLua.ini
  • Overseer_char.ini -> OverseerLua_char.ini
• Consolidated and removed obsolete or macro-specific functionality

Additional Notes:

• Core functionality was unchanged should match previous without issues.
  • Main modifications were around what gets kicked off and when
• UI functionality being expanded to allow greater control of configurations.
• Documentation on the resource will be updated as time permits.

Please comment on any functional or usability issues as this first release gets sorted out.

• Corrected issue where some rewards would be left unclaimed

• Some rewards may not be automatically claimed, if recognized that the wrong one is selected
  • The next script run should pick this up, or reward may be manually claimed

Work to resolve this issue is continuing

• Uses [Auto-Fill] Button for faster quest agent selection
  • This can be overridden with configuration flag:
  • General\useLegacyAgentSelection = 0
• Conversion quests still use previous logic
  
  • This is due to [Auto-Fill] using any agents that exist and has no "Keep 1 or 2 of each" type of logic

• Corrected issue with last update that broke automatic repeating of the cycle

• Corrected legacy code that would cause conflicts if KissAssist was running at the same time

• If character is < 85, skip this cycle or end script if no repeat time configured.

• Appropriate rewards should always be claimed

Some miscommunication with MQ2Rewards occasionally left rewards unclaimed. This should now be resolved.

• Updated SpecificQuest processing to handle missing entry(s)

• Added ability to run a specified list of quests (i.e. Holiday Events)

Adding a section like below will first run any quests in the list, in order, before other general processing.

The following section handles the current Frostfell quests.

To stop, once the event is over for example, remove the section or set index to 0. However there is no real performance hit to leaving it.

INI:

[SpecificQuests]
index=6
1=A True Friend
2=Snug in Their Beds
3=Avarice Never Ends
4=Silent Night
5=A Wonderful Awful Idea
6=Return of the Music