MQ2Bot (Old Version - Archived)

flatlined785 · Jan 26, 2016

sigh.

the problem is MQ2bot is trying to cast something and failing. The outcome of that is these silly spam messages. The failure in this case isn't caused by moving in any way. I've provided info saying this many times now.

I just logged on the wiz that this happens with. No lev, no bard, no group, no nothing. Wiz on his own, freshly logged in. Haven't moved, have only hit my bot on button. I leave the whole keyboard alone, and the only thing that has any ability to trigger anything is now mq2bot.

Bot starts up.
Bot self buffs.
Bot stands there doing nothing for a few sec.
MQ2Cast aborting message appears. I posted them before.
a few seconds later, again.
this will carry on until I stop MQ2bot.

Here's the mq2bot debug log output.

Code:

<above this are more can't find mana click items >
[2016/01/26 23:19:41] Mana: Can't find #0 (Summoned: Modulating Rod).
[2016/01/26 23:19:41] Mana: Checking 0 : 'Harvest of Druzzil'
[2016/01/26 23:19:41] Mana: Returning, mana=100>=20 or InCombat=false and UseManaInCombat=true or not valid char info
[2016/01/26 23:19:41] Pet: Checking routine
[2016/01/26 23:19:41] SelfBuffs: Checking routine
[2016/01/26 23:19:41] Med: Checking routine
[2016/01/26 23:19:41] Heals: Checking routine
[2016/01/26 23:19:41] Loot: Checking routine
[2016/01/26 23:19:42] Pet: Checking routine
[2016/01/26 23:19:42] Med: Checking routine
[2016/01/26 23:19:42] Heals: Checking routine
[2016/01/26 23:19:42] Loot: Checking routine
[2016/01/26 23:19:42] Pet: Checking routine
[2016/01/26 23:19:42] Med: Checking routine
[2016/01/26 23:19:42] Heals: Checking routine
[2016/01/26 23:19:42] Loot: Checking routine
[2016/01/26 23:19:43] Pet: Checking routine
[2016/01/26 23:19:43] Med: Checking routine
[2016/01/26 23:19:43] Heals: Checking routine
[2016/01/26 23:19:43] Loot: Checking routine
[2016/01/26 23:19:43] Pet: Checking routine
[2016/01/26 23:19:43] Med: Checking routine
[2016/01/26 23:19:43] Heals: Checking routine
[2016/01/26 23:19:43] Loot: Checking routine
[2016/01/26 23:19:43] Merc: Checking routine
[2016/01/26 23:19:43] Pet: Checking routine
[2016/01/26 23:19:43] Med: Checking routine
[2016/01/26 23:19:43] Heals: Checking routine
[2016/01/26 23:19:43] Loot: Checking routine
[2016/01/26 23:19:44] Pet: Checking routine
[2016/01/26 23:19:44] Med: Checking routine
[2016/01/26 23:19:44] Heals: Checking routine
[2016/01/26 23:19:44] Loot: Checking routine
[2016/01/26 23:19:44] [3786581984348] MQ2Cast:[Casting]: Aborting! (CastM)

that will repeat forever until I stop mq2bot. When I stop it, some routine will time out and MQ2Cast will give a final error message after a while, then it will all stop.

MQ2bot is trying to cast something. It's using MQ2Cast. It is probably passing it something bad, for some reason. MQ2Cast is trying to cast it but never telling us what, and eventually fails the cast - but it doesn't know what it was failing, and (I guess) it defaults this error message.

Is it possible it's being told to cast something, with a long failure timeout, and that thing it is casting is now missing/renumbered/doesn't exist?

It's nothing to do with actually moving, and it's a bit annoying that when I first reported this, I noticed it while I was trying to move around. Actually it was happening all the time, and I only noticed it because it messed up my movement. I don't usually look at this toon screen to see the problem any other way.

I reported it as some bug with moving about, but that isn't the case, a symptom of this is that while the cast tries to happen, moveutils is paused and so I saw a movement delay happening. The cause is a chain, moveutils->mq2cast->mq2bot.

Short of making a video showing this, I don't know what else I can do to demonstrate that it's not player error, it's a problem with what MQ2Bot is doing since the update I reported above. promise 4realzies

I do notice, that my mana bar is still missing, and the only thing I can't do is confirm this is or is not making MQ2Bot do something strange. I can't do this because I can't get the mana bar back, to check the behavior stops or not.

Edit : Except, 3 days ago I posted about this, and noted at the end of the post, the mana bar was there, and when it disappeared, the toon started generating this error. I don't recall that now, and I have not been playing so I haven't been worrying about this problem.

Maybe when whatever causes the mana bar problem is fixed, the bot will no longer trigger this problem. I can't tell if the mana bar problem is due to a daybreak bug, or some side effect of MQ2 / a plugin.

