Download
(80 Kb)
Download
Updated: 02-21-14 12:32 PM
Pictures
File Info
Compatibility:
Siege of Orgrimmar (5.4)
Updated:02-21-14 12:32 PM
Created:07-29-10 06:15 PM
Downloads:3,707
Favorites:58
MD5:
5.4
Hydra - Multibox Leveling Helper
Version: 5.4.7.162
by: Phanx, Akkorian
Hydra is a multibox leveling helper that aims to minimize the number of times you need to actively control secondary characters.

Please note that Hydra is not a replacement for key cloning software — addons can’t cast spells, target units, or perform many other actions, so you will still need some way to send your key strokes and mouse clicks to your secondary characters’ instances of WoW.

Options are accessible by typing “/hydra” or by browsing to the Hydra panel in the Interface Options window. Several common commands can also be keybound in the Key Bindings window.


Feature Requests

No additonal major features are planned, but if you have an awesome idea (and you’ve double-checked that it’s something an addon can actually do), feel free to post a feature ticket, and if it’s something I think I’d use, I might add it.


Bug Reports

If you encounter a problem with Hydra, please try some quick troubleshooting steps, and then submit a bug report to let me know about the problem. Please include as much of the following information as you can:
  • Hydra version
  • WoW version, language, and region
  • Character level, class, faction, and server
  • Whether the problem happens when all other addons are disabled
  • Description of the problem (eg. what did you do? what did you expect to happen? what actually happened?)
  • Specific steps I can follow to reproduce the problem, if it's not clear from the description
  • Exact text of the first related error message, if any
  • Screenshot, if the problem is graphical
Remember to check on your ticket after a few days, as I may need more information from you in order to find and fix the problem!


Language Support

Works in all languages. Translated into English, Español, Français, Русский, and 한국어. To add or update translation for any language, enter them on the Hydra localization page on CurseForge, and then send me a PM here or on CurseForge to let me know that you’ve made changes. If you don’t have a Curse account and don’t want to create one, you can PM me your translations instead. Thanks!


Full Feature List

Hydra operates on the basis of “trust”. You tell it which characters you trust, whether they're your multibox characters or just your questing buddies, and features are enabled or disabled depending on whether you’re in a party with trusted characters or not. For example, whispers are only forwarded to party chat if everyone in the party is on your trusted list.

You can add or remove names to your trusted list in the options panel. There's also an option to add everyone in your current party to your trusted list, for quick setup for multiboxing groups.

Automation
  • Accepts summons and resurrections.
  • Declines duels, guilds, and arena teams.
  • Repairs equipment and sells junk to vendors.
Chat
  • Forwards whispers to secondary characters to party chat.
  • Forwards responses in party chat back to the sender as a whisper from the secondary character.
Follow
  • Notifies you when a party member starts or stops following you.
  • Type “/followme” or “/fme” to command all party members to follow you.
  • Type “/corpse accept” to make all other party members who are ghosts accept their corpse.
  • Type “/corpse release” to make all other party members who are dead release their spirit.
Mount
  • Causes other characters in the party (and in range) to mount when you mount.
Party
  • Accepts party invitations from trusted characters.
  • Request a party invitation by typing “/inviteme name”, where “name” is the target. If no target is specified, your current target unit will be used.
  • Request a promotion to party leader by typing “/promoteme”.
Quest
  • Accepts quests that another trusted party member already accepted, or all quests
  • Accepts quests shared manually or automatically (eg. escort quests) from players
  • Accepts quests started from looted items
  • Shares quests accepted from NPCs
  • Turns in completed quests (you still need to choose a reward if there’s a choice)
  • Abandons quests abandoned by trusted party members
Taxi
  • Autoselects the last taxi node selected by anyone in the party in the last 60 seconds.
  • Type “/cleartaxi” to manually clear the selection for the current character.
  • Hold the Shift key when interacting with the flight master to bypass this module’s functionality.

Limitations & Caveats

Chat module limitations:

