Go to Page... |
Updated: | 09-18-16 02:58 PM |
Created: | 07-29-10 06:15 PM |
Downloads: | 9,113 |
Favorites: | 57 |
MD5: |
I am no longer developing or maintaining World of Warcraft addons. I haven't played in years, and don't have the time or interest to continue working on addons for a game I don't play anymore. If you are an addon author interested in continuing one of my addons, please see https://phanx.net/addons/. If you are an addon user, sorry, but there won't be any more fixes or updates from me. |
Scroll down for a full list of features. 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 standard Key Bindings window.Bug Reports & Feature Requests
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.
Post an issue on GitHub (preferred), or post a comment here on WoWInterface. If you are reporting a bug, please read this first and provide as much of the requested information as possible.Language Support
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.Automation
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.
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.Primary character detection:
Whisper forwarding is disabled in non-trusted parties, and there is currently no notification if someone whispers a secondary character in this situation.
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.
Comment Options |
02-23-14, 11:25 PM | |||
|
Re: Quest Functionality
__________________
Retired author of too many addons. Message me if you're interested in taking over one of my addons. Don’t message me about addon bugs or programming questions. |
||
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
02-23-14, 10:58 PM | |
|
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.
__________________
Retired 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 |
View Public Profile |
Send a private message to acapela |
Find More Posts by acapela |
Add acapela to Your Buddy List |
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-23-14, 08:30 PM | |
|
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.
__________________
Retired author of too many addons. Message me if you're interested in taking over one of my addons. Don’t message me about addon bugs or programming questions. |
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
02-23-14, 10:48 AM | |
|
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 11:05 AM.
|
|
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-22-14, 03:25 PM | |
|
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 03:28 PM.
|
|
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-22-14, 02:52 PM | ||
|
Re: Re: The Guild repair button you automated for me in .139
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.
__________________
Retired 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 |
View Public Profile |
Send a private message to acapela |
Find More Posts by acapela |
Add acapela to Your Buddy List |
02-22-14, 12:29 PM | ||||
|
Re: The Guild repair button you automated for me in .139
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.
__________________
Retired author of too many addons. Message me if you're interested in taking over one of my addons. Don’t message me about addon bugs or programming questions.
Last edited by Phanx : 02-22-14 at 12:30 PM.
|
|||
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
02-22-14, 09:12 AM | |
|
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 12:23 PM.
|
|
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-22-14, 08:46 AM | |
An Aku'mai Servant
Forum posts: 36
File comments: 8
Uploads: 0
|
The Guild repair button you automated for me in .139
I meant to tell you before now, but always, it slipped my mind.
I love, love, love it - BUT, 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. I run a metric butt-tonne of add ons, and I didn't want to spend half a day trying to decide which one was not playing nice, so I turned off everything save Hydra, but still had the same issue. I didn't open a ticket and such because it's not such a major work-around, I rolled back to .139, and told Curse to ignore automatic updates for now. I do read the patch notes, so I expect that, at some point, I will have to update, but - for now - I'm good. I love your work.
__________________
Bacon. 'Nuff said. |
|
Donnaterassi |
View Public Profile |
Send a private message to Donnaterassi |
Find More Posts by Donnaterassi |
Add Donnaterassi to Your Buddy List |
02-21-14, 05:33 PM | ||
|
conclusion: someone needs to work through the code, use Ambiguate() everywhere, as needed, or otherwise resolve the "charname-realmname" issue throughout the addon.
looks like most of the subsidiary Blizzard API is equipped to accept simple character names, but not "charname-realmname". i don't how things are supposed to work if characters from different realms have the same character name... i suppose Blizzard would say "you need to pass unitids to these API methods, to disambiguate". so, does hydra need to build/employ some sort of reverse lookup from "charname-realmname" to unitid, and switch to using unitids? bleah... i am also seeing at least some partial/occasional quest autoshare/autoaccept behavior working correctly; there are some glitches, i need more playtime to try to see if i can identify some patterns. update2: the range check in Mount:ReceiveAddonMessage() needs to use "Ambiguate()" as well: Code:
if not UnitIsVisible(Ambiguate(sender, "none")) then return self:Debug("Not mounting because", sender, "is out of range.") end update1: instrumented one of these functions (Mount), discovered that "sender" is being delivered to module:ReceiveAddonMessage() in the form "charname-realmname", and the subsequent UnitInParty() invocation is returning "nil". strangely, UnitInRaid() is returning some sort of garbage... constructs like "type(UnitInParty(sender))" and "tostring(UnitInParty(sender))" are resulting in a Lua error: "bad argument #1... value expected". so, i changed the first few lines of Mount:ReceiveAddonMessage() (in Modules/Mount.lua, starting at line 41) to look like this: Code:
function module:ReceiveAddonMessage(message, channel, sender) if not core:IsTrusted(sender) or not (UnitInParty(Ambiguate(sender, "none")) or (IsInRaid() and UnitInRaid(Ambiguate(sender, "none")))) then return end self:Debug("ReceiveAddonMessage", message, channel, sender) Phanx/whoever, i am available to help test whatever you want to test. just let me know.
however, 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... tried all of this on a fresh install (deleted my saved variables file), disabled everything except Hydra, and added relevant grouped characters to my "trusted" characters first. let me know if you want my shared variables file.
__________________
Retired 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-21-14 at 11:40 PM.
|
|
|
acapela |
View Public Profile |
Send a private message to acapela |
Find More Posts by acapela |
Add acapela to Your Buddy List |
02-21-14, 03:39 PM | ||
|
Thanks! I suspect the settings will magically start working again when one of my other addons gets updated. In the meantime, it's easy enough to change the default options in LUA - even without actually knowing LUA.
|
|
|
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-21-14, 01:34 PM | |
|
Version 5.4.7.162
I have still been unable to reproduce any issues with any options for any module not saving, with any version, and neither have any of the other people I've asked to install the addon and test, so if you're still having this problem, I really don't know what to tell you...
__________________
Retired author of too many addons. Message me if you're interested in taking over one of my addons. Don’t message me about addon bugs or programming questions. |
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
02-21-14, 01:21 PM | |||
|
Re: Re: Fix!!!
I don't know LUA, I'm just brave enough to "fake it 'til I make it" when desperate. lol I wasn't going to do the whole addon testing thingie, but resetting my saved variables didn't help so I just changed the defaults in LUA to be what I wanted.
|
||
|
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-20-14, 09:37 PM | ||
|
Re: Fix!!!
I actually tweaked this slightly: function f:CHAT_MSG_ADDON(prefix, message, channel, sender) sender = Ambiguate(sender, "none") if sender == myName or prefix ~= "Hydra" then return end ...again, works for follow/mount. Have not had quest share/accept work for a while now, have not looked into it. As for options, I found that my "Automation" options do not save, but my "Quest" options do save (have not looked into this either).
__________________
Retired 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 |
View Public Profile |
Send a private message to acapela |
Find More Posts by acapela |
Add acapela to Your Buddy List |