freewilly · Jan 27, 2016

Yeah Pete, I have to kind of go with Flatlined on this one. I don't have any levitate on, no bard in group (in fact I usually run a bard in group but I'm trying to level another non-bard toon now, which is about the only difference in how I do things), I'm doing semi-AFK and do not have MQ2moveutils loaded. I've never had an issue until this most recent EQ/MQ2 patch.

As a side note, I am fully prepared to be embarrassed.

htw · Jan 27, 2016

Looks to me like it's timing out for the default max (which is 20 seconds). Is the bot trying to cast some buff or something else, that takes more than 20 seconds? If that's the case, we need to increase the max allowed cast time. The max should be set to cover pretty much any spell, or it will just abort it after 20 seconds (assuming if there is one or more that is more than that).

Let me know and if so, I can modify and push it (I need to know what cast time we are talking about...)

htw

htw · Jan 27, 2016

BTW, CastM is not for movement, it's a 'mark', i.e. timestamp, for when the cast started. And like I said, the max is 20 seconds, so CastM+20s, timestamp>that, and you get a CastM abort.

htw

freewilly · Jan 27, 2016

For me, I don't see him trying to cast anything. It's basically like mq2bot is not running other than receiving those error messages. He doesn't even target npc's in camp.

I shut my group down last night but will fire them up again after work this evening and get debug results, etc.

flatlined785 · Jan 27, 2016

I had a look at the timings, they seem to be about ~22 seconds between messages. Maybe 20 sec for timeout and a bit to cycle through and handle the fail, and a bit to decide it wants to attempt the cast again.

The bot doesn't tell what it is trying to cast. Increasing this cast timeout will just mean the attempts take longer to time out.

----

I logged in the wiz to do some tests. I noticed that on log in, I had a mana bar. I ran the bot and the mana bar disappeared mid-way through the bot init sequence.
So I relogged, and mana bar is there. Ran the bot, it vanishes again, during init.
Relogged and did not run the bot. Stood there ~5 mins. Mana bar stays there. As soon as I run the bot, the bar disappears. It sometimes happens while init output is flowing up the chat, sometimes after this has all finished, as long as a second.

----

I went back to my first post about this, and grepped my logs to confirm.
In my logs for the wiz, which goes back forever, I have :

Code:

xxx - [2016/01/10 17:13:40] [3785177620526] MQ2Cast:[Casting]: Aborting! (CastM)
xxx - [2016/01/21 09:18:21] [3786099501531] MQ2Cast:[Casting]: Aborting! (CastM)
xxx - [2016/01/21 09:18:47] [3786099527737] MQ2Cast:[Casting]: Aborting! (CastM)
xxx - [2016/01/21 09:21:31] [3786099691538] MQ2Cast:[Casting]: Aborting! (CastM)
**snipped for freedom**

.. that is, one time it happened in the past (dunno why, doesn't matter), and then from the morning of 21st Jan, it happens all the time when bot is running.

and the bot startup version messages, as follows -
[2016/01/20 17:35:31] MQ2Bot (20160115.0113 : 23.8.0.0): did not have this problem
[2016/01/21 07:40:11] MQ2Bot (20160121.0956 : 23.8.1.0): which was the next version pushed for test, did have this problem.

Those version numbers also in the first post I made about this.

htw · Jan 27, 2016

The bot doesn't tell what it is trying to cast. Increasing this cast timeout will just mean the attempts take longer to time out.

Yeah no shit lol... so if you don't see him trying to cast something, then MQ2Bot is trying to cast something that isn't correctly done. I'm sure Pete will take a look at which is causing it, or maybe put some debug messages in any casting call.

htw

PeteSampras · Jan 27, 2016

i added a debug message in for casting that involves mq2cast should be in latest build. it should give one message for spell and target and then another message for spell/gem or spell/alt or spell/item.

if you are casting on a PC, it will have their name. so do a scrub before you post a log. i can probably just change that to type isntead so it only displays pc/npc.

flatlined785 · Jan 27, 2016

version on test build is 20160126.1559 : 23.9.2.0 ... I suspect that is the one Fry pushed at some point recently, but not the one with your extra debugging output, Pete.

htw · Jan 27, 2016

I just pushed his new one to test and live now, so no, it wasn't the very latest.

htw

flatlined785 · Jan 27, 2016

Okay, that lets me see what it is trying to do.

In selfbuff the bot is detecting the various buffs I can have. It detects a couple of self buffs.
When it goes to cast them, one is memd in the default gem (for me,7).
It will cast that buff fine.
Then it wants to cast the next one, and needs to mem it, which it does not do.

[2016/01/27 11:42:32] Attempting to cast TOON on Armor of the Codex Rk. II
[2016/01/27 11:42:32] Attempting to cast Armor of the Codex Rk. II using gem7

... and that is what fails.

I left the bot running and unmem'd that gem. It did not mem the spell.
I mem'd the spell, and it cast it fine.
Since it's then got that buff, it didn't keep trying and spam stopped.

With the buff on, I zoned, so that the mana bar came back. The bot runs, is running, with the buffs already cast so it needs do no rebuffing work, and I have a mana bar.

I removed the buff, with the spell memd. The bot immediately casts it, and before / when the cast started, the mana bar disappeared.

I got the bot to cast some other stuff, mana recovery instead of self buff. it's mana recovery casts did not make the mana bar disappear. As soon as it has to cast the self buff (which it can do correctly now, it's memd), the mana bar disappears.

