Cyclone Stucks with Gameobjects

[3.1415]

thanks for your awesome work so far


Bot trys to Cyclon mobs out of range/possibility:

I was able to observe this ones:
-mob and player stand around a table edge(library/other) / very close to a candlestick(library) / other objects(edge/chest/cant walk through thingy)
=> bot is trying to cyclone but cant (doesnt walk around / is blocked)

-player stand at last stages of a stair(docks) and mob is below him
=> in range but cant cyclone

edit:
leap slam = same stuck

Instance Stuck detection is the only possible solution so far

fix it please

 

[pushedx]

Thanks for reporting. We still need to add the "idle" timers as well as a "timeout" timers for various skill usage and interactions. That should hopefully fix some of these issues, but it's not a quick fix, because we have to track bot actions per instance to determine if the bot is actually stuck or not.

Other than this issue, is Cyclone working well skill wise?

 

[3.1415]

re

Thanks for your reply. Yes it works great.

what I like alot:
-start cycloning before getting in range for acutaly hit. => protects him against stun (cant be stunned while cycloning)
-doesnt stop after killing first target and process to the next target in range (just awesome)
-used with cast on crit build => super gatling gun farmer with overpowered damage => insane clean time

things to improve:
-out of sync while cycloning makes him stuck(sometimes) => get reseted and is out of range. around 5sec for reengage
-the stuck issue
-if whirling blades(moving spell) is available in spellpool bot takes whriling blades for 1 solo mob instead of cyclone
I tryed to fix this by deleting NumberOfMobsNear condition in exile.cs but it didn't work => had to remove WBlades => slower cleantime

 

[xujinSWTOR]

Same issue.

 

[njmgaming]

I'm working on a better stuck solution myself, but in the short term, here's a LOL fix for cyclone sticks.

private readonly WaitTimer _stuckCd = new WaitTimer(TimeSpan.FromSeconds(5));
private Composite CreateStuckLogic()
{
	return new PrioritySelector(
		new Decorator(ret => _stuckCd.IsFinished,
			new Action(ret =>
			{
				Log.Debug("Unstucking YO");
				Interop.PostMessage(LokiPoe.ClientWindowHandle, 0x206, (IntPtr)0x1, IntPtr.Zero);
				_stuckCd.Reset();
			}))
		);
}

and put this above RegisterBuffs()

CombatComposite.AddChild(CreateStuckLogic());

The above code simply sends a windows double right click message to the window. You shouldn't get stuck for more than a few seconds.

Modify the timer to your own liking, and of course use at your own risk.

 

[pushedx]

We'll get double click added to the api functions (single click was just added) to make that code a little more pretty soon.

Thanks for letting us know this solves one of the stuck issues. It was added because it's been reported it does, but people just needed a way to do it from the bot itself.

I know I say this a lot, but we'll be re-looking into our code to see why this is even a problem and why this actually fixes this issue.