Release Overseer Automation (1 Viewer) 1.9

[BigDorf]

Correct @dontrootmebro looking to do recruitments as priority to have more agents added for better options later, followed by those with tradeskill items as rewards.

@Robban as you can see, i didnt change the "ignore" flag, so expected that as "0" ( false ), it should not ignore and do recruits.

But as shown, it did not, even though it was perfectly possible to do it.

i have more information to follow.

 

[BigDorf]

tl;dr
There is an operational bug, in what is reported between the "dry theory" run, versus the "live, really do it" run of the overseer macro.
/mac overseer generalList
vs
/mac overseer

The former, looks at but doesnt accept valid recruit quest tasks and goes on to state it would do other tasks instead.
The latter, does actually engage the recruit task correctly. Great! But, negates the value of the dry run.



Details

With this key bits of the character ini file:-

[CODE lang="ini" title="overseer char ini" highlight="4,10"]useQuestPriorities=1
agentCountForConversion=2
ignoreConversionQuests=0
ignoreRecruitmentQuests=0
countAgentsBetweenCycles=0

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


Since the post earlier today, another attempt at Overseer is made.
You can see above the ini file is configured to go for Recruitment, and then Craft, Harvest or Research.

There is a recruitment task quest in the listing, and I am able to manually assign it if I wished to.


Now again to the macro, and as it to process without starting the quests, as per the documents.
/mac overseer generalList

There is a lot of output as it goes throught the options which I will come back to, but first the summary it produces of what "generalList" says it would do.



It will go for a harvest, at 86%, and skipped the recruit fighters that was fully viable and 88% chance.

So lets go back to that processing information.
Types=Recruitment|Crafting|Harvesting|Research

Indeed, the first section it looked at is Recruitment, with a variety of combinations and then Crafting, then Harvesting.
Two interesting grabs of the output of the parsing, rememberng that a level 1 common recruitment is viable.


...


Now you can see clearly, it parses over the options and doesnt look at the recruitment, but does look at the harvest, which appears in the summary.

This makes no sense at all.

Now, there is a twist.

I havent changed anything, and re-run the macro to just do it.

/mac overseer



It does select the Recruit Fighters task!



This critically negates some value from "generalList" option of the macro, as it does not yield the same results, so isnt a true "dry run".
With the exception of skipping over recruits (grrrr!), it does however show the correct ordering of reviewing quest tasks as per the ini file rules, even though it doesnt make the right decision ( took harvest over recruit ).


Whilst Im fine to use the macro as is, now that I understand this bug / feature, hopefully this write-up will help others if they encounter similar until the macro has a chance to be fixed.


Regards.

 

[B_I_G__D_A_D_D_Y]

@GoldenFrog when I was young I never understood the old saw, "No good deed goes unpunished!"

 

[GoldenFrog]

@GoldenFrog when I was young I never understood the old saw, "No good deed goes unpunished!"

Hah - well thanks. Still at work so missed this whole thread. With BigDorf having quite the write-up. When I get home I"ll catch up and see what can be done.


Thanks y'all.

 

[GoldenFrog]

Big Dorf you are completely correct in what you summarize - however there's one historical reason it works that way. The "generalList" and "generalListFast" were added (initally for myself) as diagnostics as to what your config would mean as far as running.

'Recruitement'and 'Conversion' were never part of the
Types=Recruitment|Crafting|Harvesting|Research

However I am noticing a new issue where recruitments aren't skipped but the "SELECT RECRUIT" step isn't working. Seems more pronounced if you skip conversions.

I am pushing an update which just fixes this then want to understand more exactly the problem you are seeing.

 

[GoldenFrog]

GoldenFrog updated Overseer Automation with a new update entry:

1.27

• Addresses small timing issue seen where first quest attempted may not actually be selected.
  • More pronounced if you skip Conversions, the first recruit may not be run.

Read the rest of this update entry...

 

[BigDorf]

I am pushing an update which just fixes this then want to understand more exactly the problem you are seeing.

Sorry, i dont know if that was a question, or a statement of intent. I will look to restate the problem from a high level.


The macro processes the ini files, the available agents the character has, and the list of quest tasks available to select at the moment. From these the macro makes decisions of what can be done.

