• 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 (1 Viewer) 04/27/2026

No permission to download
@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.
Glad to hear things are working.

Ladon has a Lua script which does the handling of overseer items. He has given me permission to integrate it into this script, which I hope to do today/tomorrow. Until then you can run his script:
https://www.redguides.com/community/threads/overseerrewards.82967/

The Duplicate Elite Agent processing is on the backlog. I'm always a bit nervous coding destructive things but it is half-written and think it's solid. Hope to push that shortly as well.
 
I do a pause all, then run overseer, then end overseer, pause off. Cleaner, and works wonders.
I actually tried that after GF's post but I got the same error in the same place in the process
 
GoldenFrog updated Overseer with a new update entry:

2.8: General Corrections, Claiming Agent Packs

  • Handful of general bug fixes in the LUA port
  • Optional ability to automatically claim Agent or Tetradrachm packs
  • Using...

Read the rest of this update entry...
 
GoldenFrog updated Overseer with a new update entry:

2.10: Resolved Issue with LIP Helper Script

This is now version 2.8 - with a correction in our INI LIP Loading routine.
Original update notes from 2.8:

  • Handful of general bug fixes in the LUA port
  • Optional ability to automatically claim Agent or Tetradrachm packs
    • Running the first time should add two new configuration entries:
      • claimAgentPacks=0
      • claimTetradrachmPacks=0
    • Change either to "=1" to enable automatic claiming of the appropriate packs
    • Special thanks to...

Read the rest of this update entry...
 
FYI Golden, I tried running this on my SK again after the update and still have the same issue. Didn't think the update was meant to fix this as it seems to be a "me problem", but wanted to let you know anyway. Running the mac on SK in the meantime
 
I stopped using the Overseer Lua because it would fail when running multiple accounts at once. Hopefully that's fixed by now? I feel as if it was trying to read config files concurrently that caused the issues.
 
I stopped using the Overseer lua because it would fail when running multiple accounts at once. Hopefully that's fixed by now? I feel as if it was trying to read config files concurrently that caused the issues.
Are you using the global settings or per-character INIs?

Overseer.ini

INI:
[General]
useCharacterConfigurations=1
 
I stopped using the Overseer lua because it would fail when running multiple accounts at once. Hopefully that's fixed by now? I feel as if it was trying to read config files concurrently that caused the issues.
I'm only running 7 characters - but they all run the Lua at once and I haven't seen issues related to that.

Do you have any more information on what kind of failures or errors you saw?
 
I'm only running 7 characters - but they all run the LUA at once and I haven't seen issues related to that.

Do you have any more information on what kind of failures or errors you saw?

It was back in October. I'll try to run the newer version of the .Lua to see if I can still reproduce these.


Also it was killing KA on me:

I'll have to run a few characters on Lua+KA to test this out.
 
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.
How would you set it to run once and end? I would like to do so.
 
Maybe repeatTimeMinutes=0?


From the instructions page:
  • repeatTimeInMinutes: If 0, will not restart. If -1, will restart when next quest is ready. If > 0, will just repeat every specified amount of minutes
 
In addition to setting repeatTimeMinutes=0 , part 2 of my setup is creating server_character.cfg files (documented here) that autoruns overseer and a few other plugins/luas when the character enters the world.
Yeah! I use /mac overseer as part of my ingame.cfg (among other things I throw in there) just so I can load a character, go use the restroom or grab a drink etc, and then carry on with my day.
 
GoldenFrog updated Overseer with a new update entry:

2.12: Add Ability to Run Specific List of Quests (i.e. Holiday Events)

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

Read the rest of this update entry...
 
I decided to try the overseer.Lua again since you appear to be making more updates to it than the macro.

1671404692959.png

Didn't end well.


No special section was added, but it does looked like my config file was re-arranged after updating it just before the Lua script crashed:

[CODE title="Overseer_Charactername.ini"][General]
minimumSuccessPercent=70
ignoreRecruitmentQuests=0
version=2
maxLevelForClaimingExpReward=120
claimAgentPacks=0
maxLevelPctForClaimingExpReward=95
agentCountForConversion=4|3|2
claimRewards=1
minimumQuestExperience=0
questSelectionType=Priority
useFastAgentSelection=1
ignoreConversionQuests=0
monitorQuestRotation=0
logLevel=2
countAgentsBetweenCycles=0
storeQuestExperienceHistory=0
claimTetradrachmPacks=0
repeatTimeMinutes=-1

