I have been trying to avoid timers as much as possible, but yes, this did cross my mind and I'll probably do something along these lines. Kinda holding out on a Blizz fix (which is silly)...Quote:
Originally Posted by ElectronDF
Printable View
I have been trying to avoid timers as much as possible, but yes, this did cross my mind and I'll probably do something along these lines. Kinda holding out on a Blizz fix (which is silly)...Quote:
Originally Posted by ElectronDF
Hi Jafula,
I recently found out about the Jamba trade window where you can load your bags and shift it to your slaves - nice idea and job!!! Really impressive! One suggestion is to make it more clear with what you mean by "load theirs" or "load mine". I'm never sure if that means load my bags or load my trade window.
Thanks! I like the trade feature too. It's always load the trade window, never the bags. "Load mine" loads your trade window with stuff from your bags. "Load theirs" loads their trade window with stuff from their bags.Quote:
Originally Posted by Owltoid
Have you watched the video?
http://www.dual-boxing.com/showthread.php?t=31837
im not sure if anyone else has experienced this, but when showing the power bars in the display, they never move from 100% altho the health bars seems to be fine
I have the same problem with the power/mana bars. Always at 100% and no longer reflect true current mana.
Hey Jafula,
I tried using the auto-purchase and was getting strange results. It used to work perfectly for me. This time I added 20 Honeymint Tea to everyone (pushed settings), went to talk to the vendor, and toons would buy like 3 or 4 (they had less than 20 to start with and would end up with 4 or 8 or some random number).
Quote:
Originally Posted by Kris1234
Thanks for the bug reports. I've fixed the issue and you'll get the fix in the next release of Jamba.Quote:
Originally Posted by Mystic
It's a bug with the patch. I've fixed it and you'll get the fix soon.Quote:
Originally Posted by Owltoid
Looks like the real id whisper forwarding is working again. I've had a conversation with someone and the whispers forward correctly without any lua errors. Something Blizzard changed in a small patch recently perhaps?
Anyway, if its not working for you, please let me know with the text of the lua error if possible.
Received this error message after accepting quests from Remy "Two Times" in Goldshire. This is with Jamba 0.7c. It happened with both low-level quests this NPC offers.
Lua error is as follows:
Message: ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: bad argument #1 to 'find' (string expected, got nil)
Time: 11/07/10 00:06:28
Count: 2
Stack: [C]: in function `find'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: in function `GetQuestObjectiveCompletion'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1017: in function `JambaQuestWatcherUpdate'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:834: in function <...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:829>
(tail call): ?
[C]: in function `AddQuestWatch'
Interface\FrameXML\QuestLogFrame.lua:264: in function <Interface\FrameXML\QuestLogFrame.lua:246>
Locals: (*temporary) = nil
(*temporary) = "(.*):%s(.*)"
(*temporary) = "string expected, got nil"
I also noticed this same error when pressing the "Update" button on the quest watcher on the master. When this same button is pressed on the slave, the following error results:
Message: ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: bad argument #1 to 'find' (string expected, got nil)
Time: 11/07/10 00:20:04
Count: 5
Stack: [C]: in function `find'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: in function `GetQuestObjectiveCompletion'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1017: in function `JambaQuestWatcherUpdate'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:905: in function `DoQuestWatchListUpdate'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1600: in function `JambaOnCommandReceived'
Interface\AddOns\Jamba\JambaCore.lua:339: in function `OnCommandReceived'
Interface\AddOns\Jamba\JambaCommunications.lua:405 : in function `?'
Interface\AddOns\Atlas\Libs\CallbackHandler-1.0.lua:146: in function <Interface\AddOns\Atlas\Libs\CallbackHandler-1.0.lua:146>
[string "safecall Dispatcher[4]"]:4: in function <[string "safecall Dispatcher[4]"]:4>
[C]: ?
[string "safecall Dispatcher[4]"]:13: in function `?'
Interface\AddOns\Atlas\Libs\CallbackHandler-1.0.lua:91: in function `Fire'
...ce\AddOns\AtlasLoot\Libs\AceComm-3.0\AceComm-3.0.lua:268: in function <...ce\AddOns\AtlasLoot\Libs\AceComm-3.0\AceComm-3.0.lua:257>
Locals: <none>
Let me know if you need any additional information.
-CA
Seems more like its an ace3 library error or something;
Message: SendChatMessage(): Invalid escape code in chat message
Time: 11/08/10 00:34:28
Count: 1
Stack: [C]: ?
[C]: in function `SendChatMessage'
Interface\AddOns\Jamba-Talk\JambaTalk.lua:456: in function <Interface\AddOns\Jamba-Talk\JambaTalk.lua:439>
(tail call): ?
...ce\AddOns\Jamba\Libs\AceComm-3.0\ChatThrottleLib.lua:416: in function `SendChatMessage'
Interface\AddOns\Jamba\JambaCommunications.lua:745 : in function `SendChatMessage'
Interface\AddOns\Jamba-Talk\JambaTalk.lua:519: in function `ForwardWhisperToMaster'
Interface\AddOns\Jamba-Talk\JambaTalk.lua:484: in function `?'
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147: in function <...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
[string "safecall Dispatcher[16]"]:4: in function <[string "safecall Dispatcher[16]"]:4>
[C]: ?
[string "safecall Dispatcher[16]"]:13: in function `?'
...er4\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
...AddOns\Bartender4\libs\AceEvent-3.0\AceEvent-3.0.lua:120: in function <...AddOns\Bartender4\libs\AceEvent-3.0\AceEvent-3.0.lua:119>
Locals: <none>
I can confirm this bug. Only started this past week end though. My latest addon additions are Altoholic and related DataStore items. Will try disabling those and see if the error still occursQuote:
Originally Posted by CommanderAngry
EDIT: Removing Altoholic et al doesn't resolve this, and I now get the failure on entering the world - I was only getting it on update/NPC interaction previously. Error follows:
Let me know if you want someone to test things for you, Jafula.Code:Message: ...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: bad argument #1 to 'find' (string expected, got nil)
Time: 11/08/10 09:49:33
Count: 1
Stack: [C]: in function `find'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:909: in function `GetQuestObjectiveCompletion'
...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1017: in function <...face\AddOns\Jamba-QuestWatcher\JambaQuestWatcher.lua:1005>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[2]"]:9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?
...face\AddOns\Jamba\Libs\AceTimer-3.0\AceTimer-3.0.lua:164: in function <...face\AddOns\Jamba\Libs\AceTimer-3.0\AceTimer-3.0.lua:138>
Locals: <none>
Thanks for the bug reports re: the quests, I'll have a look at them soon.
Does this happen all the time or only with certain messages?Quote:
Originally Posted by smallo
Its all the time, "BUT ONLY" with the Real ID whispers.Quote:
Originally Posted by Jafula
When someone whispers one of the slaves and it tries to forward to the master.
The normal whispers *in the pinky type text* all forward correctly, just the Real ID *blue ones* which give that error.
I tried disabling bartender, cause i seen that in the error report, but then i get a Atlasloot error, just like the bartender one.
It goes on like that thru out loads of other ace3 librarys, then eventually im down to nothing, and it does it for the Ace3 library in jamba. Which is why i tought it was an ace3 thing and not a jamba thing.
Its done it ever since the damned patch, i just never noticed cause i dont have many real id friends added, just my brother. maybe blizz changed a hidden something or ace3 changed a lil something in their updates.. im no expert at this stuff.
but if ya need me to do something extra to test soemthing for ya, just yell, its no problem at all.
Remy is really nice to me. I don't get a lua error at all. However, thanks to both of your lua error posts, I can pinpoint where the error happened and I have stuck a fix in that should stop the error from happening.
What I _think_ is happening is that the server is a little slow returning quest information and Jamba has got caught up.
Quote:
Originally Posted by Iru
Bizarre, all Real ID whispers working fine at my end (the blue ones). Are your friends trying to send you links or just regular text? I can't figure out what is going wrong here.
Quote:
Originally Posted by smallo
Jamba 0.7d Released.
Changes...
Follow
* New option "Only warn if outside follow range". This is off by default. If it is on and you are in follow range and follow breaks you will not get a warning, so be careful!
Purchase
* Fixed bug where toons were not purchasing the correct amount of items.
Proc
* Fixed bug where you were unable to choose a sound for a proc. You can now choose sounds for procs!
Display Team
* Power bars now update properly.
Its just regular text chit chat from my brother - cause i added him when he changed to horde. before that i never noticed it because i didnt have any real ID people. always hated the concept of someone seeing exactly what char and server i was on.Quote:
Originally Posted by Jafula
I'll just reinstall ace3 on its own and see what happens from there.
Jafula,
We love Jamba!,
One quick request though: Are there anyway to condense the quest watcher to something of quest helper style like:
XXXXX Quest: 4/5 || I.e 4 out of 5 members have completed it, then you can choose to expand if you want? or have the option to be collapsed by default.
thanks!
Anywhere i can read a consise rundown on what Jamba does, ive browsed all the threads and its a bit daunting.
I can´t disban my team anymore - any known addon that is stopping Jamba from working correctly ??
YouArentInAPartyFix will break Jamba.Quote:
Originally Posted by Tin
I could add an option so that the quest objectives that show toon progress below them are collapsed by default.Quote:
Originally Posted by Igg
Here is a ticket. I'll see if I can do that for you at some stage.
http://wow.curseforge.com/addons/jam...ves-that-show/
So, I decided to try the newest version (0.7d) in place of my old one (0.4d) and am having a difficult time figuring out how to change focus targets. I've read through everything I could find and haven't been able to figure out what I need to do. if I manually set the focus target on each of my 4 accounts, everything works fine until I change master. The idea is to have the new master set as the new focus for each through a keybind however there is nothing in my keybinds under Jamba to allow for this.
On http://wow.jafula.com/addons/jamba/jamba-core I find this info:
Jamba cannot automatically change your characters focus for you. But what it can do, is update an internal macro that sets focus; /focus Toonname. If you select this option, when the master changes, Jamba will update this internal macro to /focus the-new-master. To access this macro, you must bind a key (in the wow key bindings under the Jamba heading) to Set Focus. Please note that Jamba cannot update this macro if you change masters while in combat.
but I don't see this. Please tell me what I'm missing.
Thank you
Col
Bnet chat forwarding and relay doesn't work for me unless "Fake Whispers For Clickable Player Names" is also checked. Is that suppose to happen? Because it is annoying not being able to quickly reply with "r"
I removed that functionality a long time ago. Basically now, you need to use Jamba-Macro instead. Jamba-Macro is a lot more flexible and lets you do much more than focus. If you cannot work out how to use Jamba-Macro, please ask in this thread.Quote:
Originally Posted by ColAngus
And sorry, the documentation is way out of date.
No, thats a bug, I'll check it out.Quote:
Originally Posted by Zal
Edit: Here's the ticket:
http://wow.curseforge.com/addons/jam...for-me-unless/
Thanks. I read about Jamba-Macro. It sounds very cool but my AHK script and macros are so simple, I'm not sure if I want to go through all the work to switch over to a true FTL setup right now. 0.7d looks amazing though.Quote:
Originally Posted by Jafula
Thank you
Col
This was hardcodet into the UI that I use - Got the line removed and now everything is working as it couldQuote:
Originally Posted by Jafula
Thx for this. I also use LUI and found your post in the support forums.Quote:
Originally Posted by Tin
i am having a very strange issue. my Quest Watcher goes aways if i relog or /reload ui.
The only way to get it back is to delete everything and log in the game and its there..... until the next time i do /reload or relog :(
i used both versions 0.7c and 0.7d and checked all options to be enabled.
Any idea what might be wrong?
The quest watcher works when you track a quest on a toon. You need to track quests on all toons for the quest watcher to work for all your team.Quote:
Originally Posted by Sebian
When you log out / reload ui, sometimes the quests get untracked. Track them again and the quest watcher should come back up.
The default options are pretty good. Try going back to them rather than checking everything...
If you are still having trouble; disable all addons except the Jamba ones and see if the problem goes away.
Hope that helps!
Hey Jafula,
So I looked through the posts since the patch and saw that the Bnet forwarding wasn't working, but that you fixed it......but mine's not working and I'm using vers 7d. Thanks!
Date: 2010-11-19 00:02:17
ID: 1
Error occured in: Global
Count: 1
Message: SendChatMessage(): Invalid escape code in chat message
Debug:
(tail call): ?
[C]: ?
[C]: ?
[C]: SendChatMessage()
Jamba-Talk\JambaTalk.lua:456:
Jamba-Talk\JambaTalk.lua:439
(tail call): ?
...ce\AddOns\Jamba\Libs\AceComm-3.0\ChatThrottleLib.lua:416: SendChatMessage()
Jamba\JambaCommunications.lua:745: SendChatMessage()
Jamba-Talk\JambaTalk.lua:519: ForwardWhisperToMaster()
Jamba-Talk\JambaTalk.lua:484: ?()
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147:
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:147
[string "safecall Dispatcher[16]"]:4:
[string "safecall Dispatcher[16]"]:4
[C]: ?
[string "safecall Dispatcher[16]"]:13: ?()
...ist\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: Fire()
...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:120:
...s\AckisRecipeList\libs\AceEvent-3.0\AceEvent-3.0.lua:119
AddOns:
Swatter, v3.1.16 (<%codename%>)
Babylonian, v5.1.DEV.130
Carbonite, v4.013
CarboniteTransfer, v1.01
Configator, v5.1.DEV.282
DBMCore, v
DBMPartyWotLK, v
DebugLib, v5.1.DEV.275
Jamba, v0.7d
JambaDisplayTeam, v0.7d
JambaFollow, v0.7d
JambaFTL, v0.7d
JambaItemUse, v0.7d
JambaMacro, v0.7d
JambaProc, v0.7d
JambaPurchase, v0.7d
JambaQuest, v0.7d
JambaQuestWatcher, v0.7d
JambaSell, v0.7d
JambaTalk, v0.7d
JambaTaxi, v0.7d
JambaToon, v0.7d
JambaTrade, v0.7d
Prat30, v3.4.12
Prat30Libraries, v
BlizRuntimeLib_enUS v4.0.3.40000 <us>
(ck=83b)
mines isnt either unless I enable fake whispers
Could you please add a "lock bar" option on the item use bar? So that when its activated new icons can still be placed in it, but nothing can (by mistake) be removed?
Back to this issue. I've noticed that when my account with RealID friends is the master/main window, everything is fine with RealID whispers. When it is NOT the master account, I get a lua error. I'm not in-game at the moment, so I can't get the exact error, but I'll edit this post and tack it on when I can capture it.
-CA
would love to see this slash command added:
/jamba-team removeall
for clearing the team list
EDIT: Error isn't Jamba Proc.
This isn't a Jamba-Proc error. It's a LibHealComm error. No parts of Jamba use LibHealComm.
It doesn't look like LibHealComm has been updated for Cataclysm (on curse.com). Are you running it as an out of date addon?
Quote:
Originally Posted by Igg