By the description, for thse two modes of execution:-

• /mac overseer generalList
• /mac overseer

The decisons and selected quest tasks output should be the same. The only difference in activity, is the former is a "dry run" to evaluate without starting quest tasks, and the latter actually does commit the agents and starts the quest tasks in game.
i.e. using the "generalList", the macro runs and outputs "this is the decisions I have made for you, and would make these quest tasks active if you run again, without the parameter". Alas they arent.

As you say, the use of "generalList" is great to help the user to understand the consequences of properties in the ini file, and allow them to tweek, re-evaluate, until confident its right. Then go for the real run, to actually do the ingame assignments to quest tasks. That is a great plan, if it actually produced the same results for both modes of running.



I had configured in the ini file, Recruitment, were to be done, and it is listed as the first type to check.
It looks at the Recruitment tasks, but doesnt select them in the "generalList" dry run, but does in actual execution.

Whilst that end result is great, its doing what I wanted, the evaluation with "generalList" isnt working. At first, I thought I had something wrong in the ini file and took time trying to figure out. Then later discovered the ini file is ok, as the live run actually works, just the dry run with "generalList" fails.


Hopefully, that has descried this clearly.

 

[GoldenFrog]

Okay. I understand. As you say, 'generalList' did not include Conversion or Recruitment as there was no logic: "Run Them Always" was the message. But the algorithm to decide how to prioritize the [QuestPriority] section was the trick. Especially since it changed a few times.

As I mentioned, adding 'Recruitment' or 'Conversion' to the
Type=Recruitment|other|other
list won't work the way you think.

The order of operations is:
1. Conversion (unless turned off by config)
2. Recruitment (unless turned off by config)
3. All others as defined in [QuestPriority]


I will enhance generalList and generalListFast to identify the complete list, however. You're correct it will be much more useful and intuitive that way.

 

[BigDorf]

Great stuff - thanks @GoldenFrog . Will look forward to testing your next update push with this amendments.



While we talk of recruitments, I have observed something today.

There appears to be a quest task of "recovery".
Not sure what it does, it didnt get picked up as wasnt in my list in the ini.




Is this another mission to add agents?

 

[GoldenFrog]

Recovery quests allow you to 'Recover' a wounded, shaken, or whatever agent:


I've only ever run one as a test. I guess if you monitor this 'game' closely, a good agent may be wounded for 24 hours but a Recovery would be done in 12.
Seems silly to me - but... nothing anybody has ever cared to request automation for.

And to be honest, not sure the macro *can* run them as written. If anyone honestly wants them in the loop - we could add logic, should someone provide me the When/Why

 

[Grimm68]

getting this on my zerker

 

[GoldenFrog]

View attachment 23904

getting this on my zerker

That's very bizarre as "_BBList]" or any form isn't in the macro at all.

Can you verify you're on a current version (mostly to make sure any random changes haven't sneaked into your copy?)

 

[Grimm68]

Just updated mq and overseer this morning from the launcher

 

[Robban]

That's very bizarre as "_BBList]" or any form isn't in the macro at all.

Can you verify you're on a current version (mostly to make sure any random changes haven't sneaked into your copy?)

its not the macro, anyone can get that running any macro... Sic explained it somewhere

 

[Robban]

https://www.redguides.com/community/threads/macro-pausing-with-this-debug-message.73819/#post-428974

 

[GoldenFrog]

https://www.redguides.com/community/threads/macro-pausing-with-this-debug-message.73819/#post-428974

Excellent thank you - that actually makes perfect sense. Never run into it myself before.

 

[jtt25c]

This has worked flawlessly for months but now it refuses to accept the missions it just sits there at the yes/no box for accepting the missions. Please help

 

[EvilBarny]

This has worked flawlessly for months but now it refuses to accept the missions it just sits there at the yes/no box for accepting the missions. Please help

i get his every now and then i find logging all the way out of game and back in fixes it

 

[GoldenFrog]

i get his every now and then i find logging all the way out of game and back in fixes it

Sadly this is an issue with core MQ2. I'll try to find and link - but it's an issue with the ConfirmationBox.

As EvilBarny (hee hee) said, there's no choice but to log out/in. It usually either happens once or never per login.

 

