Release Overseer 04/27/2026

[morgium]

how would i set this so it claims the character XP, because that has never worked for me.

[Rewards] 1=Overseer Tetradrachm 2=Character Experience 3=Mercenary Experience index=X

for X = 0,1,2,3 it always claimed the tetradrachm
when i changed the order of rewards, so made 1=Character Experience, it also claimed the tetradrachm. no matter what the fucking index was.

 

[Shadow]

You are doing it wrong. Keep the index = number of rewards. Set character exp as 1. Done. Also, you need to change your mission priorities as well to maximize.

 

[Rare Spawn]

There appears to be a bug/crash when "checking all conversion quests". the overseer game window at the time of the script crash is the 'show reward' window for the quest. I suspect this is because I set to select question based on XP , as that is the change I made recently.

questSelectionType=Exp

Where can I find overseer logs to be more helpful?

 

[Rare Spawn]

Love the Lua script, I use overseer more than any other plugin/macro... wanted to share a non-critical bug.

QuestSelectionType=Priority (switched back because of previous post)
repeatTimeMinutes=0

On exit after completion, it throws this error:

 

[Dragonslayer]

Hi Frog. Looks nice and looking forward to using it.

There's an issue with the new INI logic however. Running on a char with no existing INI file results in a crash at line 680. Turns out 'QuestSelectionType' is nil because the default INI settings uses the line

questSelectionType = Priority,

where it should be

questSelectionType = 'Priority',

Minor fix, and ran through to completion after.

I am confused, in my ini its:

questSelectionType = Priority

should that be modified?

 

[vandersl]

I am confused, in my ini its:

questSelectionType = Priority

should that be modified?

No, leave it alone in the INI file. My post was about how the script initializes the value if it is not in the INI file.

 

[Dragonslayer]

ok, ty

 

[Twinkeltoes]

So I'm new to the Lua world. I've started running this a few weeks ago. Loved it. But I noticed some issues lately with it working/not working, started converting too soon etc. I noticed there was an update so I tried reverting my .ini back to my previous .ini that worked. It caused lots of red errors on loading.
So I deleted the .ini and went from scratch. I figured the issues were due to an update that reset a lot of customization settings. So I reset those. Now I have 1 error line when I load up. I tried running tutorial and got the line after the error message.

*Edit* I ran the exact same .ini as below on a different character and he would run then bomb out on agentCountForConversion. I adjusted that to be just agentCountForConversion=7 (instead of 5/7/9, which is a minor inconvience) and that character is working now. I'm not sure how to tell the file that this character has run the tutorial or what ever it is that is blocking the script from running.

*Edit take 2* Fixed the issue. Apparently it didn't want to run overseer @ start up. I would get the need to run tutorial error. So I just ended up having to manually /Lua run overseer to get it to work. Logged came back (after making my personal adjusments to not eat up my agents in conversions and to search for the tradeskill missions) It is working now

*Summary if u run into these issues*
1 agentCountForConversion currently doesn't seem to work for common/uncommon/rare like it used to. need to set 1 number for conversion
If you get a message you need to run tutorial when you've had the Lua set to run at start up. Manually /Lua run overseer for the first time (again) log, make your personalizations.

[Debug]
doNotFindAgents=0
doNotRunQuests=0

[General]
agentCountForConversion=5/7/9
claimRewards=1
countAgentsBetweenCycles=0
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
logLevel=2
maxLevelForClaimingExpReward=120
maxLevelPctForClaimingExpReward=20
minimumQuestExperience=0.0099999999999999
minimumSuccessPercent=0
monitorQuestRotation=0
questSelectionType=Priority
repeatTimeMinutes=-1
version=2

[QuestPriority]
Durations=6h|12h
Levels=5|4|3|2|1
Priorities=Levels|Durations|Rarities|Types
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Research|Harvesting|Crafting

[QuestPriority_Unsubscribed]
Durations=6h|12h
Levels=5|4|3|2|1
Priorities=Levels|Durations|Rarities|Types
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Research|Harvesting|Crafting

