BayouGator
Member
That did the trick. Everything's running fine again. Thanks for the quick response and thanks for creating this macro. It is such a time saver.
-
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
That did the trick. Everything's running fine again. Thanks for the quick response and thanks for creating this macro. It is such a time saver.
Yes, i am using a custom UI. I will look at the error for that screen and put it in.
I forgot to update this!
I think I might have caused my own problem by frequent loading and unloading the MQ2 system that day. I was having a problem getting MQ2Nav to work in PoK so I had unloaded all of MQ2 and then reloaded it while my characters were all running. I had previously found that I have many fewer problems if I launch MQ2 and then launch Innerspace which actually then loads my EQ sessions.
So I suspect I caused my own issues with lots of weird artifacts left in memory.
- Commits
- 6
That would be good if that's all it was. I wasn't able to make much headway on that issue. Hopefully yer all resolved, then.
There's a shadowy mob outside of the PoK library on one of the sides, "a mysterious presence" or something, which sells you ornamentations and other things. It's on Find (CTRL+F).
Smokeybear72
Only YOU can prevent forest fires !
Can this get stickied int the Overview section?
I would like to auto-claim Collection fragments #1, and Overseer Tetras #2. Is there a way to configure that for now? I have been manually claiming my rewards.
Any thought into claiming regular experience if character's experience is below ##%? Such as, trying to keep the level 115s capped, if my level 115 exp is below 90%, then claim experience to keep me near cap. Just an idea.
Any thought into claiming regular experience if character's experience is below ##%? Such as, trying to keep the level 115s capped, if my level 115 exp is below 90%, then claim experience to keep me near cap. Just an idea.
- Commits
- 6
I would like to auto-claim Collection fragments #1, and Overseer Tetras #2. Is there a way to configure that for now? I have been manually claiming my rewards.
Any thought into claiming regular experience if character's experience is below ##%? Such as, trying to keep the level 115s capped, if my level 115 exp is below 90%, then claim experience to keep me near cap. Just an idea.
Now that's an awesome suggestion on the exp if < 90% kind of thing. Worth a look.
For your first comment - I'm not fully clear what you are asking for. Are you saying only collect 1 fragment a day and tetras the rest kinda thing?
[Rewards]
index=0
1=Overseer Tetradrachm
2=Character Experience
3=Mercenary Experience
Is it possible to place Collection fragments as the first option? And if no collection items as reward options, then take overseer tetras? Or, choosing tradeskill items as a reward option? I know folks who choose the TS items, although I don't.
Does this option work if I change claimReward=1 and index=3? The Overview page for this resource indicates that it is not currently working.
I had originally thought that using Overseer for exp was an awesome way to keep capped at your level (whether your level cap is 115 or 110), so hence my idea for character experience. Although if you're at 99% exp already, claiming experience as a reward is pointless.
You have the correct idea.
index=3 (how many options you want to try)
then your order is correct.
So what will happen is if there is a coin claim, it if not try second option, etc .
Claiming works correctly IF you do not have other rewards outstanding. e.g overseer claim hast to start on the first tab in reward window.
Code:
claimRewards=1
index=3
1=Collection Item Dispenser
2=Mercenary Experience
3=Overseer TetradrachmThis is not making much sense to me, is it counting duplicates or are there agents the macro does not know about ?
Look at uncommon iconic / uncommon / common
Okay see what is going on the status Exhausted etc is also in the name so causing macro to count them as a unique agent
In Sub OutputAgentCounts added line 4 - 6
Have my doubts about buying agent packs from the vendor. Bought about 60 on one account now have 162 unique agents, other account that I never bought any on is at 167 unique ones. Guessing it is just random messing with me it sure feels like the packs did not help.
Look at uncommon iconic / uncommon / common
Okay see what is going on the status Exhausted etc is also in the name so causing macro to count them as a unique agent
In Sub OutputAgentCounts added line 4 - 6
Code:
/varset agentName ${${agentNode}.Child[OW_OM_MinionEntry].Text}
/if (${agentName.Find[:]}) {
/varset agentName ${agentName.Arg[1,:]}
}
/if (!${agentName.Equal[${previousAgentName}]}) {Have my doubts about buying agent packs from the vendor. Bought about 60 on one account now have 162 unique agents, other account that I never bought any on is at 167 unique ones. Guessing it is just random messing with me it sure feels like the packs did not help.
Last edited:
It really isn't hard to log on your level 85+ characters, run the macro for a few minutes, and then log them off. Sure, automation would be cool, but that's a ton of effort for very little savings, imo.
The drunkard's stein macro was designed with a dual-purpose in mind: obtaining the task, and then adding others to it to help automate their moving multiple zones and dropping in the song lyrics. I used that macro for just the moving portion, for chain-acquiring the stein every few minutes.
- Commits
- 6
INI:
/declare agentNode string Window[OverseerWnd].Child[OW_OM_MinionList].FirstChild
/declare index int
:nextAgent
/varset agentName ${${agentNode}.Child[OW_OM_MinionEntry].Text}
/varset index ${agentName.Find[Status]}
/varset agentName ${agentName.Left[${index}]}I have one thing that did count duplicates. This happened if you had two agents of the same name, but in different states (one was "Available", the other was "Questing", for example).
Added the above code but hadn't pushed live yet. The index and agentName lines. Busy but will try to push this shortly.
Last edited:
- Commits
- 6
GoldenFrog updated Overseer Automation with a new update entry:
1.16
Read the rest of this update entry...
1.16
Read the rest of this update entry...
- Commits
- 6
So I was curious about this and wrote the functionality. It'll do every 85+ char or specified ones (i.e. "Char1|Char3"). Then I tested and ... had never done a different char on same account, apparently.
Tell me if I'm seeing something different from you, but all characters on an account use the same quests. So running 5 quests on char #1 is the same as char #2. This "Run on all chars" has no benefit.
(Unless I misunderstood the request).
Yeah, they share Overseer
drawthow
Well-known member
Oh, I didn't realize they all use the same quest. Have been logging toons and running the macro and walking away never really paid attention to what they are doing. Thanks for the info.
- Commits
- 6
The script is coded to do exactly this. If it isn't working for you, say so. But that has been working for me from the start.
wymranar
I <3 SKs *kissy face*
Ive been running overseer manually and finally gave this mac a try. @GoldenFrog you're the man!
- Commits
- 6
There is a known bug between MQ2/EQ that gets in this situation. There are apparently two message boxes, etc...
The only solution I've found is to /camp out and back in. I wish I had more details for you right now.
I'll raise the flag again to see if there has been any movement on this. The
drawthow
Well-known member
Thanks for the info, I didn't realize this was that same problem. I was thinking with the extra test in the yes/no box it was a different issue.
- Commits
- 6
You are correct, but it's actually some rule preventing it in some cases, not all. Someone can clarify that rule, I always forget.
Smokeybear72
Only YOU can prevent forest fires !
I erased all my older INI's for overseer and had macro re-build all new ones. /mac overseer
It fixed the alts that were doing this.
- Commits
- 6
The reward name is still "Character Experience". The change was to an option line-item which isn't used in the quest determination.
The scripts appear to work for me still (and logically should). Are you seeing it get the coin alternative?
- Commits
- 6
Thank you, krawdad. I admit to never fully undersatnding that 10-max completed limit.
So when it says 10/10 we can continue to start quests up to the 5-at-a-time limit. But not [Finish] any.
(I know I may have just repeated what you said but mentally translating that into the script).
- Commits
- 6
Well that's disappointing. I'll bump the cap. We don't NEED a cap, just didn't want the script hanging up forever there if some bug occurred. Thanks, great1.
- Commits
- 6
GoldenFrog updated Overseer Automation with a new update entry:
1.17
Read the rest of this update entry...
1.17
Read the rest of this update entry...
Does this mean it's sitting at the conversion page for 2 minutes? They're like 6 second quests.
If they are taking longer, then it's because your computer clock is wrong -- which is a different discussion itself, complained about on the official EQ Forums numerous times.
- Commits
- 6
No this means it will ALLOW a quest to take that long to complete without erroring out.
As of the last patch (I think), the time is now advertised as 10s on all conversions for me, at least.
But if you watch, at times it's 10s, 20s, I've personally seen 30s but others seen longer. And that happens in sequential runs.
I hadn't seen those forum discussions but my computer clock is good - sync'd and all.