Runes of Magic US / AU

U can post here if u like

.frafall

Releasing version 0.52, major changes:

• Handle all cooldown calculations within FD, including some synchronization in case of external skills
  
• Added tagging of non-gcd skill, also have auto detection but this will taker place during 1st GCD.
  
• Update configuration panel to have tuning parameters for cooldown calculations
  

.frafall

Global Cooldown (GCD)
As global cooldown is handled within FD we need a method of detecting which skills do NOT trigger GCD. This is
done in the trySkill statement as fifth argument:

FD will also auto-detect GCD skills BUT this is only detected during a GCD period, i.e. for optimal performance
tag them manually.

Cooldown Adjustment
FD handles skill cooldown internally, i.e. for a skill with 5s cooldown it times 5s from the time you hit the
macro. Normally the client uses 5s from the time the server responds, approximately 0.1-0.34s after u hit
a skill. So, the cooldown shown on an actionbutton for a 5s skill is typically 5.1-5.35s. To make up for this (I assume)
the server accepts when a skill is hit approximately 0.3s before cooldown is finished. Combat engines like
FD/DIYCE has been relying on the GetSkillCooldown client call to figure out when a skill can be used which has
resulted in lower dps even though we have tried to compensate for this by subtracting 0.3s from the value.

Since FD now handles all cooldown tracking internally there is little need for adjusting but to optimize the
dps I have added the "Cooldown Adjustment" slider, this value will be added to the cooldown of each skill
and GCD, so with a value of -0.1 the real cooldown of a 5s skill will be 4.9s. Note: if you put this at a to low
value skill will fail and you will notice a significant dps drop, I typically have this at -0.15 to -0.20s.

Event timeout
The client will not accept a new skill used before it has received an answer from server of the previous,
this is visible in addons by the COMBATMETER_DAMAGE event which occurs approx 0.1-0.35s after a skill
is used. So, FD listenes for this event and blocks until it is received.

But, during testing I have found to miss a few of these events and even one miss froze FD. So, I have
added a timeout on the events, after this it tags skill event as received. This slider adjusts the time to
wait for an event. I typically use 0.3s.

Manual timeout
When all cooldown calculations is done FD will try to verify its perceived cooldown with the 'real'
cooldown from client. If the client claims remaining cooldown is larger than the 'Manual timeout'
value FD will assume a cooldown is running. This will handle cooldowns on manually pressed skills.
Note that the value of this slider can be viewed as the delta time before cooldown finishes in which
server accepts skill to be used. I use approx 0.3s.

Releasing version 0.53, major changes:

• Bug fix in 'trySkill', this bug incorrectly evaluated skills to be used whenever a 'nil' value was give which
  actually happens from quite a lot of the client functions (true, nil). NOTE: as a result you must ALWAYS give
  at least two arguments to the trySkill(skillName, when), i.e. 'when' does NOT default to true anymore.
  
• To support non-english clients I have modified the Attack plugin to ALWAYS use english class names on
  calling the combat script. I.E. to use the Attack plugin the attack function will be named ex. RogueMage,
  not the local language equivalent. (ref a Polish issue reported)
  
• I have moved all texts in the configuration interface to a language file (locale/default/messages) to
  support translations. Any translations can be located in separate directories ex. locale/de/messages for German.
  

.frafall

Releasing version 0.54, major changes:

• Checking the cooldown of a skill at attack time to facilitate time based skills like 'Shot'
  
• Corrected bug in the PlayerMana function which failed for all mana based classes like m/p, m/wd.
  

.frafall