Whispers containing a high number of “spam words” (words that commonly appear in goldselling, powerleveling, phishing, or other spam) are forwarded as “POSSIBLE SPAM” instead of the actual text, to avoid having your account appear to send spam. If you want to see the actual message, check the receiving character’s chat log.

Whisper forwarding is disabled in non-trusted parties, and there is currently no notification if someone whispers a secondary character in this situation.

Primary character detection:

Hydra currently offers two methods for detecting the primary character. By default, it assumes that the primary character is the party leader. You can use the options panel to switch to checking for applicaton focus instead, but this method will not work if you are using multiple physical machines, and may not work if you are running multiple clients in windowed mode.


Advanced Chat Usage

If whispers from multiple senders are forwarded to party chat, your responses in party chat are assumed to be directed toward the sender of the most recently forwarded whisper. You can respond to a previously forwarded whisper by prefacing your message in party chat with “@name”, where “name” is the name of your character that forwarded the whisper.

If whispers from multiple senders are forwarded by the same character, you can respond to a previous message by whispering that character with “@name message”, where “name” is the name of the person you want “message” to be whispered to. You can also use this feature to have your secondary characters send whispers to people who haven’t already whispered you.
Version 5.4.7.162
  • Fixed problems with cross-realm player names
  • Fixed notifications in the Follow module
  • Fixed the wrong text being used on some options for the Quest module
  • Added an in-game panel for enabling debugging messages on a per-module basis
  • Updated German translations

Version 5.4.2.151
  • Fixed more issues with the Mount module
  • Fixed an issue in the Chat module where "/w Player1 @Player2 message" would cause an infinite loop of whispers when Player1 and Player2 were both trusted group members
  • Adjusted default options for the Automation and Quest modules (eg. "Accept combat resurrections" is no longer enabled by default)

Version 5.4.2.139
  • Added an option to repair using guild funds when possible
  • Fixed an issue with the Mount module

Version 5.4.2.136
  • Fixed some more issues with the Follow module
  • Fixed the options UI for adding/removing trusted names

Version 5.4.1.132
  • Fixed sending /followme without a target
  • Fixed instance chat channel detection
  • Fixed chat master detection method option dropdown
  • Added "Work Order" quests to the automation blacklist
  • Added missing Spanish translations
  • Updated for WoW 5.4

Version 5.2.0.119
  • Added an option to resume following when leaving combat
  • Added a quest blacklist to prevent automating certain quests (eg. suboptimal Tillers turnins)
  • Added checks to prevent attempting to turn in repeatable quests that aren't complete (eg. you need 6 Dread Amber Shards to turn in Seeds of Fear)
  • Fixed an issue with realm names containing spaces
  • Fixed an issue preventing guild invite declining from fully disabling until a reload/relog

Version 5.1.0.103
  • Chat: Added support for forwarding Battle.net whispers and conversations
  • Follow: Fixed the follow key binding
  • Mount: Removed dependency on LibMountInfo, since changes in the library make it useless for Hydra's purposes
  • Quest: Added an option to accept all quests, in addition to shared quests
  • Quest: Added support for starting quests from items
  • Quest: Hide the useless gossip window for auto-pickup quests
  • Quest: Fixed turnin of quests with multiple valueless rewards
  • Quest: Fixed turnin of auto-completing quests
  • Quest: Fixed quest reward selection for class-filtered rewards in MoP
  • Quest: Fixed accepting escort quests started by others

Version 5.0.4.82
  • Fixed a call to a function that was removed in WoW 5.0
  • Added French translations from Araldwenn
  • Added Russian translations from Piton4
  • Updated Spanish translations from Valdesca

Version 5.0.4.80
  • Updated for WoW 5.0
  • Removed an unused library

Version 4.3.4.78
  • Updated for WoW 5.x (Mists of Pandaria).
  • Added basic support for raids. Not really tested. Please report issues.
  • Added an option for "/followme" auto-targeting: When this option is enabled and you are targeting a group member, the command will be sent only to that group member.
  • Added "/followme" targeting: If names are entered with the command, the command will be sent only to the specified character(s). Example: "/followme Charone Charthree".
  • Fixed multiple options panel issues.

