• You've discovered RedGuides 📕 an EverQuest multi-boxing community 🛡️🧙🗡️. We want you to play several EQ characters at once, come join us and say hello! 👋
  • IS THIS SITE UGLY? Change the look. To dismiss this notice, click the X --->
Resource icon

Utility Overseer 09/16/2025

Download now:  Join us with Level 2 access or earn your way in with  RedCents.

〰️Commits​


Added Utils folder.
(9c79d7b) ~Jason Burds
Fix crash in SelectNextDuplicateAgent with nil UI element checks

Added LS to overseer.ui
(09f9b25) ~Jason Burds

〰️Commits​


Fixing Lines 1139 and 1760 with overseer.lua Added checks to make sure the equation had valid numbers.
(6e4e313) ~Jason Burds

〰️Commits​


Testing Sync from Github to RG
(8354be7) ~Jason Burds
- GoldenFrog is gonna take a look at this when he has a chance, in the meantime i've done a couple updates which should help.

Post if you get additional crashes and i'll take a look and make updates for those too
Posted by: Sic
  • Corrected crash when trying to access additional priority groups
Posted by: GoldenFrog
Posted by: GoldenFrog
  • Should catch SelectReward-Option Looping problem and continue gracefully
    • Does not address the cause of the loop, just the looping itself.
    • Any skipped rewards will get picked up in the next cycle
  • Addressed Database Lock issue reported by @dpanaben
Posted by: GoldenFrog
  • Turns off AutoRestart if an invalid UI is detected (missing MaxActiveQuests labels)
    • If RunOnStartup is checked, will still perform one loop, claiming completed missions
    • Thank you @stuff for that catch
NOTE: If using Sparxx UI, get @Psy update to the Overseer Window here:
Posted by: GoldenFrog
  • Added notification if current UI skin (i.e. Sparxx) is missing key UI elements allowing this to run

DETAILS:
Fixing issues one at a time: Sparxx - I can see the problem, but not what's specifically different in the XML.
This isn't the new field on tab 1, but rather something changed on the 3rd tab:

Default UI: View attachment 65619
Sparxx: View attachment 65620

This isn't just visual - there's no data behind it. So my script interprets that as "We're at max".
I'm not going to try to work around this right now - but instead doing the same thing when [AutoFill] was added. New warning message for anyone in this situation.

If anyone feels this is insufficient and needs different handling, let me know.
Posted by: GoldenFrog
Back
Top