#0 - Feb. 9, 2007, 5:49 p.m.
It isn't rocket science. Trinket macros should be a major part of the game, and before blizzard decided to outlaw /script's while in combat I had some wonderful macros that actually did it properly, without generating error messages. Making people hit their trinkets manually is just ridiculous.
Here's the basic problem. As it stands now there are only two ways to make trinkets sorta work. First:
/cast MyTrinketHere
/stopcasting
/cast MySpell
Second:
/castsequence reset=COOLDOWN MyTrinketHere,Attack,Attack,Attack,Attack,Attack,...
/stopcasting
/cast MySpell
There are severe problems with both methods.
First, if the trinket is not available the UI spews error messages or, even worse, for some trinkets it spews weird cut-off sounds!.
Second, there is no way to tell /stopcasting to ONLY act on the trinket spell, so if you spam a macro key it will interrupt any spell casting you already have active (such as a shadow bolt). Spamming macro keys is an absolute requirement in PvP. It is absurd for /stopcasting to act on your previously cast spells, it makes macroing spells like Shadow Bolt very difficult.
Third, there is no way to tell /castsequence *NOT* to reset, and no way to tell it NOT to cast a spell.
This is what I want, and for gods sakes please implement it!!!!!!!
/cast [cooldown:MyTrinketName] MyTrinketName
/stopcasting [currentspell=MyTrinketName]
/cast MySpell
That's it. That's all I want. I don't want it to try to equip the trinket. I want the /stopcasting nonsense built-it to it (and frankly, ANY instant-cast that doesn't have a global cooldown), or at worst allow us to conditionalize the /stopcasting as shown above. And then I want it to cast my spell.
It's so simple, I just don't understand what the problem is here. And, really, I am sick and tired of my macros making weird sounds and generating error messages.
-Burns