Version 4.3.3.67
  • Fixed party invitations from trusted characters not being accepted automatically for some people due to inconsistencies in Blizzard UI/API behavior between different WoW installations

Version 4.3.2.64
  • Fixed the "Add Current Group" button for adding all members of the current group to the trusted list
  • Fixed party invitations from trusted characters not being accepted automatically due to changes in the Blizzard UI code

Version 4.3.0.62
  • Fixed class coloring of sender names in whisper forwarding
  • Slightly improved the efficiency of spam checking in whisper forwarding

Version 4.3.0.59
  • Updated for WoW 4.3
  • Fixed the "Add Name" input option

Version 4.2.0.56
  • Updated for WoW 4.2

Version 4.1.0.52
  • Updated for WoW 4.1
  • Updated and fixed the localization of all modules

Version 4.0.6.43
  • Reworked the options layout
  • Added in-game help text for some modules (more to come)
  • Added Spanish localization

Version 4.0.3.32
  • Fixed a bug in the mount module

Version 4.0.3.31
  • Fixed the auto quest turnin option
  • Fixed a bug in the quest module when turning a quest to an NPC who offered multiple quests
  • Added embedded copies of the libraries needed for the options panel, so you don’t need to download Ace3 separately or depend on other addons including it
  • Added LibMounts-1.0 to mount module for improved mount selection support between characters who don’t have the same mount
  • Added an optional DataBroker launcher

Version 3.3.5.24
  • Fixed names added to/removed from trust list via options panel not saving between sessions
  • Limited quest automation to one pickup/turnin per click on NPC to prevent some bugs

Version 3.3.5.23
  • Added "/corpse release" and "/corpse accept" commands
  • Added option to the Follow module to show/hide chat messages
  • Added basic spam detection to try to prevent forwarding spam whispers
  • Added trust list management functions to the options panel
  • Settings are now saved on a per-character basis
  • Added backwards compatibility for WoW 3.2 (still live in China)

Version 3.3.5.15
  • Added mount speed data so my blood elf paladin and warlock don't have to ride around on rainbow cocks :)
  • Added quest turnin notification to quest module
  • Fixed completed quest turnins (no idea how that "not" got in there)
  • Fixed global nil value error in automation module
  • Fixed application focus detection in chat module
  • Fixed party module trying to respond to the player's promotion request
  • Fixed "/promoteme" command
  • Changed "/inviteme" command to accept a name, but still fall back on using the current target
  • Changed quest module comm prefixes to be more distinctive
  • Turned off debugging for all modules

Version 3.3.5.8
  • Added options (requires standalone Ace3, and not extensively tested)
  • Fixed quest turn-ins
Archived Files (6)
File Name
Version
Size
Author
Date
5.4.2.151
72kB
Phanx
01-02-14 06:26 PM
5.4.2.139
71kB
Phanx
12-31-13 05:16 AM
5.4.2.136
71kB
Phanx
12-21-13 09:15 PM
5.4.1.132
71kB
Phanx
11-30-13 05:53 AM
5.2.0.119
71kB
Phanx
05-04-13 06:40 AM
5.1.0.103
68kB
Phanx
12-02-12 03:50 PM


Post A Reply Comment Options
Old 04-05-14, 09:18 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3677
File comments: 1860
Uploads: 38
Yep, those are all known issues, but I haven't done any multiboxing in at least 2 years, am not even actively playing WoW at the moment, and don't have that much time to spend debugging addons anymore, so pretty much they'll be fixed when they're fixed. If you have addon programming experience and can provide a tested and functional patch I'm happy to incorporate it, but otherwise, just telling me over and over what's broken isn't going to magically give me more spare time or get it fixed faster, sorry.
__________________
Author/maintainer of Grid, PhanxChat, ShieldsUp, and many more.
Troubleshoot an addonTurn any code into an addonMore addon resources
Need help with your code? Post all of your actual code! Attach or paste your files.
Please don’t PM me about addon bugs or code questions. Post a comment or forum thread instead!
Last edited by Phanx : 04-05-14 at 09:19 PM.
Phanx is offline Report comment to moderator  
Reply With Quote
Old 04-05-14, 11:36 AM  
SomeMMOPlayer
A Kobold Labourer

