• You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙‍♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋

  • A TLP without truebox has thawed (Very Vanilla ready)
    Frostreaver
Resource icon

Release Overseer 04/27/2026

No permission to download
OK, so I thought all is dandy, but overseer popped up during combat - and got stuck at

Code:
[Overseer.lua] >>>  Quest Rotation Cycle Available.  Initiating Full Cycle.
[Overseer.lua] >>>  Starting Cycle (01:10:10)
[Overseer.lua] >>>  Not claiming rewards per configuration
[Overseer.lua] >>>  Claiming Completed Missions
[Overseer.lua] >>>  Not claiming rewards per configuration
[Overseer.lua] >>>  Checking all conversion quests
[Overseer.lua] >>>  Not enough duplicate agents for Common Conversion
[Overseer.lua] >>>  Not enough duplicate agents for Uncommon Conversion
[Overseer.lua] >>>  Not enough duplicate agents for Rare Conversion
[Overseer.lua] >>>  Next Quest Completes In 1h:24m:36s
[Overseer.lua] >>>  *** 85 minutes until next overseer check.  (01:10:27)
[Overseer.lua] >>>  Quest Rotation Cycle Available.  Initiating Full Cycle.
[Overseer.lua] >>>  Starting Cycle (01:10:28)
[Overseer.lua] >>>  Not claiming rewards per configuration
[Overseer.lua] >>>  Claiming Completed Missions
[Overseer.lua] >>>  Not claiming rewards per configuration
[Overseer.lua] >>>  Checking all conversion quests
[Overseer.lua] >>>  Not enough duplicate agents for Common Conversion
[Overseer.lua] >>>  Not enough duplicate agents for Uncommon Conversion
[Overseer.lua] >>>  Not enough duplicate agents for Rare Conversion
[Overseer.lua] >>>  Next Quest Completes In 1h:24m:19s
[Overseer.lua] >>>  *** 85 minutes until next overseer check.  (01:10:45)
[Overseer.lua] >>>  Quest Rotation Cycle Available.  Initiating Full Cycle.
[Overseer.lua] >>>  Starting Cycle (01:10:46)
[Overseer.lua] >>>  Not claiming rewards per configuration
[Overseer.lua] >>>  Claiming Completed Missions
[Overseer.lua] >>>  Not claiming rewards per configuration
[Overseer.lua] >>>  Checking all conversion quests

Not sure if it is because of the combat?
this happened to me with auto restart as CBD said AND having a pending non overseer reward (so was freaking out on the claim and looping).
 
Ok, I certainly had less than 10. I will retry today and see if that behavior is reproducible.
Were they Military and Stealth rewards?

What I am seeing is the Next Rotation Time not updating.

Also, The first claim that is not getting claimed is maxed.

I had collection dispenser and experience as my claim rewards. I added mercenary experience and overseer tetradrachm and he did end up claiming on the mercenary experience on thus clearing them from claim window and stopping the loop.
 

Attachments

  • Untitled.jpg
    Untitled.jpg
    54.1 KB · Views: 1
  • Untitled.jpg
    Untitled.jpg
    52.1 KB · Views: 1
Last edited:
this happened to me with auto restart as CBD said AND having a pending non overseer reward (so was freaking out on the claim and looping).
I was experiencing this as well...

Once i un-checked the "Automatically Restart" box, it settled down..

I'm also having intermittent rewards being claimed.. I've got about 15 toons I'm running this on... Various gold/silver/f2p, all have "Claim Rewards" checked, and upon logging in, when I have overseer Lua start, seems only about 2/3 of them claim their rewards.. the remaining it says claiming, but just closes the reward window and continues its cycle and picks up the new quests, then closes overseer window..

In none of these cases are the rewards windows maxed out.. In fact, they are empty in all of them, and only the currently claimed rewards are the active ones.
 
I was experiencing this as well...

Once i un-checked the "Automatically Restart" box, it settled down..

I'm also having intermittent rewards being claimed.. I've got about 15 toons I'm running this on... Various gold/silver/f2p, all have "Claim Rewards" checked, and upon logging in, when I have overseer lua start, seems only about 2/3 of them claim their rewards.. the remaining it says claiming, but just closes the reward window and continues its cycle and picks up the new quests, then closes overseer window..

