My paladin is very low level but already it was applying more than one seal / judging it etc. I imagine it just gets more complex at higher levels. So is a seal button actually required? If all paladins using AutoBar have to make their own seal button(s) it is better to just have it built in.
Or is this something the standard bar buttons are better for. Discuss...
when i'm soloing (i'm prot), i switch constantly to eliminate downtime and i keep having to dig through my book for the extras. it's just fluff, but it helps keep my buttons sorted :)
Sounds cool. ^^
Is that much slower than a PT table?
Well, we'd still want to be using the PT table, so it does mean a wee bit of new processing. But getting the item category takes a fraction of a microsecond, and we'd only be scanning the tooltip for Quest:Quest items. Tooltip scanning takes less than a millisecond though, and is totally cacheable.
So... I really wouldn't worry about it performance wise.
As for the risk of non-usable items popping up, I wouldn't really worry about it. I'd rather have a "dud" button pop up during a handful of quests (which will tell me where I should be using the item if I do click it!) than missing it entirely 99% of the time which is the case right now.
Well, the PT table would change from being vetted items to being items to exclude. I should probably construct the pre wotlk as the inverse of the current set, and get cracking on adding the wotlk exclude items.
Meanwhile I am trying to shoehorn drag and drop into AceGUI and it is frustrating so far. I will fix the quest stuff when I am done with that.
Why would it have to be a list of items to exclude? If you are scanning for usable quest items, you are only missing a scant few - those would be the ones to keep in a PT table? (would be something like usable items that belong to quests but do not say "Quest Item" in their tooltip)
Why would it have to be a list of items to exclude? If you are scanning for usable quest items, you are only missing a scant few - those would be the ones to keep in a PT table? (would be something like usable items that belong to quests but do not say "Quest Item" in their tooltip)
You misunderstand the problem. Reread the below again and notice the part where scanning gives you items that you do not want.
since i have learned the new artisan cooking skill in Nordend the cooking button has diappeared in my basic autobar. All other artisan skills (ingeneering, leatherworking) are there but cooking is missing.
I am on a german client. Could this be the reason?
You misunderstand the problem. Reread the below again and notice the part where scanning gives you items that you do not want.
Uhm... okay, re-read, but I still can't follow. I have yet to find a "Use: Blablabla" item that isn't actually usable. You may get the hand-symbol that gets a blue glow if you hover over the correct object to use it on, but I would not call that unusable. It may in some / many cases be easier to just click on the object in game, but who cares?
Uhm... okay, re-read, but I still can't follow. I have yet to find a "Use: Blablabla" item that isn't actually usable. You may get the hand-symbol that gets a blue glow if you hover over the correct object to use it on, but I would not call that unusable. It may in some / many cases be easier to just click on the object in game, but who cares?
The purpose of AutoBar is to make things easier. Opening your bags and looking for some item you MUST click on sucks. Hence the Quest Button. it specifically contains items that you have to right click on to use.
Having a button to click on so that the cursor glows and then you can click on an in game object you could have just clicked on in the first place is silly and absolutely not the point. All such items need to be specifically filtered out.
...since i have learned the new artisan cooking skill in Nordend the cooking button has diappeared in my basic autobar. All other artisan skills (ingeneering, leatherworking) are there but cooking is missing...
It is much more likely that something else is wrong. The spell name used is from:
GetSpellInfo(33359)
you should be able to do the following:
/script print(GetSpellInfo(33359))
note the name that gets printed out.
using that you should be able to do
/cast Cooking
where Cooking is whatever German name you got above.
Let me know if anything goes wrong with this. The same name ought to be used for all skill levels and the artisan one should not have suddenly changed after years of use.
If you can do this then follow the debug instructions from the very first post in this thread.
Using /script print(GetSpellInfo(33359)) i get the following output:
Kochkunst Meister Interface\Icons\INV_Misc_Food 0 false 0 0 0 0
When trying /cast Kochkunst nothing happens
Looking at the spellbook i see the the cooking is now called 'Kochen' so indeed the name has changed!
/cast Kochen brings up the cooking interface.
So it seems that as soon the artisan cooking skill is gained the skill changes its name on german clients from 'Kochkunst' to 'Kochen'. Very strange.
I'm not sure if this has been posted somewhere but is there a fix for the WotLK quest items not showing up? If there is, sorry. Also is there a fix for death knights?
BTW, I love autobar to death, been using it for years. Keep it up.
Using /script print(GetSpellInfo(33359)) i get the following output:
When trying /cast Kochkunst nothing happens
Looking at the spellbook i see the the cooking is now called 'Kochen' so indeed the name has changed!
/cast Kochen brings up the cooking interface.
So it seems that as soon the artisan cooking skill is gained the skill changes its name on german clients from 'Kochkunst' to 'Kochen'. Very strange.
I hope this helps.
Kind regards
X-buZZ
/cast Kochen should still work no matter what skill level you are. Also, /run CastSpellByName("Kochen") will work since CastSpellByName() is not protected when "casting" trade skills.
Hi,
i use autobar since long time, but i ve many problem since some updates and maybe wotlk. issues i ve are with poison, quest and maybe more with popup button (i use shift to popup )
i think problem is with arrange on use because i can uncheck this but if i check again (so enable) i have one lua issue and i have this for all button i try to change arrange on use status.
maybe refresh problem because of lua error: i select "arrange on use" i have lua issue and can't see little box clecked but if i go another button on the bar and if i go back previous button, little box is checked this time.
difficult to explain really good because my english is little poor but maybe with screenshot , youcould understand more good.
so i can't use poison, because when i choose one (with shift or not) , sometimes ive lua error (always the same) , and sure never i can replace poison because little blizzard popup ask me for replace but disappear in 1 sec.....very curious..but really annoying
thanks if u have some idea.
ahh of course, i tried to delete savevariable but no good change.
http://code.google.com/p/autobar/wiki/Usage
My paladin is very low level but already it was applying more than one seal / judging it etc. I imagine it just gets more complex at higher levels. So is a seal button actually required? If all paladins using AutoBar have to make their own seal button(s) it is better to just have it built in.
Or is this something the standard bar buttons are better for. Discuss...
when i'm soloing (i'm prot), i switch constantly to eliminate downtime and i keep having to dig through my book for the extras. it's just fluff, but it helps keep my buttons sorted :)
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorWell, we'd still want to be using the PT table, so it does mean a wee bit of new processing. But getting the item category takes a fraction of a microsecond, and we'd only be scanning the tooltip for Quest:Quest items. Tooltip scanning takes less than a millisecond though, and is totally cacheable.
So... I really wouldn't worry about it performance wise.
As for the risk of non-usable items popping up, I wouldn't really worry about it. I'd rather have a "dud" button pop up during a handful of quests (which will tell me where I should be using the item if I do click it!) than missing it entirely 99% of the time which is the case right now.
Meanwhile I am trying to shoehorn drag and drop into AceGUI and it is frustrating so far. I will fix the quest stuff when I am done with that.
You misunderstand the problem. Reread the below again and notice the part where scanning gives you items that you do not want.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumsince i have learned the new artisan cooking skill in Nordend the cooking button has diappeared in my basic autobar. All other artisan skills (ingeneering, leatherworking) are there but cooking is missing.
I am on a german client. Could this be the reason?
Kind regards
X-buZZ
Uhm... okay, re-read, but I still can't follow. I have yet to find a "Use: Blablabla" item that isn't actually usable. You may get the hand-symbol that gets a blue glow if you hover over the correct object to use it on, but I would not call that unusable. It may in some / many cases be easier to just click on the object in game, but who cares?
The purpose of AutoBar is to make things easier. Opening your bags and looking for some item you MUST click on sucks. Hence the Quest Button. it specifically contains items that you have to right click on to use.
Having a button to click on so that the cursor glows and then you can click on an in game object you could have just clicked on in the first place is silly and absolutely not the point. All such items need to be specifically filtered out.
End of story.
It is much more likely that something else is wrong. The spell name used is from:
GetSpellInfo(33359)
you should be able to do the following:
/script print(GetSpellInfo(33359))
note the name that gets printed out.
using that you should be able to do
/cast Cooking
where Cooking is whatever German name you got above.
Let me know if anything goes wrong with this. The same name ought to be used for all skill levels and the artisan one should not have suddenly changed after years of use.
If you can do this then follow the debug instructions from the very first post in this thread.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumUsing /script print(GetSpellInfo(33359)) i get the following output:
When trying /cast Kochkunst nothing happens
Looking at the spellbook i see the the cooking is now called 'Kochen' so indeed the name has changed!
/cast Kochen brings up the cooking interface.
So it seems that as soon the artisan cooking skill is gained the skill changes its name on german clients from 'Kochkunst' to 'Kochen'. Very strange.
I hope this helps.
Kind regards
X-buZZ
BTW, I love autobar to death, been using it for years. Keep it up.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAutoBar-v678.3_beta_release, the MH/OH Weapon Buffing, isnt recognizing some rogues poisons.
Deadly Poison VIII
Instant Poison VIII
i made a 678.4 tag to pick up the changes
Thanks for all your hard work, really amazing mod.
i use autobar since long time, but i ve many problem since some updates and maybe wotlk. issues i ve are with poison, quest and maybe more with popup button (i use shift to popup )
i think problem is with arrange on use because i can uncheck this but if i check again (so enable) i have one lua issue and i have this for all button i try to change arrange on use status.
maybe refresh problem because of lua error: i select "arrange on use" i have lua issue and can't see little box clecked but if i go another button on the bar and if i go back previous button, little box is checked this time.
difficult to explain really good because my english is little poor but maybe with screenshot , youcould understand more good.
so i can't use poison, because when i choose one (with shift or not) , sometimes ive lua error (always the same) , and sure never i can replace poison because little blizzard popup ask me for replace but disappear in 1 sec.....very curious..but really annoying
thanks if u have some idea.
ahh of course, i tried to delete savevariable but no good change.