[Rewards]
1=Character Experience
2=Claws of Veeshan
3=Collection Item Dispenser
4=Overseer Tetradrachm
5=Mercenary Experience
index=5

 

[morgium]

You are doing it wrong. Keep the index = number of rewards. Set character exp as 1. Done. Also, you need to change your mission priorities as well to maximize.

[General]
useCharacterConfigurations=0
maxLevelForClaimingExpReward=120
maxLevelPctForClaimingExpReward=99.99
minimumQuestExperience=0.0099999999999999
(...)

[Rewards]
1=Character Experience
2=Mercenary Experience
3=Overseer Tetradrachm
index=3

 

[Shadow]

[General]
useCharacterConfigurations=0
maxLevelForClaimingExpReward=120
maxLevelPctForClaimingExpReward=99.99
minimumQuestExperience=0.0099999999999999
(...)

[Rewards]
1=Character Experience
2=Mercenary Experience
3=Overseer Tetradrachm
index=3
View attachment 43641

View attachment 43640

Now show us your QuestPriority section? On further thought, paste the entire .ini

What happens when you use index=0 BEFORE the exp options? Why would index=x be below the options?

 

[Rare Spawn]

[General]
useCharacterConfigurations=0
maxLevelForClaimingExpReward=120
maxLevelPctForClaimingExpReward=99.99
minimumQuestExperience=0.0099999999999999
(...)

[Rewards]
1=Character Experience
2=Mercenary Experience
3=Overseer Tetradrachm
index=3
View attachment 43641

View attachment 43640

I can confirm having this same odd behavior now too. I am still trying to drill down on it, having just a few opportunities to test every 12h or so. I *suspect* it has something to do with the feature that skips XP if you have over a certain level and %.

I also noticed the new default ini puts XP as option 2, and Techno as option 1. It seems suspicious that when I run a character who is max level already, BUT I still want XP for my merc, it is always choosing techno. even if I set the max level for XP to be 121.

 

[morgium]

Now show us your QuestPriority section? On further thought, paste the entire .ini

What happens when you use index=0 BEFORE the exp options? Why would index=x be below the options?

No reason, order doesn't matter. i didnt try index=0, although i see now that i said i did, that was out of habit because array indices usually start at 0 for the first element. my bad.

i looked at the code, when i would set index to 0, rewardOptionCount would be 0.
You can also see why order doesnt matter. This reads the value, no matter where it is.
local rewardOptionCount = settings['Rewards']['index']

Also looking at the code, there is no reference to the Quest Priority section, also thats not the point here.
ill look at the claim logic and try to find out why its doing that for me.

 

[ralen]

Why would index=x be below the options?

This happened to all of my character .ini's in a recent update as well. It also reset all of my selection options and I had to redo them. I'm not sure if the recent patch caused it, but is the Index= required to be before or after the list as of now? Or does it not matter?

 

[Dragonslayer]

@morgium: have the same behavior, no matter what I am trying. Have 2 characters not max level, where I claim manually "Character Experience" as a workaround, b4 I launch overseer.Lua.
@ post 74 Goldenfrog replied: "Sorry for the exp not claiming. Will try to resolve as soon as I can.", so eventually Goldenfrog will havew a look at it and solve it. In my ini index=3 resides above the options. This doesn't matter.
My guess is, ther's just a bug which will get ironed out hopefully with the next version.

 

[Shadow]

This happened to all of my character .ini's in a recent update as well. It also reset all of my selection options and I had to redo them. I'm not sure if the recent patch caused it, but is the Index= required to be before or after the list as of now? Or does it not matter?

Index=x is before in the mac version, so...

 

[Rare Spawn]

No reason, order doesn't matter. i didnt try index=0, although i see now that i said i did, that was out of habit because array indices usually start at 0 for the first element. my bad.

i looked at the code, when i would set index to 0, rewardOptionCount would be 0.
You can also see why order doesnt matter. This reads the value, no matter where it is.
local rewardOptionCount = settings['Rewards']['index']