In none of these cases are the rewards windows maxed out.. In fact, they are empty in all of them, and only the currently claimed rewards are the active ones.
Yah, I don't think the max is relevant to the issue after looking a few other toons. For some reason those were just the ones that wouldn't claim the experience. After adding other choices to the reward window it did claim those rewards, not sure why it skipped the experience reward. I could manually select experience as the reward but it just wouldn't claim the exp reward with the script.
 
Yah, I don't think the max is relevant to the issue after looking a few other toons. For some reason those were just the ones that wouldn't claim the experience. After adding other choices to the reward window it did claim those rewards, not sure why it skipped the experience reward. I could manually select experience as the reward but it just wouldn't claim the exp reward with the script.

I didnt notice any correlation to the type of quest that generated that reward.. I'm just doing character experience for all of them anyway, so that is the first choice of almost every reward type (except recruit ones I believe)...

I'm running same Lua's , plugins, etc on all the toons too, so its not like one has something conflicting vs another..

I have the /Lua run overseer as one of the lines in my ingame.cfg file.. I wonder if its possible its trying to start its script of "things to do" too soon ? Ie some client-server lag thats disrupting that?

Just to throw a spanner in the works.... Doing the same thing on the same toons on the test server runs and claims rewards with no problems.. And i have everything set the same as my live version...
 
My guess is the loop is occurring here.
Code:
::retryOptionClaim::
                option.Select()

                logger.log2('Claiming ' .. option.Text() .. ' (' .. rewardItem.Text() .. ')')
                mq.delay(1000)

                --- TEMP logic to detect not-select option
                if (option.Selected() == false) then
                    logger.log2('Option selection issue.  Attempting again.')
                    mq.TLO.Rewards.Reward(rewardIndex).Option(rewardOptionName).Select();
                    goto retryOptionClaim
                else
                    -- Verify the selected option is the one we want
                    if (option.Text() ~= rewardOptionName) then
                        logger.log2('Incorrect option selected (' .. option.Text() .. ').  Skipping.')
                        goto nextreward
                    end
                end
 
so for some reason, in line 14-15, its not detecting the valid reward option as per the character's ini and reward choices, its just jumping past that, but its doing the full overseer cycle, claiming, and then running quests, even though its a quick cycle as all 5 have been selected previously...

is there a way to run this through a watcher or anything? I know this is only a Lua run within the game, but any way to do similar to how you could step by step it in an external compiler?
 
so for some reason, in line 14-15, its not detecting the valid reward option as per the character's ini and reward choices, its just jumping past that, but its doing the full overseer cycle, claiming, and then running quests, even though its a quick cycle as all 5 have been selected previously...

is there a way to run this through a watcher or anything? I know this is only a lua run within the game, but any way to do similar to how you could step by step it in an external compiler?
Not sure, but for now to test it out, I just changed the code to claim the reward (which is usually experience at the top left or empty and claims overseer agents) instead of skipping to nextreward.

Now I have to wait for the next rotation. haha

goto nextreward
to
rewardItem.Claim()
 
Yah, so the one that didn't have a matching rewardOptionName selected claimed the reward by default and it moved on. Probably not the right fix, but this does seem to be the area that was going in to a loop.
 
Good grief, get a good night's sleep and miss the mess.

Question @LorDeth & @amosssnake - if you stop and restart the misbehaving script, does it still do the looping?

Someone mentioned the looping yesterday and I hadn't been able to reproduce. I can add some additional logging in key areas to see whats going on.
 
Good grief, get a good night's sleep and miss the mess.

Question @LorDeth & @amosssnake - if you stop and restart the misbehaving script, does it still do the looping?

Someone mentioned the looping yesterday and I hadn't been able to reproduce. I can add some additional logging in key areas to see whats going on.
haha sorry GF. honestly, mines been working good when i uncheck that automatically restart.. I was always manually claiming my rewards, so wasnt really a big deal to me..

but I'm happy to try stuff to see if it helps isolate, though CBD is probably already closer to nailing it than I am..