With the mana bar in place, I removed from my buff list, a different self buff, which I did not have memd. The bot detected I I had lost the buff, and my mana bar disappeared. The bot unmem'd gem7, and memd the spell, and rebuffed me fine.

With the above armor spell now on me but not memd, I removed that buff. The bot detected I had lost it, but failed to mem it, and I get the spam back.

I'm posting all these variations because you can probably fix the mem / spam problem, but something in there is making the mana bar disappear, so I wanted to give you a bunch of scenarios that trigger "the vanishing".

PeteSampras · Jan 27, 2016

lulz @ TOON on SPELL. i will fix that in the debug message.

So ya. if it is not memming that, it would lead me to believe that something in mq2cast is borked. all memming is handled via that plugin. the exact line pushed is:

::sprintf(castLine, "/multiline ; /stopcast ; /stopsong ; /casting \"%s\" %s", castSpell->Name, spellGem);

so it stops anything currently casting and uses mq2cast to mem/cast the other spell. Now i could detect if something is casting and only use /stopcast and /stopsong then, which now that I think about it I will do.. but that doesnt interfere with spells casting.

flatlined785 · Jan 27, 2016

Toon was my cleanse, but yeah the args are in the wrong order to that string format call

It was just debugging and you were in a rush to get something in there.

There's no other cast happening that it might be bothered by - at least, it's not trying and being stopped in some way, and there's no cast I can see happening.

Well - logged in wiz to mess about.
When I have a mana bar showing, I can manually type the /memorize or /casting command, and it will work.
When the mana bar has gone, none of these commands work, they do not mem the spell.
If the spell is mem'd, as above post, the command works if the mana bar is not there. So ... no mana bar means the memorize phase of these 2 commands cannot work.

I can't see what is causing the mana bar to vanish, other than it 100% happens when I run the bot.
I can evac, gets mana bar back, then run bot and mana bar vanishes.

If I have all the buffs the bot wants to have. And I have a mana bar. And the bot is running. And I have the "test" spell memd.
When I remove the test buff, the bot casts it immediately. About half way through the 2-ish second cast, the mana bar disappears.

Now I am back in the "no mana bar" world as above.

So I can loose mana bar by
- having bot recast a mem'd self buff when I have the mana bar.
- having bot try to mem a self buff when I have the mana bar.

Once mana bar is gone, see above notes for behavior.

Trying to do this manually, I can't make the mana bar disappear -
I enter the full line you say the bot uses (multiline stop etc). And at the end put the armor spell info and gem7.
The directly entered command works and casts just fine.
I then unmemd the spell, and re-entered the command. The system mem'd the spell and cast it.

Now my best guess is something in that bot function to do self buffs, or a function it calls to do casting, is writing to some global var, and that var is pointing at incorrect memory. I don't know what in the bot could otherwise make the mana bar vanish. Something corrupting some memory somewhere, yes?

I took the bot to a junk zone, and having the correct buffs so it would not vanish my mana bar, I ran the bot and aggro'd some grey mobs.
The bot nuke routine casts fine and does not remove the mana bar.
The bot cast twincast fine, which is listed as fight buff (and was in a gem already).

Is there a difference between the routines that cast in self buff and in fight buff, other than checking for battle mode etc ? I looked at the debug log and saw the same Toon -> Spell thing, so it's calling the same subroutine. Maybe something that happens before that in self buff and not in fight buff.

/bot UseSelfBuffs=0, disabling the bot from caring, stops the mana bar from vanishing, since those routines don't function. I'm not playing so I can't test if somewhere else it eventually looses the mana bar somehow (ie via proper combat).

Can you pull a copy of the bot source out of source control, and go back to the revision version I mentioned worked okay, and diff that routine against current, see if anything altered?
If you can do that old build against current Test eqmain, I would run that new-old-build and see if the problem definitely would not happen .. I have the old DLL but it doesn't function against current mq2 / offsets, etc.
I am 100% that the problem was introduced to test build in that update I mentioned, but I don't know what other DLLs were updated to "current" for test, at that time ... meaning I don't know if mq2cast or anything else was updated.

