Jamba 0.5 available for testing (Update 12).

[Jafula]

Im using ISXBoxer and today I had a problem with follow strobe. I switched from my usual window to one of the slaves and the old "main" refused to follow the new "main" without manually hitting my follow key.

You might want to talk to someone involved with ISBoxer; I've not had anything to do with it, but from the ISBoxer wiki, it looks like it does some sort of automatic Jamba integration, which will be broken with 0.5 (unless its been updated to handle 0.5).

Also updates to jamba options dont seem to be pushing to the slaves one thing that keeps cropping up is that the display of team will be screwed up on all slaves(blank bars or some slaves missing) until I open up jamba and unclick any option I selected (i.e. "experience bar") and then click it again. Once I push after that it's fine, but it seems to be screwed up everytime I log in.

The jamba options should be pushing to slaves correctly. Make sure you are using 0.5 Update 4 as I have made some bug fixes to the display team code.

[Khatovar]

Hiya Jafula,

Been playing around with things a bit tonight. While messing around with follow strobing and trying to figure a way to get strobing only while mounted {macro-wise} I ran across the following error

Message: Interface\AddOns\JambaDev\JambaTag.lua:345: table index is nil
Time: 09/08/09 00:55:14
Count: 94
Stack: [string "Interface\FrameXML\BasicControls.xml:<Scrip.. ."]:18: in function <[string "Interface\FrameXML\BasicControls.xml:<Scrip.. ."]:4>
(tail call): ?
Interface\AddOns\JambaDev\JambaTag.lua:345: in function <Interface\AddOns\JambaDev\JambaTag.lua:343>
Interface\AddOns\JambaDev\JambaTag.lua:500: in function `DoesCharacterHaveTag'
Interface\AddOns\JambaDev-Follow\JambaFollow.lua:933: in function <Interface\AddOns\JambaDev-Follow\JambaFollow.lua:928>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[2]"]:9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?
...e\AddOns\JambaDev\Libs\AceTimer-3.0\AceTimer-3.0.lua:158: in function <...e\AddOns\JambaDev\Libs\AceTimer-3.0\AceTimer-3.0.lua:132>

Locals: characterName = nil
(*temporary) = <table> {
Shewhotakes = <table> {
}
Themoonbiter = <table> {
}
Kina = <table> {
}
Messkit = <table> {
}
Çroaker = <table> {
}
}
(*temporary) = <table> {
}
(*temporary) = "table index is nil"
AJM = <table> {
moduleDisplayName = "Core: Tags"
SetDefaultModuleLibraries = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:373
EnableModule = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:338
modules = <table> {
}
baseName = "JambaDev"
IterateEmbeds = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:448
SecureHook = <function> defined @Interface\AddOns\JambaDev\Libs\AceHook-3.0\AceHook-3.0.lua:336
RawHookScript = <function> defined @Interface\AddOns\JambaDev\Libs\AceHook-3.0\AceHook-3.0.lua:395
settingsDatabaseName = "JambaTagProfileDB"
allTagsList = <table> {
}
chatCommand = "jamba-tag"
JambaSendMessageToTeam = <function> defined @Interface\AddOns\JambaDev\JambaModule.lua:68
defaultModuleState = true
RemoveTagCommand = <function> defined @Interface\AddOns\JambaDev\JambaTag.lua:416
IsEnabled = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:457
DisableModule = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:356
RemoveTagGUI = <function> defined @Interface\AddOns\JambaDev\JambaTag.lua:447
RegisterMessage = <function> defined @Interface\AddOns\DataStore\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:117
UnregisterMessage = <function> defined @Interface\AddOns\DataStore\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:180
OnCharacterRemoved = <function> defined @Interface\AddOns\JambaDev\JambaTag.lua:514
IsHooked = <function> defined @Interface\AddOns\JambaDev\Libs\AceHook-3.0\AceHook-3.0.lua:493
db = <table> {
}
SetEnabledState = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:430
Hook = <function> defined @Interface\AddOns\JambaDev\Libs\AceHook-3.0\AceHook-3.0.lua:274
enabledState = true
RegisterEvent = <function> defined @Interface\AddOns\DataStore\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:117
JambaModuleInitialize = <function> defined @Interface\AddOns\JambaDev\JambaModule.lua:90
JambaConfigurationGetSetting = <function> defined @Interface\AddOns\JambaDev\JambaModule.lua:130
SettingsTagListRowClick = <function> defined @Interface\AddOns\JambaDev\JambaTag.lua:592
IterateModules = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:443
JambaSendCommandToTeam = <function> defined @Interface\AddOns\JambaDev\JambaModule.lua:58
Enable = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:305
RegisterChatCommand = <function> defined @Interface\AddOns\DataStore\libs\AceConsole-3.0\AceConsole-3.0.lua:59
JambaRegisterModule = <function> defined @Interface\AddOns\JambaDev\JambaModule.lua:44
GetModule = <function> defined @Interface\AddOns\DataStore\libs\AceAddon-3.0\AceAddon-3.0.lua:222
JambaSendSettings = <function> defined @Interface\AddOns\JambaDev\JambaModule.lua:53
parentDi

Only on my slaves after using the command "/jamba-follow strobeon Kina slave" {also 'strobeonme'} . I get it on everyone if I use the all parameter. It spams at the same frequency as out of combat follow strobing. A little digging and it seems that Drinking/Eating is causing the error. Unchecking it causes the error to stop.

[Jafula]

Hiya Jafula,

Been playing around with things a bit tonight. While messing around with follow strobing and trying to figure a way to get strobing only while mounted {macro-wise} I ran across the following error



Only on my slaves after using the command "/jamba-follow strobeon Kina slave" {also 'strobeonme'} . I get it on everyone if I use the all parameter. It spams at the same frequency as out of combat follow strobing. A little digging and it seems that Drinking/Eating is causing the error. Unchecking it causes the error to stop.

Cheers; I found that one thanks to you. Was caused by a typo.

[rahven32]

Seems if you have follow after combat check and use the macro I posted above it will get confused if you try changing leaders. Sometimes I change and hit the follow macro and it will try to follow my old leader again. Sometimes several times. So if i switch and try and loot with a new leader sometimes in mid loot or even before reaching the body it will try to follow the old leader again. I just can't figure out how to do it everytime =/

[Jafula]

Seems if you have follow after combat check and use the macro I posted above it will get confused if you try changing leaders. Sometimes I change and hit the follow macro and it will try to follow my old leader again. Sometimes several times. So if i switch and try and loot with a new leader sometimes in mid loot or even before reaching the body it will try to follow the old leader again. I just can't figure out how to do it everytime =/

Hmmm, lets see if we can work this out. I'm about to post Update 5 and I'll add a message in Jamba-Follow that prints out when it gets the new master command (and who it thinks that master is). I'll also add a message when it gets the follow command as well and print out who its trying to follow. It'll be a bit spammy but it should help pinpoint what is going on.

Edit: I'm not about to post Update 5, because I can't test it due to WoW being offline for maintenance - ah well, tomorrow night then.

[joypunk]

Is there any reason the Jamba features are still active while your team isn't online... or on characters that aren't part of a team?

I currently only use Jamba on my Warlock/Hunter leveling team. All of my other characters do not need it. I get messages about accepting quests and even get warnings about follow being broken (who was I following??).

In fact, I think there is an issue with the following. When I am on my main, without a team, and no one in my group... and I am on a vehicle, when I exit combat it appears as though follow strobing attempts to follow myself. (Sorry, I'm not very good at explaining things.)

[Jafula]

Is there any reason the Jamba features are still active while your team isn't online... or on characters that aren't part of a team?

I currently only use Jamba on my Warlock/Hunter leveling team. All of my other characters do not need it. I get messages about accepting quests and even get warnings about follow being broken (who was I following??).

In fact, I think there is an issue with the following. When I am on my main, without a team, and no one in my group... and I am on a vehicle, when I exit combat it appears as though follow strobing attempts to follow myself. (Sorry, I'm not very good at explaining things.)

Thanks very much for your post and feedback.

I'd like Jamba to be able to be active and be reasonably unobtrusive on your characters. However, when Jamba starts up it will add a solo character to its own team and set that character to be its own master. If you type /jamba-team on one of your solo characters you should see that character in the team as the master.

Can you tell me what messages your are getting about accepting quests and when you get them?

I might need to add some logic in to Jamba-Quest to not send messages if there is only one member in the team.

Follow functionality is currently being "developed" again and I have probably broken something from 0.4. From your vehicle self follow problem description, I think I've missed the fixes from the last few months for those problems. I'll make sure they are in the code for Update 6.

Please do keep coming back here and posting your problems/issues.

[Jafula]

Update 5 available (see first post)

Jamba-Toon module added + some fixes.

Some debug messages in for master changing / following in Jamba-Follow.

To stop these messages, edit Jamba-Follow.lua and changed lines 153- 155 from

local function DebugMessage( ... )
AJM:Print( ... )
end

to

local function DebugMessage( ... )
-- AJM:Print( ... )
end


If you play with these messages on, please let me know if you notice anything unusual going on with when a character gets a new master and who it follows.

[rahven32]

New error with new version.

Date: 2009-09-08 17:32:46
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\JambaDev\JambaUtilities.lua line 73:
   bad argument #2 to 'format' (string expected, got nil)
Debug:
   (tail call): ?
   (tail call): ?
   [C]: format()
   JambaDev\JambaUtilities.lua:73: FormatMoneyString()
   JambaDev-Toon\JambaToon.lua:673: ?()
   ...onLoader\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
      ...onLoader\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
   [string "safecall Dispatcher[1]"]:4:
      [string "safecall Dispatcher[1]"]:4
   [C]: ?
   [string "safecall Dispatcher[1]"]:13: ?()
   ...onLoader\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
   ...ce\AddOns\Recount\Libs\AceEvent-3.0\AceEvent-3.0.lua:119:
      ...ce\AddOns\Recount\Libs\AceEvent-3.0\AceEvent-3.0.lua:118
AddOns:
  Swatter, v5.6.4424 (KangaII)
  AddonLoader, v2.0
  Align, v
  Ampere, v3.1.0.15
  BagnonForever, v1.1.2
  BagnonTooltips, v
  BrokerButtonFacade, v3.2.35
  BrokerLonnyGameMenu, v$Revision: 101 $
  BrokerLonnyMicroMenu, v$Revision: 101 $
  BrokerMacaroon, v30000.2
  BrokerProfessions, v1.0
  BrokerRecountStats, vv1.61
  BrokerSmartBuff, v3.2a
  ButtonFacade, v3.2.275
  ButtonFacadeApathy, v3.2.70
  caelNamePlates, v
  CBHViewport, v100
  Chinchilla, vv2.0.5
  Combuctor, v2.1.2
  CombuctorConfig, v
  CombuctorSets, v
  DockingStation, v0.3.2 (Beta)
  JambaDev, v0.5
  JambaDevDisplayTeam, v0.5
  JambaDevFollow, v0.5
  JambaDevFTL, v0.2
  JambaDevProc, v0.5
  JambaDevQuest, v0.5
  JambaDevTaxi, v0.5
  JambaDevToon, v0.5
  Livestock, v1.1.7
  Macaroon, v30100.2.6
  Mapster, v1.2.3
  myBindings2, v2.1.$LastChangedRevision: 51 $
  PhanxChat, v3.2.0.51-beta
  PitBull4, vv4.0.0-beta3-9-gc4985e6
  PowerAuras, v2.6.2O
  QuestHelper, v1.1.13
  Recount, v
  RedRange, v
  SatrinaBuffFrame, v3.1
  SmartBuff, v3.2a
  TipTop, v1.9.1
  TomTom, v222
  TweakWoW, v2.9.3
  zBrokerLocation, v1.2
  zBrokerPerformance, v1.1
  BlizRuntimeLib_enUS v3.2.0.30200 <us>
  (ck=487)

Also slaves are no longer completing quests if they have a reward choice.

[Jafula]

New error with new version.

Date: 2009-09-08 17:32:46
ID: 1
Error occured in: Global
Count: 1
Message: ..\AddOns\JambaDev\JambaUtilities.lua line 73:
   bad argument #2 to 'format' (string expected, got nil)

Also slaves are no longer completing quests if they have a reward choice.

Thanks, just uploaded a new version with a fix for that error.

Nothing has changed with the quest code. Can you check that your settings are correct. By default, if there is a reward choice, Jamba expects you to manually choose the reward and click complete.

Do you have the override option checked for if reward selected, use that reward?

If your settings are okay,I wonder if they changed something in the maintanence?