any way for me to enable logging via the ini file? I havent been logged in all day now, as i've been busy with RL stuff.. but i dont want to log in yet, otherwise I miss the next cycle, and have to wait till tomorrow.. the only thing i see in the character ini is loglevel=2 ..

I think when i forced it to stop, it auto restarted.. only way i could make it stop was to uncheck the 'auto restart' box THEN click that manual stop button..
 
haha sorry GF. honestly, mines been working good when i uncheck that automatically restart.. I was always manually claiming my rewards, so wasnt really a big deal to me..

but I'm happy to try stuff to see if it helps isolate, though CBD is probably already closer to nailing it than I am..

any way for me to enable logging via the ini file? I havent been logged in all day now, as i've been busy with RL stuff.. but i dont want to log in yet, otherwise I miss the next cycle, and have to wait till tomorrow.. the only thing i see in the character ini is loglevel=2 ..

I think when i forced it to stop, it auto restarted.. only way i could make it stop was to uncheck the 'auto restart' box THEN click that manual stop button..
Never a worry here - things ain't workin'. Bug until it's fixed.

The Log Level impacts what goes to the output window as well as the MQ Log file. Next release will have that option in settings as I'm adding more debug output to turn on.

I have fixed a few minor things I'm seeing, not sure it'll address exactly but I appreciate your help (and CBDs, of course) so should get it there soon.
 
Never a worry here - things ain't workin'. Bug until it's fixed.

The Log Level impacts what goes to the output window as well as the MQ Log file. Next release will have that option in settings as I'm adding more debug output to turn on.

I have fixed a few minor things I'm seeing, not sure it'll address exactly but I appreciate your help (and CBDs, of course) so should get it there soon.
ok right on,.. I've got this resource on my watch list so i'll just keep an eye for updates and will try and keep updated accordingly..

does it presently dump anything useful to a log file? or anything I can do that you can use?
 
So just an FYI. If you are running overseer.Lua and happen to run tooncollect.Lua to claim collections. tooncollect unloads mq2rewards and this is what is used to claim your rewards with overseer.Lua

I know the script checks to see if its loaded, i actually made my script load it because I noticed this funny behavior of the script telling me it wasnt loaded. this might call for a load plugin before running the rotation to make sure its loaded.

Code:
if (mq.TLO.Plugin("MQ2Rewards").IsLoaded() == false) then
        logger.log('MQ2Rewards required for collecting rewards. Loading.')
        mq.cmd("/plugin mq2rewards load")
        mq.delay(1000)
        if (mq.TLO.Plugin("MQ2Rewards").IsLoaded() == false) then
            logger.log_error("MQ2Rewards could not be loaded. Rewards will not be collected.")
        end
    end
 
Last edited:
So just an FYI. If you are running overseer.lua and happen to run tooncollect.lua to claim collections. tooncollect unloads mq2rewards and this is what is used to claim your rewards with overseer.lua

ok good to know.. not using that one though.. but I'll also make sure that mq2rewards is loaded on all my chars when they are on..
 
Question - In the past we had to select which quests we wanted to do - Military, Research, Harvesting, etc. Do we not now? Will it automatically select the quest based on the reward priority?
 
I added this to the collectrewards just in case it gets unloaded while its running. other than this issue, i've been running different scenerios on 30 plus toons since yesterday morning and no crashes yet. :) keeping fingers crossed. Hopefully with some of these things GoldenFrog can get some ideas or something useful from it. haha When you have such a complex thing as the overseer with so many variables the script is amazing.

Code:
function CollectAllRewards()
    if (mq.TLO.Plugin("MQ2Rewards").IsLoaded() == false) then
        logger.log('MQ2Rewards required for collecting rewards. Loading.')
        mq.cmd("/plugin mq2rewards load")
        mq.delay(1000)
        if (mq.TLO.Plugin("MQ2Rewards").IsLoaded() == false) then
            logger.log_error("MQ2Rewards could not be loaded. Rewards will not be collected.")
        end
    end
Good call on conflicting unloading of MQ2Rewards. I don't run any such things so haven't seen/considered that. Will add that logic as well.
 
Question - In the past we had to select which quests we wanted to do - Military, Research, Harvesting, etc. Do we not now? Will it automatically select the quest based on the reward priority?
CBD answered but currently there's been no changes to this area. Still requires manually editing the INI file - or leaving it and getting the same behaviour you have previously.
If you had an INI before, it migrates and keeps your configurations.