[QuestPriority_Unsubscribed]
Durations=6h|12h|24h
Levels=1|2|3|4|5
Priorities=Levels|Rarities|Types|Durations
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Recruitment|Exploration|Diplomacy|Trade|Crafting|Harvesting|Research|Plunder|Military|Stealth

[Rewards]
1=Terror of Luclin
2=Collection Item Dispenser
3=Overseer Tetradrachm
index=3

[QuestPriority]
Durations=6h|12h|24h
Levels=1|2|3|4|5
Priorities=Levels|Rarities|Types|Durations
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Recruitment|Exploration|Diplomacy|Trade|Crafting|Harvesting|Research|Plunder|Military|Stealth
[/CODE]


I have overseer run in my ingame.cfg file, and it crashed on accounts 1, 2, 3, 4, 5, 6, 11, 12. Accounts 7-10 ran through without problems, and all of my config files are the same except for the order of tradeskills they each claim.
I used autologin for all 12 accounts at once.
 
[Rewards]
1=Terror of Luclin
2=Collection Item Dispenser
3=Overseer Tetradrachm
index=3

[/CODE]


I have overseer run in my ingame.cfg file, and it crashed on accounts 1, 2, 3, 4, 5, 6, 11, 12. Accounts 7-10 ran through without problems, and all of my config files are the same except for the order of tradeskills they each claim.
I used autologin for all 12 accounts at once.

I will look into that error when back at the system.

The Lua LIP save routine does re-order items within a section, but should have no impact other than being annoying.
To verify, you aren't saying the order of tradeskill was changed in a meaningful way, correct? For example, you didn't initially want Collection Item Dispenser as #1 and it re-arranged that, correct?
 
To verify, you aren't saying the order of tradeskill was changed in a meaningful way, correct? For example, you didn't initially want Collection Item Dispenser as #1 and it re-arranged that, correct?
Correct, just the sections themselves re-ordered. Should have no impact I would imagine, just a note that it did touch the .ini file.
 
I will look into that error when back at the system.

The LUA LIP save routine does re-order items within a section, but should have no impact other than being annoying.
To verify, you aren't saying the order of tradeskill was changed in a meaningful way, correct? For example, you didn't initially want Collection Item Dispenser as #1 and it re-arranged that, correct?

This is the closest thread to the same problem that I am having with running the overseer script. I have the same exact script on all of my 14 accounts and yet a couple of the accounts just keeps making the Collection Dispenser Fragments instead of the Mercenary AA's which I have as 1. Mercenary Experience 2. Character Experience 3. Overseer Tetradactyl (ha ha)!!! So, It is beyond my comprehension why it would keep defaulting to the Collection Bowls of Jelly Beans! What am I doing wrong ladies and gents?? My Config file looks as follows:

[Debug]
doNotFindAgents=0
doNotRunQuests=0

[General]
version=1
claimRewards=1
repeatTimeMinutes=-1
minimumSuccessPercent=0
logLevel=2
agentCountForConversion=2
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
countAgentsBetweenCycles=0
monitorQuestRotation=0
questSelectionType=Priority
minimumQuestExperience=0.0
storeQuestExperienceHistory=0
useFastAgentSelection=1

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

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

[Rewards]
1=Mercenary Experience
2=Character Experience
3=Overseer Tetradrachm
 
This is the closest thread to the same problem that I am having with running the overseer script. I have the same exact script on all of my 14 accounts and yet a couple of the accounts just keeps making the Collection Dispenser Fragments instead of the Mercenary AA's which I have as 1. Mercenary Experience 2. Character Experience 3. Overseer Tetradactyl (ha ha)!!! So, It is beyond my comprehension why it would keep defaulting to the Collection Bowls of Jelly Beans! What am I doing wrong ladies and gents?? My Config file looks as follows:

[Debug]
doNotFindAgents=0
doNotRunQuests=0