Also looking at the code, there is no reference to the Quest Priority section, also thats not the point here.
ill look at the claim logic and try to find out why its doing that for me.Claim

Claim logic appears to be starting at the HIGHEST index and working backwards... going to test setting the reward I want as index=3 and the ones I dont want as 2 and 1, and see what happens when these quests finish in a few hours.

 

[morgium]

i

Claim logic appears to be starting at the HIGHEST index and working backwards... going to test setting the reward I want as index=3 and the ones I dont want as 2 and 1, and see what happens when these quests finish in a few hours.

ah no, i thought that too at first, but this is about the Quests themselves!! The options are iterated from 1 to optionCount! dont risk it
so if you have 4 quests done, it starts at quest 4, and then checks the options and so on.

 

[Rare Spawn]

i

ah no, i thought that too at first, but this is about the Quests themselves!! The options are iterated from 1 to optionCount! dont risk it
so if you have 4 quests done, it starts at quest 4, and then checks the options and so on.

Haha too late, I have a bunch more techno than I needed

Check out the function SkipRewardOption, I think the < and > are arse backwards, and one of them needs to be "less or equal to".
Fixing that locally worked, but revealed that the script has more bugs... after making a claim for reward index 1, i this it is still looping through the additional options, as it keeps telling me how many total Techno I own, despite the EQ log showing my XP gains.

 

[Rare Spawn]

Let me start by saying I use this addon THE MOST, and this was a huge part of what brought me to MQ2. Thank you for all the time and effort you put into this macro, its clearly a labor of love, and I am thankful to @GoldenFrog for every bit of it. I'm not a coder, and I couldn't make something like this. I can't state that part enough. So I am hoping my contribution below is helpful, not misperceived as criticism or nit picking. After all, QA work is ideal for guys that can't code, so here I go.

ignoreRecruitmentQuests=1 Does not appear to work, it still ran recruit missions.

Current version was also picking recovery missions. Maybe type=any means literally any? Especially when I was prioritizing 6h.

Getting an occasional, but not easily repeatable crash on claiming conversion quests. Maybe a delay issue?

questSelectionType=Exp had some crash issues scanning through all the quests. I love the concept, does this take into consideration that 3x 6H quests is more XP than 1x 24H quest of the same level/rarity? OR will it just go for the biggest XP quests which will typically be the 24h ones?

Claiming EXP rewards is broken because the skipRewardOption function has the greater/less than backwards. Here is a temp hot fix for that

[CODE lang="Lua" title="function SkipRewardOption"]function SkipRewardOption(rewardOptionName)
if (rewardOptionName ~= "Character Experience") then return false end

local maxLevel = settings['General']['maxLevelForClaimingExpReward']
local maxPct = settings['General']['maxLevelPctForClaimingExpReward']
if (maxLevel == nil) then return false end
if (maxPct == nil) then maxPct = 95 end


if (maxLevel < mq.TLO.Me.Level()) then return true end
if (maxLevel > mq.TLO.Me.Level()) then return false end

if (maxPct < mq.TLO.Me.PctExp()) then return true end
return false
end
[/CODE]

The exit() on line 103 (and possibly 96 too) cause Lua errors to spew when the script ends. Here is what I did to fix that.

[CODE lang="Lua" title="function Main (edited)" highlight="81, 54, 47"]function Main ()
Initialize()
LoadMq2Rewards()

local countdownDelayMinutes = 60
local minutesToWait
local repeatTimeMinutes = settings['General']['repeatTimeMinutes']

if (DebugNoRunQuestMode == true) then
Log ('DEBUG: Not Actually Running Quests due to Debug|doNotRunQuests configuration flag')
end

if (Param0 ~= nil) then
Parameterized(Param0)
return
end

::cycleLoop::
-- Reset any variables we're keying off of
TooManyPendingRewards = false
AvailableQuestListLoaded = false
ActiveQuestListDirty = true

Log2 ('Starting Cycle '..os.date('(%H:%M:%S)', os.time()))