Forum posts: 0
File comments: 1
Uploads: 0
Update soon?

Want to say how much I have appreciated this addon. Has made the multiboxing I do so much nicer.

But at this point it has been broken for months now. Some parts still work (vendor selling, group joins, announcing follow break, etc.).

The functionality of auto refollow, /followme, /promoteme, taxi, and mount/dismount with group don't work at all anymore. The bulk of the issues start when realm merges happened. And you could sometimes revert to an older version and have some of it still working.

As of a couple months ago though (wow 5.4.7 patch?) something changed and no versions work correctly.

Seems to all be charname-realmname related. Hydra seems to be trying to pass charname-realmname to the follow and promote commands, but they only accept charname.

It is not a trusted name issue as far as I can tell. Have tried populated the trusted listed with just charname, with just charname-realmname, and with both.

I have tried running with all other addons disabled. I have deleted out all hydra configs and directories. Doesn't fix the problem.

Anyway. I have loved the addon for a long time, and have been limping along with standard wow macros. But hoping we see an update sometime soon to make this fully work with connected realms.
SomeMMOPlayer is offline Report comment to moderator  
Reply With Quote
Old 03-02-14, 01:35 AM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3677
File comments: 1860
Uploads: 38
Re: Re: Re: Re: Re: Quest Functionality

Originally Posted by acapela
What action(s) could an addon take to prevent another addon from receiving events?
It would have to explicitly unregister the event on the other addon's frame, and it seems extremely unlikely that any addon is actually doing that, so if some frames are receiving the event but not others after certain types of errors occur, it's most likely a game client bug.
__________________
Author/maintainer of Grid, PhanxChat, ShieldsUp, and many more.
Troubleshoot an addonTurn any code into an addonMore addon resources
Need help with your code? Post all of your actual code! Attach or paste your files.
Please don’t PM me about addon bugs or code questions. Post a comment or forum thread instead!
Phanx is offline Report comment to moderator  
Reply With Quote
Old 03-01-14, 09:47 PM  
acapela
A Cobalt Mageweaver
AddOn Author - Click to view AddOns

Forum posts: 235
File comments: 1286
Uploads: 6
Re: Re: Re: Re: Quest Functionality

Originally Posted by Phanx
If that's the case, there's probably just nothing I can do about it. When it happens, does any part of the default UI's quest display stop working? If you register for the same events in another addon, are they received there?
At this point, I have seen the problem crop up even when there are no LUA errors for the session. I will go ahead and instrument another addon, to see if the events are received elsewhere.

What action(s) could an addon take to prevent another addon from receiving events?
__________________
Current author/maintainer of Aloft (the nameplate addon)
http://www.wowinterface.com/download...AloftBeta.html
-----
Zippy said it best: "All life is a BLUR of Republicans and Meat!"
acapela is offline Report comment to moderator  
Reply With Quote
Old 02-24-14, 08:13 AM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3677
File comments: 1860
Uploads: 38
Re: Re: Re: Quest Functionality

Originally Posted by acapela
i don't know where these are coming from. this is attributed to PetTracker, which makes no reference to "CompactRaidFrame1" nor invokes method "ClearAllPoints" on anything anywhere.
I haven't seen that particular error, though PetTracker does raise an error for me if I'm in combat the first time the pet journal is opened in a given session...

