|
|
metadata
I have all of the auto skills unlocked. 5 of attack, and 5 of support.
When I start my run I have to go some time with using just a few combat skills, while I focus on my build.
With most of my skills being locked.. the auto skills seems to always pick the locked ones. So I upgrade auto skills to go faster, but it could take several cycles to land on one of the skills I actually have.
I wish I had never purchased the support upgrades and just let it cycle through the attacks.
My suggestion is to either let us pick which skills are going to be used, or only auto pick skills that are unlocked in the tech tree.
thanks
|
|
|
metadata
> *Originally posted by **[Associated1992](/forums/1023269/topics/1763037?page=1#12899377)**:*
> I have all of the auto skills unlocked. 5 of attack, and 5 of support.
>
> When I start my run I have to go some time with using just a few combat skills, while I focus on my build.
> With most of my skills being locked.. the auto skills seems to always pick the locked ones. So I upgrade auto skills to go faster, but it could take several cycles to land on one of the skills I actually have.
>
> I wish I had never purchased the support upgrades and just let it cycle through the attacks.
>
> My suggestion is to either let us pick which skills are going to be used, or only auto pick skills that are unlocked in the tech tree.
> thanks
Auto-cast is definitely on my radar -- I plan on having the player select which skills to AutoCast, and to fix it sometimes not casting
|
|
|
metadata
> *Originally posted by **[lavaflame2](/forums/1023269/topics/1763037?page=1#12899494)**:*
> Auto-cast is definitely on my radar -- I plan on having the player select which skills to AutoCast, and to fix it sometimes not casting
If at all possible, player customizable conditional auto casting with skill priorization would be a killer feature. For example:
* if HP is below 50%, prioritize Heal
* if Meteor, Flurry or Smite is active, don't cast Meteor, Flurry or Smite
* etc...
The functionality would be pretty simple to implement in source code, but I've no idea how to actually make it usable especially on a mobile platform.
|
 "Associated1992"){kind=small}
 "lavaflame2"){kind=small}
 "tserhey"){kind=small}