htw · Jan 27, 2016

MQ2Cast hasn't changed since November, and that was just a few lines for clickies. Before that, October, when AA stuff changed... etc.

I wonder if it's being seen more due to what the bot may be doing, since hawthorne mentioned it without MQ2.

flatlined785, when you see them disappear, have you tried targeting yourself (hawthorne mentioned), to see if they return or not?

htw

flatlined785 · Jan 27, 2016

I'm really sure this only started happening to me / on test when the set of updates I indicated before, went out.
My play patterns since TDS went free to play have been the same, and I would have noticed the knock-on impact of this on the wiz. I've been running around doing quests, and he only just started not keeping up with the other toons

I logged my wiz back in to check, once mana bar goes, targetting myself, or familiar, or anything else I could target, makes no difference. mana bar stays gone. I have only managed to get it to return by zoning. Any method of zoning resets it.

Other clients continue to see the mana of that toon, and various other MQ2 TLO and so on, all continue to report proper and accurate mana. All the ones I thought to check anyhow. Class seems to still report as Wiz.

It's like the personal window, whatever it's called, like it's pointer to my toon's mana, was overwritten with null, so the UI reacts by hiding my mana bar.
I can't say that's really what is happening, but it appears like that. Why whatever /that/ window has for my mana should matter to all these other things I don't know, I doubt they are referring to that window, more likely the direct memory locations in EQMain structs.

I guess also, at this point, other problems with the bot currently could be caused by this too, since god knows what's happening. I don't use any pet class, so I have no idea if pets were working for me, for example.

hawthorne · Jan 27, 2016

Just a quick thought, you said it only clears for you when zoning... have you tried reloading the UI?

What I saw appeared to be a UI issue of some sort. It happened both in the default UI, and again when I started using the update of the old UI I prefer, Sparxx if that makes a difference. I wasn't seeing it on my toon though, it was on other toons.

Wife and I were pulling in a hot zone, and I was boxing an SK tank, she had a druid and I was running a ranger. I never noticed my own disappear, but rather her mana bar and the SK tank. If I target them in group, either by hotkey or by clicking in the group window, after a second or two their mana bar gauge came back. This occured in both default and Sparxx. This was in a lower level hot zone so not anything in later expansions if that matters. I was not running MQ2.

je5terhead · Jan 27, 2016

having an issue with toons not using mod rods and mage is not casting / using his personal mod rod as well. any ideas?

freewilly · Jan 27, 2016

With regards to the issue both Flatlined and myself have been talking about I just did a debug dump:

Spoiler:

One thing I notice is the line "[2016/01/27 17:18:48] Attempting to cast MYTOONSNAME on Deadskin".

I've changed my toons actual name to "MYTOONSNAME" in this log but it seems odd that it would try to cast MYTOONSNAME on a spell. Maybe that's nothing but seems odd. I didn't notice in my other posts on this issue that the mana bar was disappearing, but it is. I just logged in all my toons, fired up mq2bot on them and the necro makes his pet then stops doing anything and the mana bar disappears. This debug was only run for a very brief time when I first started mq2bot. There had been no combat by anyone in the group during this time.

I'll keep poking around with it to see if I can contribute more.

EDIT: Update, the mana bar is disappearing on all toons that normally have a mana bar. And FYI, before I ran this debug I did download the most current mq2bot.

EDIT: So I did a reboot and all my toons running mq2bot are now working. I still get the, MQ2Cast:[Casting]: Aborting! (CastM), error on my necro but all my casters appear to be working thus far. I know I should have tried rebooting sooner. I have heard/read about issues with memory leaks, maybe that is what I was encountering.

EDIT: After running for about 8 hours without issues the problem has returned.

lugnut · Jan 28, 2016

Mez is broken

Hey guys,

Was grinding away last night mez was working great...pulling in 3 - 4 mobs chanter was taking care of it all. Updated today and BAM...mez no longer seems to be a priority, the chanter has three in camp and is debuffing....

flatlined785 · Jan 28, 2016

I had a few toons on today for about an hour, been busy with other things though.

I checked, and /reloadui does not get my mana bar back.

Also, all my caster toons are able to get this bug, I will guess via the technique relating to buffs and bot init.

MQ2Bot (Old Version - Archived)

Member

Lifetimer

Developer

Developer

Lifetimer

Member

Developer

Your UI is fucking you. Stop using it.

Member

Developer

Member

Your UI is fucking you. Stop using it.

Member

Developer

Member

Celer, Silens, Mortalis

Member

Lifetimer

Member

Member

Similar threads