Hey I’m a software engineer with a backround in Bioinformatics and Applied Mathematics. I’ve also created addons for World of Warcraft in the past (for personal use). I would really like to assist you on this and help solve some difficult problems you might be facing because I’m quite adept in the Lua programming language and simply love the idea. Also I’m counting down the days Classic goes live lol. Please get in contact with me if you’re interested.
1 Like
Thank you Dejablue
1 Like
CTMod?? ![:heart_eyes:](https://d38bqls1q93fod.cloudfront.net/en/wow/images/emoji/twitter/heart_eyes.png?v=6" ":heart_eyes:")
Not, cool.
Ask Tekkub first.
I meant no disrespect. Do the addons that Durrus is porting just not have authors anymore?
A lot of the addons we loved from Classic’s authors have moved on. For example, Pally Power. . Still no solid word on someone picking up the mantle on that one.
The good news is that the list of working addons on the wowinterface list and our list at Will it Classic is growing. (many of our list points to them as we are just a community driven aggregate and not a distribution hub like the great folks at wowinterface.)
Remember to support all our addon authors. These awesome folks are developing these addons out of a passion and love and often spend more time working on them than playing the game they love.
as far as i’m concerned any non ui skin addon, i will never support, addons kills wow, handicap all the skill required for encounters no game aside from wow has 3rd party programs saying what is going to happen
1 Like
I know we are getting these addons and they were, in part, part of vanilla, but this sucks.
Someone please port the “RangeColor” addon to Classic. It’s a simple addon that changes the color of the entire spell icon instead of only the keybind text.
Red: out of range
Blue: out of mana
Green: ineligible target
Love youuuuu
Clique does not seem to be working properly.
It is not distinguishing the difference in spell ranks.
Ex: I have Healing Wave Rank 1-4. If I bind ranks 2, 3, and 4 to mouse clicks, no matter which one I choose to use it always defaults to the highest rank.
It was easy to track by watching the mana consumption.
I hope this message finds the folks working on porting it over. Thanks.
1 Like
Clique by default isn’t currently doing spell ranks, but if you want to bind spells other than the max rank simply click on the bind other, macro thing and bind it as a macro. I’m doing that in beta and it works fine. As a macro you could do something like:
/cast Healing Wave(Rank 1)
or
/cast [@mouseover,exists,help] Healing Wave(Rank 1)
By default this will only use the key when you mouseover over a frame, regardless of the @mouseover in the macro, just like if you just default bound the Rank 1 spell, but you can then set other options like global or hovercast. Global will treat it like a normal keybind and not pay any attention to enemy/friend or other conditions (except ones set in the macro if you’re binding a macro). Hovercast will treat it as a normal @mouseover macro (meaning it will use the keybind over a character model as well as a unit frame).
If you wanted the key to be a mouseover macro unless you had no target and heal you instead, you’d do something like:
/cast [@mouseover,exists,help][@player] Healing Wave(Rank 1)
/cast [@mouseover,exists,help][] Healing Wave(Rank 1)
the second one is effectively the same thing if you have auto self-cast turned on
and set the keybind to global since you’d want it to use that keybind regardless of where your cursor was or what you were targeting (it would then also effectively be a hovercast keybind also, but you wouldn’t set it that way since you want it to heal yourself if you’re not targeting anything).
I think you could also have two separate keybinds to the same key in clique to get it to only do frames by default and then heal yourself with no target, but I’m not in the game to test it. I think you’d basically bind the same macro twice except one with [@player]. The normal one you’d have as default in clique and the [@player] one you’d turn off default and turn on global. You’d only do that if you only wanted it to mouseover heal when over a unit frame and not over someone’s character model, but also heal yourself if you had no mouseover unit frame target.
TLDR: If you want to bind a specific rank and ignore all the potential complexity of clique options on top of macro conditionals, just bind a macro (a in-clique macro, not a /m macro on the actionbar) to whatever key you want and make the macro:
/cast SpellName(Rank #) IE
/cast Healing Wave(Rank 1)
i had a love/hate relationship with this addon. i’m curious if blizz will let players use it when the game launches
612 posts…did anyone say Decursive yet?
I dont want to use a add on for the auction house… am I really going to be forced to download one because others are using an addon that makes the buying and selling of items easier and i’m at a disadvantage otherwise… so sad what the WoW interface folder has turned into… from simple aesthetic UI changes to game breaking mandatory add ons… I hate add-ons… I really do
Yes, they have.
2 Likes
That is what I did. I am using mouseovers for now.
When you say by default, do you mean clique has never been able to recognize spell ranks? I am almost positive it used to have that function in the past.
With all the totems I have I am running out of keybinds. That is why I was trying to move my decurses and healing spells to my mouse.
But…but… #NoChanges. Decursive needs to work, or it isn’t really Vanilla.
I’m a big fan of TellMeWhen, would be amazing to have it in Classic
I understand your concern. Without Decursive, certain encounters in Vanilla raids might seem to some to be of Herculean difficulty by comparison. That is until people learn to adapt; which they will. And yes, it will still be “harder than intended” because later Vanilla raid encounters were designed with the existence of Decursive in mind. But, if I were Blizzard, I would still leave that as it is. With all of the (very valid) criticism about that Vanilla content will be too easy because it’s too well-known and add-on authors have only gotten better, it is not altogether unwise to leave something alone that is tipping the scales in the other direction.
Also, as we move forward in this beta, keep in mind that #nochanges is not to be taken literally. It is a concept, and thus, can only be properly understood in a specific context. No one (that has thought carefully enough) is suggesting that Blizzard simply re-release the 1.12 client and spin up some 1.12 servers. Why not? Because, over the years we have gotten…
- a 64-bit client supporting the AMD64 instruction set and more than 4 GB of RAM
- countless bug fixes in the network and rendering code
- support for widescreen with AMD GPUs
- DirectX 11 and 12 on Windows
- more than 16 audio channels
- major steps forward in the LUA interpretter
- BNet and launcher integration
- the ability to play before the game is fully downloaded
- lots of other technical but valuable, non-design-impacting stuff
What we want #nochanges in is how it feels to play the game. To apply that specifically to the Decursive issue, #nochanges will be violated either way (it’s allowed vs. it is blocked). And, believe it or not, #nochanges would be violated in a far worse way if they allowed Decursive to exist in Classic.
Just because so many things were possible in Vanilla’s more open add-on API surface doesn’t mean that the community had advanced enough in our ability to develop add-ons that we were capable of exploiting it in truly game-breaking ways. Blizzard narrowly averted that potential crisis with the Burning Crusade pre-patch. But, if they allowed add-ons to use abilities in combat in Classic today, the kinds of add-ons you would see would be so much more advanced than Decursive. Think for just a moment about what we, collectively, might be capable of with the knowledge we have now. Would the software development arms race that resulted resemble anything like what you remember from 2006?
#nochanges does not mean that nothing can or should change. Time has advanced for thirteen years. The player base and meta have evolved. Add-on development has matured. Blizzard cannot stuff all these cats back in their bags. What #nochanges means is that given what we have to work with, we’re going to do our damnedest to get the feeling we had playing the game we fell in love with.
1 Like
Need Omen Threat Meter or something similar. Especially in Vanilla WoW when threat gauge was important