I noticed the same thing for quite a few items. If I had to guess, timer data was set two different ways over a widespread amount of clickies. For one group of clickies you have them:
Successfully greying out and correctly reporting their remaining recast time to the (Underfoot) client. These items include all epic 1.5/2.0s, Tier 8 bps, and a select few donor weapons & random items.
The other group of items does not grey out, does not report the remaining cast time, and will simply report to the client that it's always ready but if you attempt to click and it's not truly ready it will yield a timer not met message.
Gameplay is fine, they all work great, so Conradd I can only recommend that you use /echo ${FindItem[Valtron's Necklace of Wonder].Timer} for the items that report their timer correctly and set up manual timers for the rest. An example of a manual timer, for those that don't know, would be:
Code: Select all
|---Declare the timer---------
/declare DonorWeaponTimer timer outer 0
|---Usage Scenario would be--
/if (${Defined[DonorWeapon]} && ${DonorWeaponTimer}==0) /dosomething
|---After a successful cast you can restart the timer with something like
/echo Clicking ${DonorWeapon}
/call cast ${DonorWeapon} item
/if (!${Macro.Return.Equal[CAST_INTERRUPTED]}) {
/varset DonorWeaponTimer 81
}
|-Timers are in deciseconds for those new to mq2 timers-|