Search results

Spell.Cast("Freezing Force", ret => Me.Level >= 62 && Me.CurrentTarget.Distance <= 0.5f && !Me.CurrentTarget.HasMyDebuff("Freezing Force")), so this is what we want ? .. hard to do this on a phone :)

OK, I'm on the road now. Please post your code so I can get it in to the SVN and for the next update. If it's working how you want it, then it will work that way for the rest :)

OK but with your logic it's just going to always re-apply. I assume you would want the Me.CurrentTarget.DebuffTimeLeft("Freezing Force") <= 2) We really don't need to have the level logic on spells anymore, that was older code where the bot didn't know how to handle unlearned spells. Give this...

Can you share your code or let me know the name of the debuff that Freezing Force applies? Because it would be as follows then (I think, so hard to test this not having the class): Spell.Cast("Freezing Force", ret => !Me.CurrentTarget.HasMyDebuff("NAMEOFDEBUFF") ||...

Oh sorry that is from the beta build and it has the HK-55 routine added. Because your other files aren't updated it probably had a heart attack looking for the F4 mapping. In any case glad you saw an improvement. I will move it to the stable release but feel free to shoot some additional...

Anyone with a Guard/Vig want to test this out... and compare with current?

also .. does Whirling Blow exist ? (Guardian Vigilance)

Thank you for this, I see a few things that can be tweaked. But take a look here for your spells and your prioritization (dispatch for example). Although it's not in his rotation, if you want to use it I advise adding <=30 health. Either way the routine clearly needs some edits. I'm working on...

and what logic was that? Care to share for the benefit of the rest of the community?

I will check marauder when I get back from vacation but logs help guys. That's why it's there.

Excellent glad you found the issue!

Maybe I misunderstood the wording of your original post but in a nutshell. You no longer have to level manually from 1-9, as in the bot does work now from 1-9 whereas when 5.0 dropped it was unable to. That bug was introduced in 5.0 because SWTOR now allowed you to choose at character creation...

That's right it will use the Basic class abilities until level 10 when the Discipline can be determined. Edit: When the Advanced Class and Discipline can be determined.

Not always necessary but in the case of Shiv it was an issue for Operatives. You can determine that by when you are stuck or seem to be waiting to do the next ability, move closer to your target and pay attention to the next ability. It will most likely be something that was out of range. Post a...

Would need to see a log but most of the time it's due to an ability that the bot is trying to prioritize is out of range and there is no range properly setup in the routine. For example Shiv was improperly setup in the agent recently and was corrected: Spell.Cast("Shiv", ret =>...

You are either using an older version of Default Combat or a different CR. I just tested Sith Inquisitor before and after choosing Deception for an advanced class and in both scenarios the bot worked as intended. Before picking Deception: 2017-07-19 17:02:54,566 [1] INFO MainWindow - Starting...

The bot has issues with transitioning and traveling (loading screens). Some say they have had luck by stopping the bot first then starting it after the screen loads. For me personally I just don't bother starting the bot until after I'm in the Operation or Flashpoint. The same error would occur...

OK I made a Sith Inquisitor as well but I chose Sorcerer / Madness and the bot had no issues. I will test it with a Assassin and see if I can replicate the issue.

12:11:44,705 [INFO] [DefaultCombat] *** Default Combat v75*** 12:11:44,705 [INFO] [DefaultCombat] Level: 3 12:11:44,706 [INFO] [DefaultCombat] Class: Inquisitor 12:11:44,706 [INFO] [DefaultCombat] Advanced Class: None 12:11:44,707 [INFO] [DefaultCombat] Discipline: CanNotBeDetermined...

The pre-combat buffs, post-combat healing, scavenging, harvesting nodes in range, mounting etc is designed only when the bot is in an automated state (with movement or questing). In order to see those applied with Default Combat you would need to use a profile like the 1 I attached (but this...