This is obviously on the list of things to get put into the UI
 
I have always been in the habit of choosing the Mission type I wanted to maximize the reward type I wanted to receive hence why I asked because I still had my .ini set for Military and something else for ornament dispensers. I wanted to have TBL research materials instead, and chose that as priority, but if your missions are set incorrectly, it won't run the tasks that offer those rewards.
 
I'm also getting all kinds of errors which stop Overseer Lua and also on some constantly cycling through checking all the quests, checking conversions, over and over non stop.
 
I'm also getting all kinds of errors which stop Overseer lua and also on some constantly cycling through checking all the quests, checking conversions, over and over non stop.
Known issue. Fix should be incoming soon. Still testing but haven't experienced this two full cycles. (yet) hehe
 
So far this morning, I am not getting the looping, but I'm still getting about 50% success rate for reward claims on my live toons - about 15 in total, 7 are claiming rewards OK and rest are not.. all are running mq2rewards, and in all cases, its character experience I've got set for the top reward..

And on test, im getting 100% success rate for claiming rewards... both live and test versions of the Lua are running up-to-date versions from the launcher..
 
So far this morning, I am not getting the looping, but I'm still getting about 50% success rate for reward claims on my live toons - about 15 in total, 7 are claiming rewards OK and rest are not.. all are running mq2rewards, and in all cases, its character experience I've got set for the top reward..

And on test, im getting 100% success rate for claiming rewards... both live and test versions of the lua are running up-to-date versions from the launcher..
Are the ini settings the same on all of your toons?
 
Not sure if this effects any of the troubleshooting done above, but wanted to share as an FYI... When I login to 1 account, Overseer loads and runs with the first character's ini file. If I camp to character select, and login an alt on the same account, it says Overseer is still running from the previous character, and I assume the same ini. I had to Lua stop, and Lua start again to rerun with the current character's ini.

My use case is to start overseer missions on any char, but want the low level to claim them all for the XP.
 
Not sure if this effects any of the troubleshooting done above, but wanted to share as an FYI... When I login to 1 account, Overseer loads and runs with the first character's ini file. If I camp to character select, and login an alt on the same account, it says Overseer is still running from the previous character, and I assume the same ini. I had to lua stop, and lua start again to rerun with the current character's ini.

My use case is to start overseer missions on any char, but want the low level to claim them all for the XP.
Currently it pauses when switching characters for two main reasons
  1. Made things wonky with the INI and hadn't gotten that sorted out yet
  2. Seemed to have requests for that, "I wanna switch to my alt and back without alt starting Overseer"

For now, the answer would be to restart the script on each character switch. I have two EQ buttons just for this.

But there is a task to add the logic to reload the appropriate characters INI data. It's actually not very far down the priority list.
 
Overseer Lua stopped on 2 of my 6 toons overnight. I don't have any of them claiming the rewards and i have Automatically Restart checked. I will turn logs on so I can catch the spam if any stop and post it.
 
Overseer lua stopped on 2 of my 6 toons overnight. I don't have any of them claiming the rewards and i have Automatically Restart checked. I will turn logs on so I can catch the spam if any stop and post it.
Are your rewards full? If so you can't clear the finished Overseer quests to enable it to start new ones.
 
Overseer lua stopped on 2 of my 6 toons overnight. I don't have any of them claiming the rewards and i have Automatically Restart checked. I will turn logs on so I can catch the spam if any stop and post it.
Does your reward window look like this.

Probably no ideal, but well see.
Code:
::TryAgain::
    local canClaimQuests = mq.TLO.Window('OverseerWnd/OW_OverseerActiveQuestsPage/OW_AQP_CompletedLabel').Text()
    if (string.find(canClaimQuests, "10 / 10")) then
        print('Max Quests Claimed. Need to wait for next Rotation')
        mq.delay('1m')
        goto TryAgain
    end
 

Attachments

  • Untitled (3).jpg
    Untitled (3).jpg
    15.3 KB · Views: 0
Last edited:
Release Overseer

Users who are viewing this thread

Back
Top
Cart