OpenOverseerWindow()
ValidateTutorialStatus()
CollectAllRewards()
ClaimCompletedMissions()
CollectAllRewards()
RunConversions()
RunRecruitQuests()
RunGeneralQuests()
DetermineNextQuestTimes()
DetermineNextRunTime()
CloseOverseerWindow()

if (MinutesUntilNextQuest == 0) then
-- TEMP: 'Til tracking down when this happens. Possibly when quest completes during run?
-- Check that we actually do NOT have pending quests.
if (mq.TLO.Window(ActiveQuestList).Children()) then
LogError ('Out of sync: No next quest minutes but pending quests exist. Checking cycle again.')
goto cycleLoop
end

Log ('No pending quests.')
goto exit
else
Log ('Next Quest Completes In :'..NextQuestCompletion)
end

if (repeatTimeMinutes == 0) then
Log ('Ending Macro.')
goto exit
end

if (repeatTimeMinutes > 0) then
local MinutesUntilNextQuest = repeatTimeMinutes
end

if (settings['General']['countAgentsBetweenCycles'] == true) then
OutputAgentCounts()
end

::countdownLoop::
if (MinutesUntilNextQuest <= 0) then
goto cycleLoop
end

Log ('*** '..MinutesUntilNextQuest..' minutes until next overseer check. '..os.date('(%H:%M:%S)', os.time()))
if (MinutesUntilNextQuest > countdownDelayMinutes) then
MinutesUntilNextQuest = MinutesUntilNextQuest - countdownDelayMinutes
minutesToWait = countdownDelayMinutes
else
minutesToWait = MinutesUntilNextQuest
MinutesUntilNextQuest = 0
end

mq.delay(minutesToWait.."m")
goto countdownLoop
::exit::
end[/CODE]

Again, thank you for the great script. It gets much mileage at my house, so much that it had some issues, I started googling Lua code samples until I could patch my local copy. Sorry to be a pain in the butt, but I hope it helps!

 

[Dragonslayer]

@Rare Spawn : your inversion of > and < in function SkipRewardOption solved the "Character Experience" problem for me. Niced finding.

 

[GoldenFrog]

Thank you, RareSpawn and everyone. Critical feedback is the reason things like this get completed and updated. Never worry about that.

;tldr For your issues/questions, looks like these are all issues with the Lua port. Nice catches and fixes; you're good to change careers to development.

• ignoreRecruitmentQuests - corrected
  • Issue impacted ignoreConversionQuests and a couple others.
• Backwards <> - corrected (and very disconcerting and slightly embarassing).
• exit() - corrected. Those 2 were missed and still in the original Macro format

Additional details:
I admit that I "questSelectionType=Exp" hasn't gotten very much attention since "Priority" was added in. I would recommend changing to that. It gives you much more control, if desired, over what quests are run, and which rewards are selected.
Also, it only picked the quest with the single highest reported exp. So no, 3x6h wouldn't be used instead. That was planned but never happened due to "Priority" allowing you to specify things like "Only run 6h Trade Level 5 rare only", or whatever options give the highest exp at that time.

questSelectionType=Priority

[QuestPriority]
Durations=6h|12h|24h
Levels=5|4|3|2|1
Priorities=Levels|Durations|Rarities|Types
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Any

 

[GoldenFrog]

So I'm new to the lua world. I've started running this a few weeks ago. Loved it. But I noticed some issues lately with it working/not working, started converting too soon etc. I noticed there was an update so I tried reverting my .ini back to my previous .ini that worked. It caused lots of red errors on loading.
So I deleted the .ini and went from scratch. I figured the issues were due to an update that reset a lot of customization settings. So I reset those. Now I have 1 error line when I load up. I tried running tutorial and got the line after the error message.

*Edit* I ran the exact same .ini as below on a different character and he would run then bomb out on agentCountForConversion. I adjusted that to be just agentCountForConversion=7 (instead of 5/7/9, which is a minor inconvience) and that character is working now. I'm not sure how to tell the file that this character has run the tutorial or what ever it is that is blocking the script from running.

