MMOMinion

Yep forget my post newest version fixed it and line number won't match anymore.

so should we use newest version of easynin? or reposted old one?

(01-04-2016, 09:24 PM)king_S Wrote: [ -> ]so should we use newest version of easynin? or reposted old one?

Use the newest version (3.10) with the latest Skill Manager update.

(01-04-2016, 09:58 PM)sxiong86 Wrote: [ -> ]

(01-04-2016, 09:24 PM)king_S Wrote: [ -> ]so should we use newest version of easynin? or reposted old one?

Use the newest version (3.10) with the latest Skill Manager update.

thanks

Running newest version, with skill queuing off and Ive noticed a frequent thing happening whenever I enable the bot with Huton in OoC active: Before it uses any mudras it will immediately use Invigorate before it does so, even at full TP before combat even starts.

(01-09-2016, 01:43 AM)Shotaro1 Wrote: [ -> ]Running newest version, with skill queuing off and Ive noticed a frequent thing happening whenever I enable the bot with Huton in OoC active: Before it uses any mudras it will immediately use Invigorate before it does so, even at full TP before combat even starts.

I can't reproduce the problem.

Are you using hotkeys to start the bot? Is your hotkey to start the bot the same hotkey for invigorate?

(01-09-2016, 05:54 AM)hxx112 Wrote: [ -> ]

(01-09-2016, 01:43 AM)Shotaro1 Wrote: [ -> ]Running newest version, with skill queuing off and Ive noticed a frequent thing happening whenever I enable the bot with Huton in OoC active: Before it uses any mudras it will immediately use Invigorate before it does so, even at full TP before combat even starts.

I can't reproduce the problem.

Are you using hotkeys to start the bot? Is your hotkey to start the bot the same hotkey for invigorate?

I can't reproduce the problem either and have been using this over the last couple days w/o issue.

Thanks for making this profile! +rep

Yeah, after investigating and resetting bindings it seemed to be a problem with that. Invigorate was bound to the same key, with that aside the profile still works amazing. Barely any bunny's at all, even without optimal settings.

I found a bug. On enemies with no facing (i.e. so rear + flank both always apply) the profile will use Armor Crush instead of Aeolian Edge when Huton > 40s and Dancing Edge / Storm's Eye is up

(01-13-2016, 03:58 AM)tjalex Wrote: [ -> ]I found a bug. On enemies with no facing (i.e. so rear + flank both always apply) the profile will use Armor Crush instead of Aeolian Edge when Huton > 40s and Dancing Edge / Storm's Eye is up

Just put in something like Huton < 50s on Armor Crush that way it will only do it when it can make use of the added time.