Authors CurseForge

ClosetGnome r68289 (revised recently), ClosetGnome_Banker r66041, ClosetGnome_Switcher r68962, updated standalone libraries, USEng client/server, WoW 2.4.1 live.

This is failing to recognize Adamantite Stingers (arrows) in a ClosetGnome set they are put in when trying to switch back to it. Those arrows are made via an Adamantite Arrow Maker.

Make a ClosetGnome set that includes a stack of those arrows above in the ammo slot & a bow. It saves properly. Then make & save a different set that includes some different armor, as well as a gun & (standard vendor) bullets instead of the arrows above.

Put on the "gun" set via ClosetGnome's FuBar tooltip. No problem. But then try to put the "bow" set back on via the same method. Get the following chat window feedback: "ClosetGnome: Couldn't find Adamantite Stinger in your inventory". The bullets remained in the ammo slot after the switch. This despite the fact that yes, that stack of arrows is in my inventory. All the rest of the equipment switched without a problem.

Tried switching back and forth between the "gun" and "bow" sets a few more times. Never a problem with the "gun" set, the "bow" always provided the above error message and the arrows were not swapped back in. Then tried a different bow & gun, relogged, remade the sets and so on. Same problem.

Then changed the "bow" set to use standard vendor Blackflight Arrows. This time no problems; ClosetGnome recognized them and the arrows were switched properly when manually switching sets via the FuBar tooltip.

Can't see what libraries (if any) ClosetGnome uses to recognize set components, but it needs to recognize Adamantite Stingers.

Recently rolled back to r52462--"Gnome 1.0"--to see if any in-between commits were causing the issue. Unfortunately, the problem is identical with it as with r68289 previously reported.

So tried a few other commits in between those two in the off-chance there could have been a fix-then-break. Tried r54143 ("Bugfix when using :AddSet directly"), r56858 ("Allow swapping ammunition in combat"), r57637 ("Bugfix for :WearSet when invoked with more than one argument and the character is in combat") & r60484 ("Don't re-hook if we're already hooked when creating a set").

All of them have the identical problem with those &*(^&%^ Adamantite Stingers. The itemID # is in the URL (verified in-game).

Any fix for the line 839 error?

There's a problem I've been experiencing lately. I currently use ClosetGnome and ClosetGnome_Switcher. I don't define a default set, because I prefer it to simply switch to my last used set.

If I have the following sets defined:

Cat form - weapon + idol (switcher configured to switch to this if i go cat form)
Damage - everything except weapon/idol slots
Flight form - first trinket slot for Charm of swift flight

Now if I equip my Damage set, hit cat form, go to flightform, cancel flight form. This results in my flight form trinket still equipped :(

Update: Seems to do the exact same thing with Closetgnome_Mount and using a land mount :/

Quote from Whitetooth »

Feature suggestion: When equiping an offhand, remember the bag where it came from, so when you equip a 2-hander, you can put the offhand back to where it came from, instead of having to manually move it from the backpack to the bag.

Can I vote for this option too? I would love to use closetgnome for this function... But it really drives me nuts to have my weapons out of place. I guess i'm one of those folks who likes their bags sorted a certain way ><

Thanks!

Spy

Quote from Jerry »

Crafted ammunition may have different uniqueID part from stack to stack. Thats the reason ClosetGnome fails to find them after the stack that was used when saving the set has been depleted.

(cheers)

That makes perfect sense. Hope there is a way around the issue. Doesn't seem like it with the way ClosetGnome currently works, though.

If item strings of differing stack levels of crafted ammo vary, ClosetGnome won't be able to find the saved string for the ammo in your saved variables...unless the stack count is identical.

I get the following error in closetgnome occasionally.
------------------------------------------------------
Date: 2008-05-08 13:00:01
ID: 53
Error occured in: Global
Count: 1
Message: ..\AddOns\ClosetGnome\ClosetGnome.lua line 848:
Invalid inventory slot in GetInventorySlotInfo
Debug:
Ace2\AceEvent-2.0\AceEvent-2.0.lua:299: TriggerEvent()
Ace2\AceEvent-2.0\AceEvent-2.0.lua:910:
Ace2\AceEvent-2.0\AceEvent-2.0.lua:903
---------------------------------------------------------
Any ideas?

I'm getting the same error as Mozul. It shows up whenever I use macros similar to the following:

#showtooltip Wrath(Rank 10)
/cast Wrath(Rank 10)
/equip Idol of the Avenger

I have similar macros for Starfire, Lifebloom and Rejuvenation.

Quote from Pusikas »

ClosetGnome_Mount has GratuityLib in its X-Embeds. But I can run it just fine with LibGratuity-3.0 installed (disembedded). No idea if that is something that should be "upgraded".

Quote from Rabbit »

Because LibGratuity-3.0 fools AceLibrary into thinking that it is Gratuity-2.0 as well.

Actually, it looks like CG_Mount never even opens GratuityLib. Can it be removed from the OptDeps/X-Embeds alltogether?

Hello I found an issue with druids and Switcher!
I have a Feral set for cat and bear and a "Caster" Set (I tried 1 set and 2 sets for cat and bear and it does not work either).
If I switch into bear I get my staff, if I get back to normal or moonkin I have my Caster set and it works fine BUT if I change from Cat to Bear or Bear to Cat it does not equip my feral staff (it should keep it its the same for both forms) it changes to the caster set (Default in switcher)!
It only happens if you swich between the two feral forms, all other forms work fine. Does anyone know how to fix this? :(
If I dont use the Default set it works but I need it to have my Caster set when I cast something in Bear/Cat form.

And I noticed that it says "Item not found" if I switch to Moonkin or Default form but the Item is in my Bag and equipped properly. o.O
I use it on the German Client.

Quote from dyree »

Actually, it looks like CG_Mount never even opens GratuityLib. Can it be removed from the OptDeps/X-Embeds alltogether?

It uses SpecialEvents-Mount which needs GratuityLib.

Long time user, first time poster...

Anyways, lately I've had an issue when trying to update a set. After shift-clicking the set in the fubar menu, the window pops up as usual, however only the first two letters of the set name are shown (SH, instead of SHADOW RESIST, in this case). Moreover, I can't add any letters, or create new sets with longer than two letter names.

I vaguely remember having this issue before, but I don't know how I fixed it, if I am even remembering correctly.

I tried to search for similar problems, didn't see anything, though searching here isn't as intuitive as it could be.

Any assistance or advice is welcome!

(Oh, right... I'm just using ClosetGnome, no other components or pieces)

Quote from tsigo »

It uses SpecialEvents-Mount which needs GratuityLib.

Bah, I missed that. Oh well.

So, a few restarts of wow later the problem just solved itself. I didn't change... anything.

I know, it sounds like I'm insane.

Quote from Bl4ckSh33p »

Hello I found an issue with druids and Switcher!
I have a Feral set for cat and bear and a "Caster" Set (I tried 1 set and 2 sets for cat and bear and it does not work either).
If I switch into bear I get my staff, if I get back to normal or moonkin I have my Caster set and it works fine BUT if I change from Cat to Bear or Bear to Cat it does not equip my feral staff (it should keep it its the same for both forms) it changes to the caster set (Default in switcher)!
It only happens if you swich between the two feral forms, all other forms work fine. Does anyone know how to fix this? :(
If I dont use the Default set it works but I need it to have my Caster set when I cast something in Bear/Cat form.

And I noticed that it says "Item not found" if I switch to Moonkin or Default form but the Item is in my Bag and equipped properly. o.O
I use it on the German Client.

I have the exact same problem. Has there been any resolution on it?