The INI-From-Scratch got some attention last week but apparently still issues. I will try to dig in more today.


agentCountForConversion requires a pipe between numbers, not a slash. I checked the original macro and it was a pipe also.
agentCountForConversion=4|5|6

I will do more testing of this feature though - as I rarely use it myself. I thought globally keeping 4 of each was a lot. 5, 7, 9 is a ton. I love it.

 

[GoldenFrog]

GoldenFrog updated Overseer with a new update entry:

2.6: Corrected issues with LUA Port

• Issue with ignoreRecruitmentQuests, ignoreConversionQuests and a few others
  • Problem was in logic maintaining compatibility of INI for both LUA and Macro
• Updated two locations where script ending (exit) was wrong
• Corrected logic boo-boo in "Choose Exp When Below Certain Level/Percent"

Read the rest of this update entry...

 

[GoldenFrog]

GoldenFrog updated Overseer with a new update entry:

2.7: Removed obsolete test code

* Removed obsolete test code

Read the rest of this update entry...

 

[Twinkeltoes]

I've still been getting some Lua errors causing it to crash, not sure why it happens on some toons and not the others as I have my .ini copy/paste to all of them. After it crashed on character load, I manually /Lua run overseer and it seems to work. I also had it claiming the wrong reward for some reason. I have first check be Claws of Veeshan tradeskills, 2nd is overseer tetradrachm. It says claiming CoV stuff, but doesn't then goes to Tetradrachm and claims that.

[Debug]
doNotFindAgents=0
doNotRunQuests=0

[General]
agentCountForConversion=7
claimRewards=1
countAgentsBetweenCycles=0
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
logLevel=2
maxLevelForClaimingExpReward=120
maxLevelPctForClaimingExpReward=95
minimumQuestExperience=0.0099999999999999
minimumSuccessPercent=0
monitorQuestRotation=0
questSelectionType=Priority
repeatTimeMinutes=-1
version=2

[QuestPriority]
Durations=6h|12h
Levels=5|4|3|2|1
Priorities=Levels|Durations|Rarities|Types
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Types=Research|Harvesting|Crafting

[QuestPriority_Unsubscribed]
Durations=6h|12h
Levels=5|4|3|2|1
Priorities=Levels|Durations|Rarities|Types
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Any

[Rewards]
index=4
1=Claws of Veeshan
2=Collection Item Dispenser
3=Overseer Tetradrachm
4=Mercenary Experience

 

[GoldenFrog]

I've still been getting some lua errors causing it to crash, not sure why it happens on some toons and not the others as I have my .ini copy/paste to all of them. After it crashed on character load, I manually /lua run overseer and it seems to work. I also had it claiming the wrong reward for some reason. I have first check be Claws of Veeshan tradeskills, 2nd is overseer tetradrachm. It says claiming CoV stuff, but doesn't then goes to Tetradrachm and claims that.

Thank you, Twinkeltoes.

I have a few tradeskill rewards pending completion in a couple hours. I'll check your exact INI then. I did verify that Tetradrachms, Collection, and Ornamentation Dispensers are working for me.

How are you configured to run the Lua at startup? Want to make sure I duplicate your configuration.

 

[B_I_G__D_A_D_D_Y]

Thank you, Twinkeltoes.

I have a few tradeskill rewards pending completion in a couple hours. I'll check your exact INI then. I did verify that Tetradrachms, Collection, and Ornamentation Dispensers are working for me.

How are you configured to run the lua at startup? Want to make sure I duplicate your configuration.

I've went back to using the macro version as it's more reliable than the Lua. I think the reliability has to do with lag. No matter which automation I use there are frequent errors. The macro version seems more capable of recovering from the problems and then continuing on.