[General]
version=1
claimRewards=1
repeatTimeMinutes=-1
minimumSuccessPercent=0
logLevel=2
agentCountForConversion=2
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
countAgentsBetweenCycles=0
monitorQuestRotation=0
questSelectionType=Priority
minimumQuestExperience=0.0
storeQuestExperienceHistory=0
useFastAgentSelection=1

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

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

[Rewards]
1=Mercenary Experience
2=Character Experience
3=Overseer Tetradrachm
Looks like you are missing your index=3 for your rewards.
 
What does the index do and does the #3 pertain to something specific?
Deified is right but I that shouldn't be your problem.

INI:
[Rewards]
index=3
1=Mercenary Experience
2=Character Experience
3=Overseer Tetradrachm
4=Something Else
5=Another

The "index" tells it how many entries to read. In this case it's saying use 1, 2, and 3. 4 and 5 will be ignored.
Yours is reading Mercenary Experience and not the other two.

Couple notes first:
  • Character Experience gives more mercenary experience than Mercenary Experience.
    • Since the change to give Mercs exp even when suspended, Mercenary Experience isn't the best option for any situation any longer
  • The Reward chooses the first available, so Merc, Char, Tetradrachm, etc..
    • Since all options have Character Experience, nothing after that choice will happen
    • If you want Tetradrachm when available, else Character Experience, flip those
    • 1=Overseer Tetradrachm
    • 2=Character Experience
There has been a few hiccups in rewards not being claimed, but hadn't heard of incorrect ones before.
Don't think I'd seen mis-collects before. Let me get some more information on this.
 
Is there an option to have the script exit at end, when quest log is full?

I use kiss and don't want this starting up again while fighting.
 
Is there an option to have the script exit at end, when quest log is full?

I use kiss and don't want this starting up again while fighting.
@BlankStare described in post 137 for me the use of "repeatTimeMinutes=0"
This will cause Overseer to run once and end. This solved for me the interferences with kissassist.
 
That first error indicates you aren't running MQ2Next, but are choosing Experience-sorted quests:
INI:
questSelectionType=Exp

If you truly aren't using next, this should be Priority.
Few questions. That error indicates you aren't running MQ2Next, but are choosing Experience-sorted quests:
INI:
questSelectionType=Priority

The second error is due to the script expecting that value to be there. I will update the logic to enforce a default ('Priority')

Looks like a different twist on the error:

1673563953104.png

First time trying the Lua version out. Going to take a look at the ini to see if anything needs tweaking. It works fine for the mac version.
 
@GoldenFrog

This is the line that is causing issues with macros, i commented it out and everything seems to work just fine (both overseer and kiss)[CODE title="overseer.Lua line 1382"]-- FailedQuest_AddMinionToCurrentPendingCache(mq.parse('${${bestAgent}.Child[OW_OQP_MinionNameBtn].Text}'))[/CODE]
 
If you start the macro on one toon with overseer enabled, then relog to another toon (who is <85 for instance), on expiration of the rechek timer the script tries to open /overseer for ~ 20 times in a second or so :-)

Maybe there could be a check if the currently logged in char is at least > 85?
 
If you start the macro on one toon with overseer enabled, then relog to another toon (who is <85 for instance), on expiration of the rechek timer the script tries to open /overseer for ~ 20 times in a second or so :-)

Maybe there could be a check if the currently logged in char is at least > 85?

Been meaning to do this, but wasn't sure what the exact behavior should be on character change.

I would guess most people only want to run on the character it was initiated on. Logging to an alt should end the script or skip until original character returns.

For now, I'll add a check and if <85, wait for configured repeat time or exit if none.
 
@GoldenFrog

This is the line that is causing issues with macros, i commented it out and everything seems to work just fine (both overseer and kiss)[CODE title="overseer.lua line 1382"]-- FailedQuest_AddMinionToCurrentPendingCache(mq.parse('${${bestAgent}.Child[OW_OQP_MinionNameBtn].Text}'))[/CODE]
Thank you, winnower. The issue was specifically the mq.parse - was a miss in the Lua port. I updated.

Though with the next patch, all of this will become obsolete and [Run All] will take over the world!
 
It seems the latest update broke the repeatTimeMinutes=-1 feature. Script now just ends instead of looping.
 
Release Overseer

Users who are viewing this thread

Back
Top
Cart