Originally Posted by acapela
update: i have instrumented some of Hydra's quest event handling... when this problem occurs, it looks like the events are simply not being delivered.
If that's the case, there's probably just nothing I can do about it. When it happens, does any part of the default UI's quest display stop working? If you register for the same events in another addon, are they received there?
__________________
Author/maintainer of Grid, PhanxChat, ShieldsUp, and many more.
Troubleshoot an addonTurn any code into an addonMore addon resources
Need help with your code? Post all of your actual code! Attach or paste your files.
Please don’t PM me about addon bugs or code questions. Post a comment or forum thread instead!
Phanx is offline Report comment to moderator  
Reply With Quote
Old 02-24-14, 12:06 AM  
acapela
A Cobalt Mageweaver
AddOn Author - Click to view AddOns

Forum posts: 235
File comments: 1286
Uploads: 6
Re: Re: Quest Functionality

Originally Posted by Phanx
That's pretty weird. None of the quest API functions are protected in any way, so taint shouldn't be a factor. At least with that info I can try to reproduce it.
some refinement of this. i have observed a few cases where there is an error in BugSack, but Hydra is unaffected.

here is an example of the sort of error that seems to be affecting Hydra (or, i should say: immediately subsequent to this, Hydra quest functionality did not work properly):
Code:
2x [ADDON_ACTION_BLOCKED] AddOn 'PetTracker' tried to call the protected function 'CompactRaidFrame1:ClearAllPoints()'.
!BugGrabber\BugGrabber.lua:586: in function <!BugGrabber\BugGrabber.lua:586>
[C]: in function `ClearAllPoints'
FrameXML\FlowContainer.lua:157: in function `FlowContainer_DoLayout'
FrameXML\FlowContainer.lua:17: in function `FlowContainer_ResumeUpdates'
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:185: in function `CompactRaidFrameContainer_LayoutFrames'
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:130: in function `CompactRaidFrameContainer_TryUpdate'
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:62: in function `CompactRaidFrameContainer_OnEvent'
[string "*:OnEvent"]:1: in function <[string "*:OnEvent"]:1>
i don't know where these are coming from. this is attributed to PetTracker, which makes no reference to "CompactRaidFrame1" nor invokes method "ClearAllPoints" on anything anywhere.

a similar error is generated by OmegaMap, but i have observed several instances of this, subsequent to which there were no problems with Hydra:
Code:
2x [ADDON_ACTION_BLOCKED] AddOn 'PetTracker' tried to call the protected function 'CompactRaidFrame1:ClearAllPoints()'.
!BugGrabber\BugGrabber.lua:586: in function <!BugGrabber\BugGrabber.lua:586>
[C]: in function `ClearAllPoints'
FrameXML\FlowContainer.lua:157: in function `FlowContainer_DoLayout'
FrameXML\FlowContainer.lua:17: in function `FlowContainer_ResumeUpdates'
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:185: in function `CompactRaidFrameContainer_LayoutFrames'
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:130: in function `CompactRaidFrameContainer_TryUpdate'
...actRaidFrames\Blizzard_CompactRaidFrameContainer.lua:62: in function `CompactRaidFrameContainer_OnEvent'
[string "*:OnEvent"]:1: in function <[string "*:OnEvent"]:1>
OmegaMap does call "ClearAllPoints" on a wide variety of things, but does not directly reference anything called "CompactRaidFrame1".

in both cases, there is no error trace through the cited addon (PetTracker, OmegaMap, etc). these are generated into BugGrabber's Frame:ADDON_ACTION_BLOCKED/ADDON_ACTION_FORBIDDEN handler. i have enabled taint logging (i think/hope), and will take a look when i get a chance.

are these actually causal, do they just correlate, or are they completely unrelated? i don't know.

update: i have instrumented some of Hydra's quest event handling... when this problem occurs, it looks like the events are simply not being delivered.
__________________
Current author/maintainer of Aloft (the nameplate addon)
http://www.wowinterface.com/download...AloftBeta.html
-----
Zippy said it best: "All life is a BLUR of Republicans and Meat!"
Last edited by acapela : 02-24-14 at 01:20 AM.
acapela is offline Report comment to moderator  
Reply With Quote
Old 02-23-14, 10:25 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3677
File comments: 1860
Uploads: 38
Re: Quest Functionality