I'll give you one example of what I mean by lag. If there are enough agents to run a Common Conversion then it will run the first time without issue. When the automation clicks the Success button the Overseer UI should switch back to the Available Mission view and the Common Conversion mission should now appear at the top of the list and the automation should immediately check if there are enough duplicate agents to run the Common Conversion again. What happens to me is the Overseer UI will NOT display the Common Conversion mission again for 2 or 3 seconds, during which the automation moves on and looks for the Uncommon Conversion mission. These multi-second delays in various UI components are what I mean by Lag and why the automation runs into problems because things don't happen like when Overseer was much more instantaneous.

I'm not complaining or blaming the macro or the Lua. It's hard to code for things that you can't duplicate in your testing. I'm running about 700 agents usually. I keep 4 Commons, 2 Uncommons, and 1 Rare and 1 Elite.

 

[Twinkeltoes]

Thank you, Twinkeltoes.

I have a few tradeskill rewards pending completion in a couple hours. I'll check your exact INI then. I did verify that Tetradrachms, Collection, and Ornamentation Dispensers are working for me.

How are you configured to run the lua at startup? Want to make sure I duplicate your configuration.

1) for some reason that screenshot I shared only shared the start up error, not the reward claiming issues that I had in the same shot. I'll attach another one to this post.
2) My start up is ran from an ingame.cfg file that currently has:
/Lua run lootly
/Lua run overseer

here is the reward claim screenshot

 

[Twinkeltoes]

Another issue I "MIGHT" be having, I need to pay attention more. Is that the reason I'm running the Lua version is so I can keep my KA going while running overseer. On at least one of my toons it SEEMS to be shutting the macro off. I.E. I have a bard assisting my MT np, and it seems after the Lua runs my bard stops assisting. I'm basically restarting my KA on my bard, druid, wiz. It's not horrible as with macro version I just forget to run overseer as I play. This way I can see my toons aren't running and get it going. It's just not working as I intend it. But of course like many other things I do, I probably have some setting wrong.

 

[Rare Spawn]

Another issue I "MIGHT" be having, I need to pay attention more. Is that the reason I'm running the lua version is so I can keep my KA going while running overseer. On at least one of my toons it SEEMS to be shutting the macro off. I.E. I have a bard assisting my MT np, and it seems after the lua runs my bard stops assisting. I'm basically restarting my KA on my bard, druid, wiz. It's not horrible as with macro version I just forget to run overseer as I play. This way I can see my toons aren't running and get it going. It's just not working as I intend it. But of course like many other things I do, I probably have some setting wrong.

I have issues too when Overseer kicks off when CWTN or KA are busy (fighting). Its for this reason I have overseer set to run once and end, and have it run when I login, and can run it when I am idle/medding ad-hoc.

 

[Twinkeltoes]

I have issues too when Overseer kicks off when CWTN or KA are busy (fighting). Its for this reason I have overseer set to run once and end, and have it run when I login, and can run it when I am idle/medding ad-hoc.

I haven't noticed issues with CWTN plug ins, but ya when the Lua kicks in it has been shutting my KA off for sure. I tested it all night last night. I might have a config setting wrong though. You may be correct that it wont do it while idle/medding. I honestly wasn't checking for that which would be interesting that there's some kind of conflict with an active macro/plug in and an active Lua vs a resting macro/plugin and an active Lua. In theory they should be diffferent files and not conflict. But something is happening.
If I'm going to only run it on start up and logging then this would be no different than the macro version for my intentions.

 

[GoldenFrog]

I have the same issues with KissAssist - but not CWTN macros. Not sure there is anything that can be done about that, but will look into it today and see.
On my CWTN toons, I let it run freely.
On the KA, like RareSpawn said, I only do once/end.

 

[GoldenFrog]

If I'm going to only run it on start up and logging then this would be no different than the macro version for my intentions.

I agree here. The key for me is maintenance and running the same thing for everyone.

First: /bcaa //Lua run overseer -- kicks things off for everyone instead of a Lua-for-some, macro-for-others
The other is it'd be nice to fix any issues with Lua and deprecate the macro so there's only one to maintain. That gets icky-blechy-yucky over time.

 

[Ladon]

The latest version crashes when attempting to write the character INI after setting

[General]
useCharacterConfigurations=0

