Someone clearly doesn't understand the nature of code writers.....Quote:
Originally Posted by Agent 0013
Someone clearly doesn't understand the nature of code writers.....Quote:
Originally Posted by Agent 0013
The quest watcher not working is probably the same thing that has happened to me. I play on seperate computers if that might give a clue. Not to make a mess, but it did/does work if I use an older version of Jamba (think it is .7c). No settings changed at all, just doesn't do tracking quests correctly.
Its working fine for me on 0.7g. Can you explain what you think is not working?Quote:
Originally Posted by ElectronDF
If I get a quest on my main, it doesn't show up in the quest tracker. The alts get the quest (auto-shared) and it doesn't show up in the quest tracker. If I go to the quest log on my main, and turn off the quest tracking manually (not Jamba buttons), it will show up for the main only. I have to go to each machine and turn off the quest tracking (Blizzard style, not Jamba) and it will show up for that person only. Basically quest tracking broke a few versions back for me. I use Blizzard's tracking and quest watcher, since it gives me the icon for using quest items. I box on 5 computers, not sure if that is causing problems either. My guess is Blizzard's quest tracker and Jamba's quest watcher don't like each other.
Well, that is totally weird, given that Jamba piggy backs off the Blizzard quest tracker and you can have both going at once with no problem.Quote:
Originally Posted by ElectronDF
You mention that you auto-share quests. You probably have to go into the quest log and use the Jamba Quest Bar to toggle tracking for that quest so that the toons watch the quest.
Perhaps you have another addon that is causing the problem. Do you use the default ui for the quest log, etc?
Also, are your toons all in the same team and do they all have the team list in their /jamba-team setup?
They are all in each team groups (hunters in 1 team and not in any other teams, pally's same way, etc). I tried again and it does work with .7d and not with .7e and above. No uninstall was done when I changed things, just literally copied over the files from previous versions.
Is there something I should have done when changed over from .7d to .7e that might have made a difference? Is there some kind of debugging messages that I can see if the quest tracking is working or just get caught up in a channel error or the alt doesn't think it is with the main for some unknown reason. It might be as simple as recreating the teams that fixes it, but I didn't want to go chasing down wild geese for no reason.
What type of message, if I could see the debug stuff would I be looking for?
for example:
1) on main, "Jamba-quest-watching-master module sent toggle quest watch for quest #345981 to alts"
2) on alts, "Jamba-quest-watching-alt module received toggle quest watch for quest#345981 from the master"
Can we get an option to display the team list horizontally instead of just vertically?
Member1 Member2 Member3
Health Health Health
XP XP XP
So far things are working well.
currently getting this error every time i log in or reload:
Message: Prefix is too long
Time: 05/07/11 17:14:52
Count: 1
Stack: [C]: ?
[C]: in function `f'
...ce\AddOns\Jamba\Libs\AceComm-3.0\ChatThrottleLib.lua:299: in function `Despool'
...ce\AddOns\Jamba\Libs\AceComm-3.0\ChatThrottleLib.lua:363: in function <...ce\AddOns\Jamba\Libs\AceComm-3.0\ChatThrottleLib.lua:320>
Locals: (*temporary) = "LibGroupTalents-1.0"
(*temporary) = "HELLO 66"
(*temporary) = "PARTY"
Quote:
Originally Posted by Kris1234
This is not a problem with Jamba. There is another addon causing this error. I imagine it will be something to do with talents. Try turning off all other addons apart from Jamba (and ISBoxer if you use it) and the message will go away.
ok thanks, will have to do some testing :)Quote:
Originally Posted by Jafula