I've found that any macros I made before, with /wait lines, the wait no longer works properly. I had to convert them all to <wait> to get them working again.
Printable View
I've found that any macros I made before, with /wait lines, the wait no longer works properly. I had to convert them all to <wait> to get them working again.
Well - it's was clearly mentioned in the patch notes that new <wait.n> (sub-)command doesnt support decimals - it also needs to have dot between wait and n number (0 -30 only) so whatever string you'd squeeze in after the fist digit or 2 would be at best case ignored (the "trimming") or at worst produce the error.
it certainly would be nice to have decimal support in our wait timers for macros again. it doesn't make much sense to me as of to why they removed it. especially with the default global cooldown set to 2.5seconds. it really doesn't make sense. other then performance related issues, there is no logic to the change.
Well - the "explanation" from SE's top brass was that they don't want to make macros too "precise" to put players who don't (want to / know how to) use them to dissadvantage, to be pressurised to used them or being abused by others for not using them ... which is IMO pretty LAME "excuse". This "PC" approach is simply wrong and results in nothing else than people using 3rd party precise scripting / macroing tools instead of the ones built-in directy in the game. It's lame at the same level as if they'd remove the chain combos with the claim it's to "difficult" and put those who're unable to (properly) use them to dissadvantage. SE - plase STOP baybisinting all the players and putting in silly limitations like this! ;(