Copying over the INI from an individual character's INI gets to running all subsequent processes.
A few things that I've noticed with the Lua version:
1) There's an EQ bug with Conversions counting towards the maximum completed quests for the day. Overseer doesn't seem to take that metric into account and spam attempts to start a quest when a character is capped out for the day.
2) Rewards claiming (as discussed above) is a little inconsistent. I'm running two exact 85 heroics for testing on the same INI and one will claim XP rewards while the other will not.
3) As mentioned above, CWTN and zoning impact performance of the script. The tab may change unexpectedly and the script will get stuck waiting for a quest to complete. Add a section for unexpected handling that verifies the current activity is on the right tab!

I Luave Overseer. Thank you.

 

[Berkz]

I started getting this error in my SK when I run Overseer. It gets to Common Conversion and stops. For some reason it only happens on my SK

 

[GoldenFrog]

The latest version crashes when attempting to write the character INI after setting

[General]
useCharacterConfigurations=0

Copying over the INI from an individual character's INI gets to running all subsequent processes.
A few things that I've noticed with the LUA version:
1) There's an EQ bug with Conversions counting towards the maximum completed quests for the day. Overseer doesn't seem to take that metric into account and spam attempts to start a quest when a character is capped out for the day.
2) Rewards claiming (as discussed above) is a little inconsistent. I'm running two exact 85 heroics for testing on the same INI and one will claim XP rewards while the other will not.
3) As mentioned above, CWTN and zoning impact performance of the script. The tab may change unexpectedly and the script will get stuck waiting for a quest to complete. Add a section for unexpected handling that verifies the current activity is on the right tab!

First apology - life has hit me again this past few months so time was limited. Things are freeing up again and I'll give this some efforts.

The "useGlobalConfigurations" just missed this in the conversion to Lua. Working on that right now.

#1 - I thought they changed things about a year ago to let Conversions be the exception to the "5 at a time" and "10 per day" limits. There's explicit code to allow Conversions in both of these cases. I apparently haven't hit that limit recently. Can remove that code if this is the case.
-- If at 10/10, only claim Conversions...

#2 - I have seen this. It sometimes leaves one behind. Lua version uses a different reward claiming scheme. I'm guessing it is something simple and dumb.

#3 - Will add additional "Fix if out of sync" logic. Need to run more competing UI scripts/plug-ins and see how they impact this.

I Luave Overseer. Thank you.

That was worth 10 points. Thank you.

p.s. I started adding your OverseerRewards logic into things but didn't get it completed and tested. Hopefully also over the next several days/week.

 

[GoldenFrog]

I started getting this error in my SK when I run Overseer. It gets to Common Conversion and stops. For some reason it only happens on my SK

Some questions for you:

• Does it always happen on the SK, or only some times?
• Is another plugin (like CWTN) active where the UI could be changing around during the Overseer run
• When this happens on the SK, can you screen shot the state of the Overseer UI? Curious if there are agents displayed and other states.

Just additional details:

That moment is when the script has hit Select Agent to see if there are enough to run the quest. This is done by checking:

• Are there any agents in the list
• Does the first agent have a number > 1 (or whatever is configured)

In your case it is seeing an agent but not the number in the corner. Very odd

 

[Berkz]

Here is more info for you Golden

1 Yes, always
2 Yes CWTN is running, however it didn't use to happen before
3 Attached is the screenshot of the overseer screen when the error happens

 

[Shadow]

I do a pause all, then run overseer, then end overseer, pause off. Cleaner, and works wonders.

 

[Rare Spawn]

@GoldenFrog thanks for the updated version, it fixed my issues. I wanted to offer up some feature suggestions for the backlog, for when things stabilize and your looking for a new challenge.

Duplicate Elite Agent management - Retiring duplicate purple agent to get tokens that offer rewards, many reward options are XP in any type of mission, but last option is for 2x blue rare agents.
Handling of Overseer items in inventory, such as claiming techno boxes, claiming agent banners, converting collection fragments into the collection dispensers.