Filir's Moonlight skill will not work if flitting is set to true.

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Having Moonlight and Flitting active
2.
3.

What is the expected outcome? What do you see instead?
Expected: Using moonlight with flitting active to increase atk.  Instead:
Homunc will only attack normal without skills until Flitting wears off.

What type of homunculus/mercenary are you using?
Filir

Original issue reported on code.google.com by bah...@gmail.com on 11 May 2010 at 2:48

[GoogleCodeExporter]

Flitting has an after-cast delay of at least 60 seconds, according to 
http://irowiki.org/wiki/Flitting . Because of this, Rampage AI Lite will not 
use other 
skills until this cast delay wears off.

When I get a chance, I'll verify that this data is correct. If you find that 
flitting's 
cast delay is indeed shorter than this, please let me know.

Original comment by faithful...@gmail.com on 11 May 2010 at 4:10

• Changed state: Pending

[GoogleCodeExporter]

I've noticed that if I deactivate the skill in rail, and manually use the 
Flitting 
skill, moonlight still casts as normal.  I think the cast delay on the Wiki is 
to 
use the same skill again.  Is it possible to remove the delay in the 
programming as 
a test?

Original comment by bah...@gmail.com on 11 May 2010 at 6:10

[GoogleCodeExporter]

In the skills file I changed the cast delay function to = 0 and it now operates
correctly.  It will cast flitting and then still use moonlight immediately.  
Now I'm
wondering how to only cast moonlight if there is enough sp for flitting.

Original comment by bah...@gmail.com on 12 May 2010 at 12:56

[GoogleCodeExporter]

In the skills file I changed the sp requirement for moonlight to 70 + level*4 
instead
of 4 * level to always save 70 sp for flitting but this doesn't really do what 
I need
it to since flitting usually dies before there is enough sp to moonlight very 
much. 
Would this have anything to do with the buffpriority function?  Maybe that 
would work
better.

Original comment by bah...@gmail.com on 12 May 2010 at 1:04

[GoogleCodeExporter]

I've updated flitting in revision 168. For the sake of simplicity, RAIL now 
believes 
that the buff wears off when it is able to cast again--even though the buff may 
wear 
off earlier.

As for the SP usage, look at the BuffBasePriority and PriorityOffset options in 
the 
state-file. For offensive spells, the priority is based on that of the target 
monster. Since buffs don't have a target monster, the BuffBasePriority is used. 
From 
this, PriorityOffset modifies that value and then the highest result is 
selected.

If RAIL does not have enough SP to cast the highest priority skill, it will 
prevent 
other skills from being cast automatically. So, in order to automatically 
reserve SP 
for flitting, just set either the BuffBasePriority or Flitting's PriorityOffset 
to a 
number higher than any of your ActorOptions "Priority".

(If you have more trouble with SP usage, please create a new issue. SP usage is 
outside the scope of this issue.)

Original comment by faithful...@gmail.com on 12 May 2010 at 2:07

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by faithful...@gmail.com on 12 May 2010 at 2:24

• Changed state: Verified