Originally Posted by acapela
I am finding quest autoshare/autoaccept functionality stops working as soon as any addon catches a LUA error. As far as I can tell, the perpetrating addon can be anything, and completely unrelated to Hydra.
That's pretty weird. None of the quest API functions are protected in any way, so taint shouldn't be a factor. At least with that info I can try to reproduce it.

Originally Posted by acapela
P.S. feature request: abandoning a quest should clear the quest out of all of the "accept" record-keeping in Hydra. Autoshare/autoaccept works differently (i.e. doesn't automate) after abandoning and re-acquiring a quest, versus acquiring the quest the first time.
Sounds reasonable, and the change is trivial, so that'll be in the next release.
__________________
Author/maintainer of Grid, PhanxChat, ShieldsUp, and many more.
Troubleshoot an addonTurn any code into an addonMore addon resources
Need help with your code? Post all of your actual code! Attach or paste your files.
Please don’t PM me about addon bugs or code questions. Post a comment or forum thread instead!
Phanx is offline Report comment to moderator  
Reply With Quote
Old 02-23-14, 09:58 PM  
acapela
A Cobalt Mageweaver
AddOn Author - Click to view AddOns

Forum posts: 235
File comments: 1286
Uploads: 6
Quest Functionality

Regarding quest functionality:

I am finding quest autoshare/autoaccept functionality stops working as soon as any addon catches a LUA error. As far as I can tell, the perpetrating addon can be anything, and completely unrelated to Hydra.

In fact, I am seeing LUA errors that apparently originate and propagate entirely within Blizzard FrameXML code which seem able to cause this.

Reloading my UI "fixes" everything. i.e. Abandon relevant quest, reload UI, re-acquire quest, and autoshare/autoaccept work fine.

Some independent confirmation of this would be helpful to my sanity .

I assume this is some sort of taint issue, and beyond Hydra's control. (Don't know enough about secure code to know whether/how Hydra configures its Quest functionality, though the relevant Blizzard API is documented as "secure"; follow/mount functionality doesn't seem to be affected.)

So, pending further testing and isolation of a (reproduceable) case where Hydra has trouble when this is NOT true, I am retracting my assertion that this part of Hydra is "not working"... doesn't look like a Hydra problem, and as far as I can tell there is no problem (Hydra's or otherwise) under a "clean" UI session. Hopefully that will save Phanx some testing effort.