[jtt25c]

Thanks you two!!

 

[Redfrog]

@GoldenFrog Had an issue I don't know how to fix, the macro runs great for me with one new issue to me. I have it accepting Overseer currency for most of my characters, but on a few I have spme saved Rewards from other quests that give 12 AA (or anything really), and the macro is accepting those other Rewards in addition to the Overseer ones. I would like it to only accept the overseer rewards if thats possible. I never had it accepting Rewards until just recently, on one 'Main' character I had 8 saved quest rewards that give 10-12 AA and left two Reward slots open to collect anything else as I play. I am awaiting for either TBL to open up or to buy ToV discounted (or the new expansion) to then use up all those AA, since I'm maxed AA on that Gold character. First time I used the accepting Techtradahms it also accepted 6 of the other quest rewards...I was like Ack my saved AA went poof. Is there a way to not touch the other rewards?

 

[GoldenFrog]

@GoldenFrog Had an issue I don't know how to fix, the macro runs great for me with one new issue to me. I have it accepting Overseer currency for most of my characters, but on a few I have spme saved Rewards from other quests that give 12 AA (or anything really), and the macro is accepting those other Rewards in addition to the Overseer ones. I would like it to only accept the overseer rewards if thats possible. I never had it accepting Rewards until just recently, on one 'Main' character I had 8 saved quest rewards that give 10-12 AA and left two Reward slots open to collect anything else as I play. I am awaiting for either TBL to open up or to buy ToV discounted (or the new expansion) to then use up all those AA, since I'm maxed AA on that Gold character. First time I used the accepting Techtradahms it also accepted 6 of the other quest rewards...I was like Ack my saved AA went poof. Is there a way to not touch the other rewards?

First, I apologize greatly. Rewards are the most sensitive part of all this.

The problem here is (blame shifting sucks) MQ2 gives extremely limited access to the Rewards window - and then only the first tab, whatever it is. We can't even look to see what the first tab name is.

If you are banking rewards, the only real choice is to handle the claiming manually. Tell the script to not do it:

[General]
claimRewards=1

For any intrepid plug-in creators, there is an MQ2Rewards plug-in but it needs finishing and polishing. Once that exists, we can do full reward management.

 

[Redfrog]

@GoldenFrog Nothing to apologize for!!! The banked AA is easy to get, least I know I was not doing something wrong.

 

[tegas]

This is amazing work as far as I’m concerned. Wondering if there might be any consideration for the Mac using DB currency to increase production. Most of my accounts build up DB coin without much place to spend it. Apologies if this was addressed previously.

 

[Redfrog]

Hey @GoldenFrog , the macro stopped 3 times on a character that never used Overseer at all yet, was my first time needing to try the Tutorial run part, so I tried it out. I'm sorry I did not write down where exactly it stopped at, but it stopped 3 times and I completed it manually, this is just feedback, not a complaint. Once tutorial was done it ran smooth as always.

 

[Gator]

Hey @GoldenFrog , the macro stopped 3 times on a character that never used Overseer at all yet, was my first time needing to try the Tutorial run part, so I tried it out. I'm sorry I did not write down where exactly it stopped at, but it stopped 3 times and I completed it manually, this is just feedback, not a complaint. Once tutorial was done it ran smooth as always.

It stops due to popup windows needing clicked and also once because a quest needs multiple agents.

 

[GoldenFrog]

It stops due to popup windows needing clicked and also once because a quest needs multiple agents.

Are you agreeing with Redfrog and reporting?

The key problem with Tutorial for me is I never found out how to reset it for an account so unless I keep making free accounts, I wasn't able to re-run or test.

Let me walk my accounts again and make sure I don't have any avail.

 

[BlankStare]

Really should just do the tutorial manually. It doesn't take that long, and only occurs once per account. We're talking like 30-60 seconds here.
The only difference is the final choice of which starter heroes you end up with.

 

[jande]

- - Conversion Quests now sort by the total number of idle duplicates in descending order, then by name.
- Optional quest party slots now display their required job rank.
- Agents who offer no benefit to a quest no longer appear in the Available Agents list in the Quests tab.
- Unavailable agents are now sorted to the end of the Available Agents list.

Going to speed up the macro /cheer

 

