SolarStrike Software

After running my bot for a time (hours/overnight often) MM starts getting a bunch of failed to cast and aborted messages, my character dies, I accrue horrible debt. Is there a way to sound an alarm or terminate the client like with the processmonitor (love that) when it gets x-amount of failed to cast or aborted in succession?

Maybe your character is running out of mana which can cause a fail to cast message?

It's a scout, but it will happen on any class. My guess is MM loses track of the cooldowns and can't cast because it thinks everything is on cooldown even when it isn't. It's probably a "memory fatigue" issue corrupting the bot. I doubt anything except a reload will fix it. I'm just hoping to find a way to detect it and kill the client b4 mobs eat me while I'm having my seizure.

Is the client still up and running when you get back to it? Are you using the normal bot attack process or have you customized anything such as the unstick functions?

I usually find my guy facedown and the last attack incomplete in MM window. I use normal attack functions. Nothing special except catch cavy and use goody

It's hard to come up with a solution that will work unless we know what is going on. I suspect this is one of those times when we are not going to be able to figure out what is happening because it happens when you are away from the computer.

There is no facility for doing something if it fails to cast a certain number of times but I thought it triggers an unstick event if it fails to cast too many times. Are you seeing unstick events on the console? If so you could use the unstick functions Lisa set up a while ago. Just create an unStick3(), unStick6() or unStick9() function somewhere, such as the waypoint onload, and it will be run on the 3rd, 6th or 9th unstick respectively.

Let me see, what else? Maybe you are putting yourself into a situation where you get attacked my multiple mobs that are obstructed by obstacles and it is somehow getting stuck alternating between these mobs. When you find him face down, are there obstructions around it? Does it usually happen in the same place? Does it happen with different waypoint files in other locations?

There are no obstacles. It just happened, but it started a couple minutes later while I was fiddling with the screenshot. Note in the screenshot it fails to complete the attack. I just sat down and my guy was standing there doing nothing. Luckily there are NPCs to kill the mobs or he woulda died. It did seem to self-correct given time. I'll check out the unstick function and see if that might be useful, but it happens in various locations in different zones.

In that screenshot it looks like the mobs are dying. The fact that it says "aborted" may just be a mistake in what it prints. I've noticed lately that I get aborted messages like that but it is actually using the skills and working properly. Although a side affect of this is, because it says aborted, it thinks the skill wasn't used and then tries to use the skill again even though it's on cooldown. It doesn't seem to happen all the time so it's hard to bug fix. Restarting the script often fixes it. That said, the failed to cast messages might be a separate issue. It would help to see a screen shot of the console when it has the issue that causes it to die.

Yeah that one wasn't exactly like the ones that cause me to die. Those were a string of failed casts. The aborts are certainly because the mob dies. I notice it all the time when the bot kills something but it doesnt die before he start the next attack/spell. If I die I'll get a screenie of the failed casts

Which rombot version you use 883Dman ?

3.29

here's a screenie of one just happening. Lucky i saw him beating on a bird with his stick b4 he died/

I don't mean the that I mean the reversion number of your bot.(lua script)

MM 1.03 Rombot: 3.29

I just realized there are 2 different things happening. 1: The bot fails to acquire a new target and rombot hangs mid-cast. I think there is an example in my first screenie where you see the last command doesn't complete. Bot just stands there. If I tab to a new target it will run over and auto attack but fail to use skills. 2. is the recent screenshot where it starts to just fail to cast. I think there is a correlation with lag. I had bad lag at the time. I think maybe the lag through the program's recognition of the the cooldowns off. Not sure. It's interesting.

I think lag is the top likely cause for theses issues. What made you suspect lag? Was the game stuttering? If so, was it also stuttering when running between waypoints between fights?

I was having a hell of a time in siege on my scout. (getting the pew pew sound without the actual action). character "locking up" and having to swap gear to move again, other player complaining of my lag porting in siege. Obviously the character in question wasn't in siege but it did occur (this time) immediately before it started. I noticed this zone is bad for lagging out over time as well. (Sarlo).

I was getting *aborted* alot in my KS runs recently on a private server, I was having ping issues so I just put it down to lag as opposed to anything else.

That may be the case with 883Dman, or not, I don't know. The reason I asked those questions is because when I was getting some aborts I had low fps which indicates a problem local to the PC. I don't believe lag can cause low fps.

So if 883Dman is getting lag with big pings then there really isn't anything we can do. But if he is getting stuttering with low fps then something is happening locally. We might be able to address that.

Did anyone ever figure this out "Failed to cast" It started happening. it seems to be happening most of the time. I tried micromacro 104 105 and rom bot few versions. bot seems to work otherwise. it just will not attack.

I tried using default profile just changed the autoelete factor and mob levels. I kept waiting to see if anyone else posted a problem.

similar problem here, my bot get stuck sometimes after killing a mob and everytime it happens the last attack was incomplete in MM window

I found this in the lantuage.lua I am trying to figure were the 82 points to must be a table or something, need to find the code generating the error.
[82] = "=> * aborted *\n",