P.S. feature request: abandoning a quest should clear the quest out of all of the "accept" record-keeping in Hydra. Autoshare/autoaccept works differently (i.e. doesn't automate) after abandoning and re-acquiring a quest, versus acquiring the quest the first time.
__________________
Current author/maintainer of Aloft (the nameplate addon)
http://www.wowinterface.com/download...AloftBeta.html
-----
Zippy said it best: "All life is a BLUR of Republicans and Meat!"
acapela is offline Report comment to moderator  
Reply With Quote
Old 02-23-14, 08:18 PM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 193
Uploads: 0
Yeah, they don't make it easy for you guys. Thanks for persisting!

Look forward to seeing/using the assist module when it's ready.


Originally Posted by Phanx
Alright, it appears that Blizzard, as usual, is lazy and inconsistent, and while some functions require a server name to work properly with cross-realm characters, other functions fail if a realm name is provided for same-realm characters. Blanket use of Ambiguate will break some things, so I've selectively used it only for the functions Blizzard forgot to update (eg. CheckInteractDistance, apparently) and will post a new release as soon as I've gotten a chance to actually test it with someone, which will probably be tomorrow.

And yes, the Assist module is coming soon. It's all written, but I didn't have time to do any testing, and wanted to get the other fixes out first.
kittykatmax is offline Report comment to moderator  
Reply With Quote
Old 02-23-14, 07:30 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3677
File comments: 1860
Uploads: 38
Alright, it appears that Blizzard, as usual, is lazy and inconsistent, and while some functions require a server name to work properly with cross-realm characters, other functions fail if a realm name is provided for same-realm characters. Blanket use of Ambiguate will break some things, so I've selectively used it only for the functions Blizzard forgot to update (eg. CheckInteractDistance, apparently) and will post a new release as soon as I've gotten a chance to actually test it with someone, which will probably be tomorrow.

And yes, the Assist module is coming soon. It's all written, but I didn't have time to do any testing, and wanted to get the other fixes out first.
__________________
Author/maintainer of Grid, PhanxChat, ShieldsUp, and many more.
Troubleshoot an addonTurn any code into an addonMore addon resources
Need help with your code? Post all of your actual code! Attach or paste your files.
Please don’t PM me about addon bugs or code questions. Post a comment or forum thread instead!
Phanx is offline Report comment to moderator  
Reply With Quote
Old 02-23-14, 09:48 AM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 193
Uploads: 0
Ok. I reinstalled your latest version of Hydra. I cleared both sets of trusted names. I created a party with two of my characters. I had them both "add group," which successfully changed loot to FFA. Following completely didn't work (they were partied, alone together, standing right next to each other in Org - yes, both from same server).

The leader gets:

Hydra: ValidateName Charactername Thrall
Hydra: IsTrusted Charactername-Thrall true
Hydra: Sending follow command to party
Hydra: SendAddonMessage Follow FOLLOW PARTY


-----------------

Debug info for the toon that's supposed to follow :

Hydra: AddonMessage PARTY Charactername2-Thrall FOLLOW
Hydra: ValidateName Charactername2 Thrall Charactername2-Thrall
Hydra: IsTrusted Charactername2-Thrall true
Hydra: Charactername2-Thrall is too far away to follow! [NOT debug - normal addon message]


On the bright side, you fixed whatever it was that was keeping settings from being saved.

Also, I saw the Assist Module...looks exciting!
Last edited by kittykatmax : 02-23-14 at 10:05 AM.
kittykatmax is offline Report comment to moderator  
Reply With Quote
Old 02-22-14, 02:25 PM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 193
Uploads: 0
Re: Re: The Guild repair button you automated for me in .139

Are both/all of your characters on the same realm? Yes.

Are you using the keybind or the slash command to request your other character(s) follow you? Slash command

Are you in a party or raid group? Tried it in a raid (which normally isn't an issue - was doing BT with hubby); also tried in party with just my two toons.

Are you inside an instance? Noticed in Black Temple, so tried again in Org.

Are there any players in your group who aren't on your trusted list? Wouldn't work with only trusted or in mixed group.


If you reset your settings, did you remember to re-add your other character(s) to your trusted list? I know you have to ask, and yes, of course. lol I also tried removing and re-adding them.

Finally, there is now an options sub-panel for enabling debugging messages. Please use it to enable debugging for the module(s) you are having a problem with, and let me know what debugging messages are shown when an action fails. For example, if following isn't working for you, give me the debugging messages that are shown when you issue a follow command. Screenshots are fine.

I just finished getting everything set up again (changing desired defaults manually in LUA/adding that one "ambiguous" line to the previous version). But I zipped my edited version in a backup, and will experiment with your new version (with debugging enabled) after I get my (likely futile) 14 daily attempts for an ever elusive Love Rocket.
Last edited by kittykatmax : 02-22-14 at 02:28 PM.
kittykatmax is offline Report comment to moderator  
Reply With Quote
Old 02-22-14, 01:52 PM  
acapela
A Cobalt Mageweaver
AddOn Author - Click to view AddOns

Forum posts: 235
File comments: 1286
Uploads: 6
Re: Re: The Guild repair button you automated for me in .139

Originally Posted by Phanx
Are both/all of your characters on the same realm? Are you using the keybind or the slash command to request your other character(s) follow you? Are you in a party or raid group? Are you inside an instance? Are there any players in your group who aren't on your trusted list? If you reset your settings, did you remember to re-add your other character(s) to your trusted list?
with regard to follow/mount/taxi:

two characters, in each other's trusted list, same realm, in a party together, using the slash command ("/followme"), not in an instance, no other characters in the party (trusted or otherwise), reset my settings (i.e. deleted saved variables, reconfigured from scratch), re-established the characters in trusted list.

see my longer post, a few posts before this one, in which i document some changes i made that got mount to work (similar changes got follow to work).

i have also observed quest autoshare/autoaccept to work, at least intermittently, but have not had enough play time to determine whether this feature is more broadly functional. there were some issues related to sharing/accepting, then abandoning, then re-sharing/re-accepting (the quest seems to stay in the "auto-accept" list, such that it is not shared after abandoning); i expect deleting the quest from Hydra's internal list(s), after abandoning, would fix that (haven't had time to play with it).

hope this helps.
__________________
Current author/maintainer of Aloft (the nameplate addon)
http://www.wowinterface.com/download...AloftBeta.html
-----
Zippy said it best: "All life is a BLUR of Republicans and Meat!"
acapela is offline Report comment to moderator  
Reply With Quote
Old 02-22-14, 11:29 AM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3677
File comments: 1860
Uploads: 38
Re: The Guild repair button you automated for me in .139

Originally Posted by acapela
with this most recent version (5.4.7-162), follow/mount do not work for me, quest sharing/abandoning does not work for me, taxi automation does not work for me...
Originally Posted by kittykatmax
I keep getting an error message that the other toon is too far away (when they are standing RIGHT NEXT TO EACH OTHER so following is totally broken - I'm noticing it's using name and server name, which I don't believe it was using before.
I admit I did not test the taxi sharing feature, but I definitely tested the follow, re-follow after combat, mount, dismount, share quests, and abandon quests features just before pushing the release, and each of those features worked flawlessly.

Are both/all of your characters on the same realm? Are you using the keybind or the slash command to request your other character(s) follow you? Are you in a party or raid group? Are you inside an instance? Are there any players in your group who aren't on your trusted list? If you reset your settings, did you remember to re-add your other character(s) to your trusted list?

Finally, there is now an options sub-panel for enabling debugging messages. Please use it to enable debugging for the module(s) you are having a problem with, and let me know what debugging messages are shown when an action fails. For example, if following isn't working for you, give me the debugging messages that are shown when you issue a follow command. Screenshots are fine.

Originally Posted by Donnaterassi
with .151 It stopped working. What I mean is, you could check the box, and close the screen. Then instantly attempt to repair, only to find that you were paying the bill yourself since the box had unchecked again.
.151 is no longer the latest version. Please update. Also, as you can see from multiple other comments on this page, I have been absolutely unable to reproduce any problem with any option saving, so unless you can give me some information that the previous posters did not, there's really nothing I can do about this problem, since it simply does not exist for me.
__________________
Author/maintainer of Grid, PhanxChat, ShieldsUp, and many more.
Troubleshoot an addonTurn any code into an addonMore addon resources
Need help with your code? Post all of your actual code! Attach or paste your files.
Please don’t PM me about addon bugs or code questions. Post a comment or forum thread instead!
Last edited by Phanx : 02-22-14 at 11:30 AM.
Phanx is offline Report comment to moderator  
Reply With Quote
Old 02-22-14, 08:12 AM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 193
Uploads: 0
OK, the single change I made had the following/mounting stuff working fine. I install the version you released yesterday, and now I keep getting an error message that the other toon is too far away (when they are standing RIGHT NEXT TO EACH OTHER) so following is totally broken for me - I'm noticing it's using name and server name, which I don't believe it was using before.

/cry

EDIT: I just went back to the previous version and put the single ambiguous comment in (like I did before) and I'm back in action.
Last edited by kittykatmax : 02-22-14 at 11:23 AM.
kittykatmax is offline Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: