Authors CurseForge

Grumph ... after one hour in lua, and testing all i could, i think the problem could come from the "bestrank function"
Because all "things" that work dont seem to use this function

In CliqueUtils.lua I modified

if castrank then
		self:LevelDebug(1, "Trying to cast: %s(%s %d)", name, RANK, castrank)

So i have a feedback on what is tried to be cast.

I try to cast Motw if no Motw on target (me)
first version: done with spellbook, mark rank 1 to 7, spell is corectly cast
Second version: i push the "max" button, i got "Trying to cast: Marque du fauve(Grade 7)", but nothing is cast
Third version: Clique:CastSpell("Marque du fauve") ok, but no best rank selection
Fourth: Clique:NewSpell("Marque du fauve", "Marque du fauve")
Here it become strange, really ... if i dont have the buff, then i got the "trying to cast" debug message but with the correct rank, but no spell is cast; if i still have the buff, then nothing happen, that is what inteded to be.

So, i know i'm not stupid, but i know i'm really not a programer, but ... i really dont know what happen.
I hope this can come from the "rank" problem with Fr localization, but as Oxman seem to work on it, i will just wait ^^

Clique:SetDebugLevel(3) will give you tons of debug information

Ok i think that comes from the fr problem with "rank" localization.

In localization.fr i can see RANK = "Rang",
So i thought it should be correct, but when i click-cast a spell, debug message show that SPELL (Grade X) is tried to be cast, not SPELL (Rang X) that should be correct.

As i just DL English client, i now try on it, just to know if all my problems come from this.
Thank you for your help, but i think i wont be able to do more :/

Well, I seem to have broke Clique with CTRA. I was using an older version just fine. Before logging in tonight I saw a version on WowInterface, so I loaded it up. Upon login, I noticed I had to recofigure my buttons. So I go through that and test them on myself (I use oUF). Then I jumped in to a raid and noticed that none of the click calls worked when clicking on a CTRA frame. All it did was target whoever I clicked on.

I went through the what few things I could think to try (deleted both Clique and CTRA and loaded new versions, CTRA from WOWInterface and actually SVNed Clique from Trunk). Still no go. :-( I am sure it is some mod or something I am doing, but it has me baffled since it was working til I upgraded to a newer version.

Any ideas?

Lots changed in the new version, but the CTRA plugin should be working.. I'll try and take a look in a moment, but I'm not sure I'll get in game.

On line 22, uncomment the following

--Clique:SetDebugLevel(1)


Make it

Clique:SetDebugLevel(1)

Does it say the CTRA plugin loads?

Oh yeah, meant to mention that. It does say the module "ctra" has loaded for CT_RaidAssist.

Everything looks to load as normal, from what I was used to seeing. Like I said, I am hoping it is a mod or something I have doing it, but at the moment I am stumped. And I am definitely a lua noob.

Ok.. just give me a few. have to finish something up then i'll try to hop in and check

Using the latest CTRaidAssist and Svn/WoWI Clique, I have no problem click casting on my raid. You may want to enable Clique:SetDebugLevel(3) and see what that gets you.

Well, phooey. I wonder what I have done.. I set the debug level to 3, but am not getting any information back when I try to click on a CTRA frame. Plenty of information from my oUF frame clicks though. Should it be returning something for the CTRA clicks if all it is doing is selecting as a target whichever frame I click on?

Ok, edit - Seems I have tracked down the problem on my end.. CTRA functionality breaks if I have Ace 1.3.0 loading.. If I disable that, I get Clique and CTRA to play nice, but of course, all my Ace 1.3.0 mods break.

Ok, I found the problem.. Helps if I read through all my mods. I still for some reason had an old version of AceHeal loading that was breaking everything. I'm a noob. :-(

Thanks so much for the help though, Cladhaire. Greatly appreciate it, and love the mod (I've got most of the healers in my guild switched over to it now!).

since a few days ago, dunno when exactly it started, clique isnt loading the xperl plug-in anymore (happened first with x-perl 1.7.1 and continued with 1.7.2, and 1.7.3 with a just updated clique. to get the plugin to load again i changed the test function from:

function Plugin:Test()
  if not IsAddOnLoaded("Perl") then return false end
  return --author == "Zek, Nymbia, Perl"
end

to:

function Plugin:Test()
  --if not IsAddOnLoaded("Perl") then return false end
  return Perl_Config --author == "Zek, Nymbia, Perl"
end

basically just copying whats it doing with other plugins.
and it made it work again :)
didnt check that with the just updated clique version but i think it still will load, will test it later today...

Thanks for this wonderful addon.

One question:
When I try to use it with sRaidframes, it doesnt work as the ctra plugin doesnt get loaded. When I enable ctraidassist and sRaidframes the ctra plugin gets loaded and Clique works on both the ctra frames and the sRaidframes frames.

So how would I force Clique to load the ctra plugin as it somehow doesnt recognize sRaidframes to be ctra?

Thanks

EDIT: Latest SVN of both addons

Cladhaire.
It took me a long time to understand what changed in my UI before click no longer work.
When i tried to use the rezz macro, i had a big clash with EP_BestSpell, so i disabled it.
I reload this addon, and things seems now to work as it should.

I still have problem with rezz, but i just have to specify the spell rank to cast to reapair it.

The problem with French client is the Rank translation, so if there are some Fr users here, just install EasyPriest.
I really hope you can make the changes in clique localization, but as i said you, i really cant manage this.
Btw, i'm ready for all tests, if you may need some :)

Quote from r4d4 »

since a few days ago, dunno when exactly it started, clique isnt loading the xperl plug-in anymore (happened first with x-perl 1.7.1 and continued with 1.7.2, and 1.7.3 with a just updated clique. to get the plugin to load again i changed the test function from:

function Plugin:Test()
  if not IsAddOnLoaded("Perl") then return false end
  return --author == "Zek, Nymbia, Perl"
end

to:

function Plugin:Test()
  --if not IsAddOnLoaded("Perl") then return false end
  return Perl_Config --author == "Zek, Nymbia, Perl"
end

basically just copying whats it doing with other plugins.
and it made it work again :)
didnt check that with the just updated clique version but i think it still will load, will test it later today...

This is bad to do. The reason being is the X Perl plugin will load for ANY perl addon, i.e. PCUF, Perl, Numbia, XPerl-- and will break things. Zek really needs to add a way to find out if its HIS mod that's loaded or not.

posted a little bug on the bug report about pets being called while the hunter is in another zone. This causes the pet to show as ?? which in turn causes the clique error I reported in the bug report. I know this is small and insignificant but better to get it squashed now before this mod gets too popular ;) (oh and it will, you have out done yourself Cladhaire :p)

Yeah thanks.. it just needs a test for the unit information. Appreciate the report.

Quote from cladhaire »

This is bad to do. The reason being is the X Perl plugin will load for ANY perl addon, i.e. PCUF, Perl, Numbia, XPerl-- and will break things. Zek really needs to add a way to find out if its HIS mod that's loaded or not.

already thought so, but i am just happy that it continues to work :)

Talk to Zek.. shoudln't be tough for him to give me SOME variable unique to XPerl.

More things to squash!

I set up wrath rank 8 in the gui options as a default hostile spell. When selecting max rank it produced an error (as shown in the bug report I just submitted).

The weird thing is it still took the max rank settings even with the error.

the weirder thing is the reason I set up wrath is it dissapeared from my settings and I had to set it up again. This could have been a corrupt saved variable?

It was an issue on my end.. Its fixed on svn or should be. I'll check again