Kuhle
Sergeant
Not sure why you are crashing. I've done 8 conversions in a row and not crashed.
-
Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
- Thread starter GoldenFrog
- Start date
Large numbers make /mac overseer crash. always has. If you run it when you have more than 400 overseer agents, it will crash when it counts them.
Kuhle
Sergeant
Well, with that being said, have you tried turning off agent counts between conversions to see what happens?
Edit: nevermind. Stupid suggestion
Well... its currently crashing while its converting. Not just when its counting. This account has a ton of common agents.
Should the Overseer.ini look like this after turning off UseCharacterConfigurations=1 ?
Code:
[General]
useCharacterConfigurations=0
monitorQuestRotation=0
storeQuestExperienceHistory=0
questSelectionType=Priority
minimumQuestExperience=0.0
useQuestPriorities=**Obsolete**
useFastAgentSelection=1
version=1
[QuestPriority]
Priorities=Levels|Durations|Rarities|Types
Durations=6h|12h
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]
index=0
1=Overseer Tetradrachm
2=Character Experience
3=Mercenary Experience
Rubicite
Member
Supposedly, DBG can detect "ultra fast" (e.g., faster than humanly possible) mouse selections. That's what happens when using the current Overseer macro. Maybe slow things down and/or add in some randomness. I can't speak for others, but the speed of the Overseer macro is NOT what attracts me to it. I use it to automate the tedious mouse clicking for task and agent selection. I don't really care if the macro takes 45 - 60 seconds longer to complete. Thank you.
There's a new Recruitment task available called "Season of Flame", a Level 1 Uncommon Recruitment task. It just showed up today in my task feed. The current iteration of Overseer.mac did not pick up this task automatically even though I'm set to:
My Overseer settings
My Overseer settings
Code:
[General]
useCharacterConfigurations=1
claimRewards=1
repeatTimeMinutes=-1
minimumSuccessPercent=66
logLevel=2
agentCountForConversion=6|6|6|5
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
useFastAgentSelection=1
version=1
monitorQuestRotation=0
storeQuestExperienceHistory=1
questSelectionType=Exp
minimumQuestExperience=0.2
[QuestPriority]
Priorities=Rarities|Durations|Levels
Rarities=Elite|Rare|Uncommon|Common|Easy
Durations=24h|12h|6h
Levels=5|4|3|2|1
Types=Any
[QuestPriority_Unsubscribed]
Priorities=Rarities|Durations|Levels
Rarities=Elite|Rare|Uncommon|Common|Easy
Durations=24h|12h|6h
Levels=5|4|3|2|1
Types=Any
[Rewards]
index=2
1=Overseer Tetradrachm
2=Character Experience
To add my two coppers to the pile, my use of overseer did run the new recruit task "Season of Flame".
Funnily, I have recruits turned off.
ignoreRecruitmentQuests=1
On my veteran accounts, they have all the overseer types at "Max"/"5".
I even double checked, when I saw the "Season of Flame" was listed in green as a level 1 recruitment.
The regular recruit task, (which it skips), was listed as a level 5 recruitment.
I'll have a look into this.
For the curious, I share the overseer ini I've used recently.
overseer.ini
Regards and Best Wishes
Funnily, I have recruits turned off.
ignoreRecruitmentQuests=1
On my veteran accounts, they have all the overseer types at "Max"/"5".
I even double checked, when I saw the "Season of Flame" was listed in green as a level 1 recruitment.
The regular recruit task, (which it skips), was listed as a level 5 recruitment.
I'll have a look into this.
For the curious, I share the overseer ini I've used recently.
overseer.ini
INI:
[General]
useCharacterConfigurations=0
claimRewards=1
repeatTimeMinutes=0
minimumSuccessPercent=80
requireMercToClaimExpRewards=0
logLevel=2
useQuestPriorities=1
agentCountForConversion=3
ignoreConversionQuests=0
ignoreRecruitmentQuests=1
countAgentsBetweenCycles=0
useFastAgentSelection=1
version=1
[QuestPriority]
Priorities=Rarities|Durations|Levels|Types
Durations=12h|24h|6h
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Any
Levels=0
[QuestPriority_Unsubscribed]
Priorities=Rarities|Durations|Levels|Types
Durations=12h|24h|6h
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Any
Levels=0
[Rewards]
index=3
1=Character Experience
2=Mercenary Experience
3=Overseer TetradrachmRegards and Best Wishes
@B_I_G__D_A_D_D_Y I have had a look at the overseer macro code.
I think the decider is the title of the quest.
@GoldenFrog
To find a recruit quest, it reads like its looking for "Recruit" in the name of the quest.
Similar, when it's looking for quests to run, it looks to exclude those with "Recruit" or "Conversion" in the name, as those are respectively handled in other sections of the macro.
Given that the new recruitment quest doesn't mention "Recruit" in title, the code perhaps requires amendment.
The UI property, OW_ALL_DifficultyLabel, could be parsed instead of the quest title.
As an aside comment, I note at least one character of mine is running "A Devotee's Quest", a level 2 recruitment.
I'm guessing there could well be more that come at higher levels.
Plus, I think DBG are introducing this as a seasonal thing, and so there may be other variations as the year progresses.
Regards and Best Wishes
I think the decider is the title of the quest.
@GoldenFrog
To find a recruit quest, it reads like its looking for "Recruit" in the name of the quest.
Similar, when it's looking for quests to run, it looks to exclude those with "Recruit" or "Conversion" in the name, as those are respectively handled in other sections of the macro.
Given that the new recruitment quest doesn't mention "Recruit" in title, the code perhaps requires amendment.
The UI property, OW_ALL_DifficultyLabel, could be parsed instead of the quest title.
As an aside comment, I note at least one character of mine is running "A Devotee's Quest", a level 2 recruitment.
I'm guessing there could well be more that come at higher levels.
Plus, I think DBG are introducing this as a seasonal thing, and so there may be other variations as the year progresses.
Regards and Best Wishes
Thank you!
On a temporary basis and based on your input I found the line of code which calls the Recruit task and added my own extra line to it.
Added to specifically grab the Season of Flame quest!
Code:
/call EnumerateAvailableQuests IsQuestByName ProcessGeneralQuest "Recruit"
/call EnumerateAvailableQuests IsQuestByName ProcessGeneralQuest "Season of Flame"Most recent modification here, showing the entire subroutine to ensure I run the "new" recruitment tasks...
RunRecruitTasks
INI:
Sub RunRecruitQuests
/call AreAtMaxQuests
/if (${Macro.Return}) /return
/if (${Ini[${MyIni},General,ignoreRecruitmentQuests]}) {
/call Log "Skipping recruitment quests (per configuration)."
/return
}
/call ChangeTab 1
/call LoadAvailableQuests
/call EnumerateAvailableQuests IsQuestByName ProcessGeneralQuest "Recruit"
/call EnumerateAvailableQuests IsQuestByName ProcessGeneralQuest "Divine Intervention"
/call EnumerateAvailableQuests IsQuestByName ProcessGeneralQuest "A Devotee's Quest"
/call EnumerateAvailableQuests IsQuestByName ProcessGeneralQuest "Season of Flame"
/returnMany thanks to @GoldenFrog for creating this awesome macro in the first place. I wish I had the skills to "fix" this correctly!
Last edited:
Seen this statement I checked Overseer and saw that I had 621 Agents.
In order to reduce the amount of Agents, I changed
Conv1
Code:
ignoreConversionQuests=1Conv2
Code:
ignoreConversionQuests=0At the next start of Overseer, it crashed right after the launch of the first conversion-Quest.
As I didn't want to click manually a hundred+ of conversions, I wrote a litte Lua:
OverLoop
Code:
local mq = require("mq")
while true do
mq.cmd("/mac overseer")
mq.delay(1)
mq.cmd("/doevents")
mq.delay('30s')
endIf someone wants to use it, you may modify "mq.delay('30s')" to "mq.delay('40s')" or even a higher delay, in order to make it work for you.
The amounts of seconds to wait befor the next loop starts depends on the potency of your PC. Befor the Overseer.mac relaunches you shall see, that a new conversion-quest should be started.
For my PC its at about 25 seconds after the launch of overseer.mac.
The Lua does nothing but restarting overseer.mac infinite after the number of seconds definded in the line: "mq.delay('30s')"
A dirty solution which brought me from 621 Agents down to 378 Agents within one our.
After that I stopped all Luas with "/Lua stop" and launched /mac overseer once manually.
Now overseer is working as expected and will reduce the amount of Agents below 200.
DE Boxing
Member
I was thinking the same thing, especially when I ran the macro and saw how fast it blew through Overseer. I actually made an updated version of the macro locally that adds some config options to define a min and max delay that gets added to all the base delays already in the macro as well as an option to disable these randomized delays if someone doesn't want them. I also added a config flag to have it run everything once and then exit just using my config files, so I can simply call '/mac overseer' and it runs everything, with an added 1/2 sec to 5 sec delay between each action by default, and when it's done it exits the macro so I don't have to specify '/end' each time I run it as I don't want it running all the time in the background.
I'd be happy to share these changes with GoldenFrog to consider adding to the main script for the community. If GoldenFrog is not interested I am sure we can figure something out. I feel much better now when I run it as it takes about as long as I would to do it manually, which was my intention all along.
In regards to sharing these changes, is this something I can simply add to the discussion or would I need to clear any changes with GoldenFrog first? New to the community and don't know the policy on altering other peoples macros.
Last edited:
DE Boxing
Member
Since I didn't hear back from anyone on this I will share snippets of code for the changes I made:
:countdownloop (after line 93)
Code:
/if (${Ini[${MyIni},General,runOneTime]}) {
/call Log "Ending macro after one overseer check cycle (per configuration)."
/endmacro
}AFTER: Sub Parameterized(string arg) (~line 162)
Code:
| Get a randomized delay time in milliseconds to slow down macro execution and randomize UI interaction times so it's not so obvious these actions are a macro in any server logs.
| If useRandomDelay = 0, then this simply returns baseDelayTimeMilliseconds (the original behaviour).
Sub GetRandomizedDelayTimeMilliseconds(int baseDelayTimeMilliseconds)
/declare result int local ${baseDelayTimeMilliseconds}
/if (${useRandomDelay}) {
/declare randomizedDelay int local ${Math.Rand[${maxRandomDelayTimeMilliseconds}]}
/if (${randomizedDelay} < ${minRandomDelayTimeMilliseconds}) {
/varset randomizedDelay ${Math.Calc[${randomizedDelay}+${minRandomDelayTimeMilliseconds}]}
}
/varset result ${Math.Calc[${baseDelayTimeMilliseconds}+${randomizedDelay}]}
/call DebugLog 3 "Adding randomized delay of ${result} ms"
} else {
/call DebugLog 3 "Adding base delay of ${result} ms"
}
/return ${result}UPDATE: Sub EnsureIniDefaults (~ line 1707)
Code:
/if (${Ini[${MyIni},General].Length} == 0) {
| *** existing /ini ${MyIni} statements ***
/ini ${MyIni} "General" "useRandomDelay" "0"
/ini ${MyIni} "General" "minRandomDelayTimeMilliseconds" "500"
/ini ${MyIni} "General" "maxRandomDelayTimeMilliseconds" "5000"
/ini ${MyIni} "General" "runOneTime" "0"
} else /if (${Ini[${MyIni},General,ignoreConversionQuests].Equal[NULL]}) {
| *** existing /ini ${MyIni} statements ***
}
/if (${Ini[${MyIni},General,useRandomDelay].Equal[NULL]}) {
/ini ${MyIni} "General" "useRandomDelay" "0"
}
/if (${Ini[${MyIni},General,minRandomDelayTimeMilliseconds].Equal[NULL]}) {
/ini ${MyIni} "General" "minRandomDelayTimeMilliseconds" "500"
}
/if (${Ini[${MyIni},General,maxRandomDelayTimeMilliseconds].Equal[NULL]}) {
/ini ${MyIni} "General" "maxRandomDelayTimeMilliseconds" "5000"
}
/if (${Ini[${MyIni},General,runOneTime].Equal[NULL]}) {
/ini ${MyIni} "General" "runOneTime" "0"
}UPDATE: Sub Initialize (after '/call EnsureIniDefaults' ~line 1822)
Code:
/declare useRandomDelay int outer ${Ini[${MyIni},General,useRandomDelay]}
/declare minRandomDelayTimeMilliseconds int outer ${Ini[${MyIni},General,minRandomDelayTimeMilliseconds]}
/declare maxRandomDelayTimeMilliseconds int outer ${Ini[${MyIni},General,maxRandomDelayTimeMilliseconds]}Once all of those changes are made the rest of the changes are to alter the '/delay' statements so they use the new Sub GetRandomizedDelayTimeMilliseconds.
Here are a few examples:
Examples:
Code:
| Replace
/delay 1s
| With
/delay ${GetRandomizedDelayTimeMilliseconds[1000]}ms
| Replace
/delay 1s (${Window[OverseerWnd].Child[OW_Subwindows].Child[${Tabs[${tabIndex},2]}].Open})
| With
/delay ${GetRandomizedDelayTimeMilliseconds[1000]}ms (${Window[OverseerWnd].Child[OW_Subwindows].Child[${Tabs[${tabIndex},2]}].Open})
| Replace
/delay 5
| With (delay number alone means 10th second or 100 ms)
/delay ${GetRandomizedDelayTimeMilliseconds[500]}msAll delays are in ms, so change all delays into corresponding milliseconds.
I did not change the delay between each cycle as that delay is in minutes, though thinking about it now it it might make sense to add a random delay of 5-15 minutes between cycles so overseer does not run immediately after one is finished. Not super efficient but then again doesn't look like it's a program either.
Finally, you can just add these settings to your INI file(s) to turn this on or off as well as change min/max delays or if you want it to only run once and exit.
Example INI changes
INI:
[General]
# existing lines
useRandomDelay=1
minRandomDelayTimeMilliseconds=500
maxRandomDelayTimeMilliseconds=5000
runOneTime=1I hope this helps out anyone like me who wants it to run more randomly so it doesn't look like it's being done by a macro.
Something like that method I created would probably work to delay other functionality to make it less obvious it's a macro. I haven't looked into it because it's beyond my knowledge but my thought is if functionality like this could be added to the actual /delay method it could go a long way to making this all seem less robotic. I would think simply something like '/delay {minTimeInTimeUnits} {maxTimeInTimeUnits}' would be great. Add to that a base setting in main INI file that calculates maxTimeInTimeUnits for calls that do not provide it (ie. all legacy calls) and you could add a randomized delay anywhere a delay command is called and even give the end user the ability to tweak the delay timings.
Hope this is of some help. Also, if I am allowed to post the updated file I did, just let me know and I will.
Tangtown
Well-known member
If you haven't maxed your tradeskills I would go that route, you can almost max everything for free using overseer. Collectibles once TS is done, merc xp comes automatically now anyway and the currency is useless (plus with the new achievements you will get free currency).
After this most recent EQ patch (July, 2022) my Overseer will miss conversion quests. It could be my machine, or my slow ass ISP. I opened Overseer.Mac and did a global search and replace of all
/delay 1s and /delay 2s and made them all /delay 3s and it's no longer skipping the conversions.
Tangtown
Well-known member
There is no need to put multiple xpacs down for rewards, if you can do a tradeskill task you can always select any xpac you want. I would probably go with ToV or CoV whichever provides the most logs/pelts/ores per shot. Your 2 and 3 will be what to pick if there is no Research or Crafting available to complete so I would put 2=Collection Item Dispenser 3=mercenary experience if you already have your xp maxed.
Some info on the tradeskilling -
With the research or crafting overseer you can select tradeskill materials as your reward. There are a few tradeskill recipes that cost almost nothing other than the droppable material you get from Overseer. A few examples below using the ToV rewards, but iirc the CoV rewards might give you even more of the TS items per task and there is a recipe very similar for those as well. You can do the same for anything from RoS up though
Research I went with Ethernere essences from CotF and made guidestones (Jande has a macro that makes this easier https://www.redguides.com/community/resources/jandes-guidestone-300-research-macro.1395/)
Pottery, baking, brewing there is recipes that only take cheap vendor items so no need to farm overseer (there may be overseer routes but I didn't use them)
Jewelcraft I used all vendor purchased items, it seems expensive but you get a decent return on vendoring so it isn't that bad. (also can probably use overseer but I didn't go this route)
Fletching Use wood from Overseer- http://www.eqtraders.com/items/show_item.php?item=64565&menustr=010000000000 (note that you can do this with conflag from RoS or various other xpacs, similar for Smithing and Tailoring below)
Smithing Ore from Overseer - http://www.eqtraders.com/items/show_item.php?item=64557&menustr=035000000000
Tailoring Pelts/Skins from Overseer - http://www.eqtraders.com/items/show_item.php?item=64558&menustr=010000000000
I'm having a problem with/mac overseer
It was working It was working fine for a while and out of nowhere instead of collecting character experience from the overseer character ini file it keeps collecting the tetradicjm currency instead . Any idea? It does this on 20 toons logged into at once when I type /bcaa //mac overseer
It was working It was working fine for a while and out of nowhere instead of collecting character experience from the overseer character ini file it keeps collecting the tetradicjm currency instead . Any idea? It does this on 20 toons logged into at once when I type /bcaa //mac overseer
this was confusing for a few of us. this 1=, 2=, 3= order - you have to make them the order what you want
this does exp first, then overseer, then merc
INI:
1=Character Experience
2=Overseer Tetradrachm
3=Mercenary ExperienceIf your INI files are correct I would suspect lag is causing the macro to encounter problems selecting the correct things. After the July patch I had to edit my overseer.mac and double or even triple all the /delay statements. Even now it still doesn't perform flawlessly like it used to.
Reboot your PC, load up a character, try Overseer.mac on just one and confirm it's working as you intend. Then load up the rest of your army and try them all at once. I only ever do 6 chars at a time.
Interesting that you say it is lag. I am starting to suspect that too as I have a torrent downloader going in the background too. I will try that thank you
I'm under 1000 agents and it will only reliably do a single conversion quest each pass of the macro. That's because the server will not present the conversion quest again in time for the macro to detect it. I'm not good enough to figure out how to delay the macro until the quest window repopulates correctly. So I just keep restarting the macro or do the conversions by hand.
Not sure what is happening but my overseer doesn't start any new questions other than recruitment now...
INI:
[General]
version=1
claimRewards=0
repeatTimeMinutes=0
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=Rarities|Types|Levels|Durations
Durations=any
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Recruitment|Exploration|Trade|Harvesting|Crafting|Plunder
Levels=5|4|3|2|1
[QuestPriority_Unsubscribed]
Priorities=Rarities|Types|Levels|Durations
Durations=any
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Recruitment|Exploration|Trade|Harvesting|Crafting|Plunder
Levels=5|4|3|2|1
[Rewards]
index=0
1=Tradeskill Item
2=Collection Item Dispenser
3=Character Experience
Last edited by a moderator:
Durations in the two places its listed should be Durations=6h|12h
Also, you're not claiming rewards but at the bottom you have 1=Tradeskill Item. This wont work, to get those type of items the name of the reward is an expansion name such as 1=Claws of Veeshan to claim the Tradeskill items available from that expansion. If you want to do that you have to set claimRewards=1
I didn’t think claim awards worked… what do I put for collection item too?
The below will run through, do the quest and collect the rewards (collection items in my case).
INI:
[General]
useCharacterConfigurations=0
claimRewards=1
repeatTimeMinutes=-1
minimumSuccessPercent=70
requireMercToClaimExpRewards=**Obsolete**
logLevel=2
useQuestPriorities=**Obsolete**
agentCountForConversion=0|2|2
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
countAgentsBetweenCycles=0
useFastAgentSelection=1
version=1
monitorQuestRotation=0
storeQuestExperienceHistory=0
questSelectionType=Priority
minimumQuestExperience=0.0
[QuestPriority]
Priorities=Levels|Durations|Rarities|Types
Durations=6h|12h|24h
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Exploration|Diplomacy|Trade
Levels=5|4|3|2|1
[Rewards]
index=3
1=Collection Item Dispenser
2=Overseer Tetradrachm
3=Tradeskill Items
[QuestPriority_Unsubscribed]
Priorities=Levels|Durations|Rarities|Types
Durations=12h|6h
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Any
Levels=5|4|3|2|1
Last edited by a moderator:
Fixed it and worked great on collections! Man, why didnt I have this on sooner!
Request for Durations=Any to be a valid option. A lot of my guys end up with tons of tradeskill items and very few (sometimes zero) collection fragments.
Code:
Priorities=Levels|Rarities|Types|Durations
Durations=6h|12h|24h
Rarities=Elite|Rare|Uncommon|Common|Easy
Types=Any
Levels=1|2|3|4|5What you probably want to do is remove duration from the priority list, that way it wont matter in selection.
Priorities=Levels|Rarities|Types
Wait. No shit. You can?
I put levels in first so that it hits any new anniversary/special/limited ones, but did not realize you could exclude the Durations.