[Nadom]

whenever I start overseer.mac my bst and wiz crashes to desktop, no other character does that. it started out of the blue yesterday. i havent changed a thing on any character/ini file. Any ideas?

 

[GoldenFrog]

whenever I start overseer.mac my bst and wiz crashes to desktop, no other character does that. it started out of the blue yesterday. i havent changed a thing on any character/ini file. Any ideas?

That's interesting. My initial thought is there's some unrelated plug-in issue going on.

But do you know if it happens immediately or... near end? The only troubleshooting starting point I have would be to remove all from Sub Main{} and then add them back in pieces to see what happens. But that's a potentially obnoxious time-consumer given the CTD.

MQ2 has logs that get kept too, no? (I'm at work again so have to wait 'til home to do more looking). Hmm.

 

[Nadom]

That's interesting. My initial thought is there's some unrelated plug-in issue going on.

But do you know if it happens immediately or... near end? The only troubleshooting starting point I have would be to remove all from Sub Main{} and then add them back in pieces to see what happens. But that's a potentially obnoxious time-consumer given the CTD.

MQ2 has logs that get kept too, no? (I'm at work again so have to wait 'til home to do more looking). Hmm.

im about to go to bed, so ill look into it after work tomorrow. all i know is that i fire it up and then 2 of my accounts have shut down.

 

[Nadom]

ok, so i started the macro and it chose rewards. Then it crashed to desktop as it was starting to search for a quest. Acording to overseer log it happened when "Ensuring all agents available."

 

[novadude17]

Hello, i'm new to MacroQuest and this specific macro. I've got it running fine on ~20 accounts but it crashes every time I run it on my primary character. I think the catching point is when its starting up and doing the count of all the agents, It crashes on Ambassador D'Vinn , of which I have two.

 

[freeferli]

There is no way to do the conversion on my Duplicate Elite / purple agents is there?

 

[CheshireGat]

There is no way to do the conversion on my Duplicate Elite / purple agents is there?

There isn't a rarity above purple. Retire the extras, which gives you an item to claim, and use the claim to increase the 'experience' of one type (such as Plunder, Harvest, etc).
Can also claim 2 random rare (blue) agents. Helps for filling in missing elite/rare agents

 

[GoldenFrog]

Hello, i'm new to MacroQuest and this specific macro. I've got it running fine on ~20 accounts but it crashes every time I run it on my primary character. I think the catching point is when its starting up and doing the count of all the agents, It crashes on Ambassador D'Vinn , of which I have two.

ok, so i started the macro and it chose rewards. Then it crashed to desktop as it was starting to search for a quest. Acording to overseer log it happened when "Ensuring all agents available."

You're now the second person to say this - and it's apparently fairly rare.

I can't duplicate it on any characters I have."

First question is if you manually can do that step:
* Open Overseer Window
* Click on [Agents] tab
* Let it sit a bit.

Assuming that doesn't crash, you can temporarily stop the "Waiting for agents" by editing the macro and commenting out the agent count as such:

Line 49 change:
/call ValidateMinionStatus

To
| /call ValidateMinionStatus

Or temporarily remove that line.

See if it helps or stops the CTD.

 

[Nadom]

Ill try that, thanks!

 

[Nadom]

it seems to be working! of the 2 accounts that crashes i started the macro on before i saved the changes to the macro, so it crashed, then saved the changes to the macro and started it up on the other account. account number 2 didnt crash´!

 

[novadude17]

You're now the second person to say this - and it's apparently fairly rare.

I can't duplicate it on any characters I have."

First question is if you manually can do that step:
* Open Overseer Window
* Click on [Agents] tab
* Let it sit a bit.

Assuming that doesn't crash, you can temporarily stop the "Waiting for agents" by editing the macro and commenting out the agent count as such:

Line 49 change:
/call ValidateMinionStatus

To
| /call ValidateMinionStatus

Or temporarily remove that line.

See if it helps or stops the CTD.

Temporarily removing the ValidateMinionStatus stopped the macro from crashing the client to desktop.
What I noticed is that it was only crashing the toons that had over 400+ total agents. I'd gotten lazy and let them build up on several, and those were CTD'ing when running it.

Thanks for figuring it out.