Thread Rating:
  • 25 Vote(s) - 3.52 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[BETA] SkillManager & Combat API Update [IMPORTANT]
#31
Updated again. I think I found a way to protect against the inherent sucktitude of mudra lag. Parsed about 15 minutes worth without a single screw-up.
Additions: "Previous GCD Skill", works in the same manner as the old "Previous Combo Skill".
Reply
#32
Is it possible to developpe more details for the subfile Target :

Target role :
All Jobs DRG/BRD/SMN.... or DPS Physical nearly Ennemy / DPS Distance / ....

exemply Goad when you comand target<500 pt cast partyS target role dps

but if BLM cast speed run skill, minion cast the spell on the blm.... and your skill are on cd for nothing...
Reply
#33
Request:

Option/Condition to use Action while moving in combination with SwiftCast.

Example:
  • Stoneskin (whm) cannot be used while player is moving. In combination with Swiftcast the Stoneskin can be cast while moving, but the bot doesn't support it yet
  • Flare (BLM) cannot be used while moving, but in combination with Swiftcast.
  • etc...

This is useful in assist mode and profiles with built in swiftcast in the rotation.
Reply
#34
@balgarion, most of the targets already pre-filter inappropriate targets, in your example, Low TP will never choose a BLM to cast on, just as Low MP will never choose a WAR. In addition, the Target Role will also apply itself to some targeting selection routines.

@bizzmo, do you think it needs to be an option, or can I just nix the moving check altogether if the Swiftcast buff is applied.
Reply
#35
IsMoving needs to be an option, it's not just for swiftcast. It's needed for many other caster jobs too.
Reply
#36
@speedtech, like what? Swiftcast is the only ability that removes cast time as far as I know.
Reply
#37
Prioritize use of scathe , ruin2, feint, firestarter, thunder proc, straighter shot, slug shot proc, clean shot proc on moving.
Reply
#38
(07-13-2015, 12:36 PM)Ace Wrote:  @balgarion, most of the targets already pre-filter inappropriate targets, in your example, Low TP will never choose a BLM to cast on, just as Low MP will never choose a WAR. In addition, the Target Role will also apply itself to some targeting selection routines.

but i said that's because build configurations forAstro cards on each dps its difficult without target role details...
like if you want cast something on pld and other thing on war or drk you cant select between all tanks.
and if you want cast something on physical dps like mnk or nin, an another spell on bard, you cant select between all dps too.

How Minion can recognize jobs differences ?
Reply
#39
(07-13-2015, 12:36 PM)Ace Wrote:  @bizzmo, do you think it needs to be an option, or can I just nix the moving check altogether if the Swiftcast buff is applied.

Nix works I think.

It gives us the opportunity to use action while simultaneously moving in combination with swiftcast that was not possible before.
Reply
#40
(07-13-2015, 01:12 PM)balgarion Wrote:  
(07-13-2015, 12:36 PM)Ace Wrote:  @balgarion, most of the targets already pre-filter inappropriate targets, in your example, Low TP will never choose a BLM to cast on, just as Low MP will never choose a WAR. In addition, the Target Role will also apply itself to some targeting selection routines.

but i said that's because build configurations forAstro cards on each dps its difficult without target role details...
like if you want cast something on pld and other thing on war or drk you cant select between all tanks.
and if you want cast something on physical dps like mnk or nin, an another spell on bard, you cant select between all dps too.

How Minion can recognize jobs differences ?
Role = tank healer melee dps or range dps.
Job = class warrior pali etc

[Image: 9fec746449.jpg]
Reply
 


Forum Jump:


Users browsing this thread: 2 Guest(s)

We help you win the game.

FFXIV Bot and More.

 

Products