Go to Page... |
Updated: | 09-18-16 02:58 PM |
Created: | 07-29-10 06:15 PM |
Downloads: | 9,198 |
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 |
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax to Your Buddy List |
02-19-14, 04:40 PM | |
|
Discussion of what changed/broke here:
http://us.battle.net/wow/en/forum/topic/11764946863 "With 5.4.7, it seems blizzard now reformats incoming whispers to always include realmname even if same realm. As such, even if you send a whisper to username, their reply will be formated as username-whisperwind for me even though I'm on whisperwind. A silly change, but i can accept it I guess. It becomes trickier though with /who queries on incoming whispers though because /who doesn't accept queries containing -realm for your own realm, it'll return no results. Formats who accepts 1. "/who name" 2. "/who name-connectedrealm" (only if realm is not same as your own but within your connection) if you send "/who name-ownrealm" then it fails. My request is that /who accept -realm for own realm to match blizzards own changes with incoming whispers now force including -realm for all incoming whispers, including own, this way mods don't have to go through ridiculous efforts to strip realm name, send who request, then re-add realm name after who request, when starting a new chat window for an incoming whisper. " http://us.battle.net/wow/en/forum/topic/11765846889 "To elaborate SendAddonMessage() does not require realmname to be specified. if you send a sync to someone, you can send it like you always have. SendAddonMessage will work if I put in "Omegal" or "Omegal-Whisperwind" as whisper target, because /w also works same way. Of course, you DO need to include realm name if they are on a different realm, even if connected realm. However, when user gets that message on CHAT_MSG_ADDON, the sender is now ALWAYS "Omegal-Whisperwind" instead of "Omegal" if they were on whisperwind and "Omegal-Whisperwind" only if they were Not on whisperwind. That is what the change is. Same realm comm RECEIVE now always includes name-realmname format, regardless of whether or not sender is from your own realm Ambiguate is a blizzard function that is designed to automatically smart handle unit names to strip realm off any name from same realm while retaining it for anyone not on same realm so sender = Ambiguate(sender, "none") added to CHAT_MSG_ADDON is pretty much the universal fix to restore pre 5.4.7 syncing behavior for your mod. The reason "none" is used is because it was found to be most reliable when used in other applications involving chat. and CHAT_MSG_ADDON, is very much chat. "none" on ambiguate should always get it right. If you use AceComm then you'd put it in your OnComm function in same manor. "
Last edited by kittykatmax : 02-19-14 at 04:47 PM.
|
|
kittykatmax |
View Public Profile |
Send a private message to kittykatmax |
Find More Posts by kittykatmax |
Add kittykatmax 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 |
Pocahuntess |
View Public Profile |
Send a private message to Pocahuntess |
Find More Posts by Pocahuntess |
Add Pocahuntess to Your Buddy List |
02-11-14, 08:26 PM | |||
|
Re: Re: Re: Re: Re: Bug: Quest Module Broken in .151 Release
If you are 100% sure your addons are all up to date on both computers, and the same problem happens with all other addons disabled, then the only other possibility I can think of is that there is something wrong with your computer's filesystem; completely deleting the saved variables file and letting WoW create a new one may help if that is the issue, though I would think you wouldn't be able to edit the file yourself if it were. I'm not really sure what else I can tell you... if I can't reproduce the problem, there's not much I can do to try to fix it, sorry.
Can you post the contents of your saved variables file (or just the quests section) as it appears after the problem arises? eg. reset, log in, make sure it's working, restart without changing anything, make sure it's not working, and log out (or reload) to save the current settings to disk. (FYI, editing your post doesn't alert me that something new was posted, so I didn't notice your edit until someone else posted a new comment; in the future, you may want to just post a new comment to make sure I see it.)
__________________
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 |
Sunteenxi |
View Public Profile |
Send a private message to Sunteenxi |
Find More Posts by Sunteenxi |
Add Sunteenxi to Your Buddy List |
levelzerozilch |
View Public Profile |
Send a private message to levelzerozilch |
Find More Posts by levelzerozilch |
Add levelzerozilch to Your Buddy List |
01-21-14, 01:23 AM | |||
|
Re: Re: Re: Bug: Quest Module Broken in .151 Release
In Core.lua: Code:
core.L = L core.debug = true -- add this core.modules = {} Code:
module:SetScript("OnEvent", function(f, e, ...) return f[e] and f[e](f, ...) end) module.debug = true -- add this module.defaults = {
__________________
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 : 01-21-14 at 01:30 AM.
|
||
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
01-20-14, 10:51 PM | |
A Kobold Labourer
Forum posts: 0
File comments: 3
Uploads: 0
|
Re: Re: Bug: Quest Module Broken in .151 Release
No need for snark. I like the addon and I'm simply trying to help. I'm new to lua so I'm just applying what I know about python. Yes I misread the module.enabled = enabled. If what I said were true, they would have been flipped.
When I updated to .151, no aspect of the quest module worked while mutliboxing. I have not verified if this bug happens while solo since I don't use Hydra unless I multibox. I wasn't accepting and sharing quests automatically. My alt did not abandon quests that my main did. There were no lua errors or crash reports on the screen. When I replaced the .151 chunk I quoted with the chunk from .139, the Quests module started working again. Maybe I over thought why on the technicalities but it's up now after my tweak. You've misread my enthusiasm to help as an 'imagination of problems.' Edit: spelling & clarification
Last edited by levelzerozilch : 01-20-14 at 10:57 PM.
|
|
levelzerozilch |
View Public Profile |
Send a private message to levelzerozilch |
Find More Posts by levelzerozilch |
Add levelzerozilch to Your Buddy List |
01-20-14, 07:47 PM | |||
|
Re: Bug: Quest Module Broken in .151 Release
Code:
local Refresh = function(module)
I'm not sure what actual problem you are having, since you did not describe one, but I am not having any trouble with the quest module. Quests are automatically picked up and turned in as expected; I am not currently multiboxing, but if the entire module was broken, then pickup and turning wouldn't be working either. If you are having an actual problem (rather than just imagining one based on your misunderstanding of what the code is doing) and you want me to look into it, you're going to have to actually tell me what it is.
__________________
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 : 01-20-14 at 07:49 PM.
|
||
|
Phanx |
View Public Profile |
Send a private message to Phanx |
Find More Posts by Phanx |
Add Phanx to Your Buddy List |
01-20-14, 12:38 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 3
Uploads: 0
|
Bug: Quest Module Broken in .151 Release
Checked out the code changes you made to the latest version (aside from the adjustment for defaults)
I noticed you changed the function module:CheckState() from Lua Code:
to 3 separate functions: Lua Code:
You also used module:Refresh() in line 516 of .151 instead of module:CheckState(). The three function split + switching to a different method seems to be the source of the problem. As a band-aid, I replaced the CheckState() code in .151 to .139's CheckState(). I'm not familiar with WoW's API (this was my first poke at LUA too) so I'm not sure what could be causing the bug. The fact that it fails silently makes it difficult. Edit: I'm beginning to suspect the failure may be due to the new assignment in Core.lua Refresh which was meant to replace the if/else statements in CheckState(): Lua Code:
You're assigning 'Refresh' as a (local) variable to Core rather than defining it as a function. I'm curious, why that is. Also, isn't module.enabled overriding module:CheckState()?
Last edited by levelzerozilch : 01-20-14 at 03:39 PM.
|
|
levelzerozilch |
View Public Profile |
Send a private message to levelzerozilch |
Find More Posts by levelzerozilch |
Add levelzerozilch to Your Buddy List |
01-04-14, 11:10 PM | |
A Kobold Labourer
Forum posts: 0
File comments: 8
Uploads: 0
|
Hi
yes I retrusted the other character. also even rebooted the computer. Thanks |
|
Sunteenxi |
View Public Profile |
Send a private message to Sunteenxi |
Find More Posts by Sunteenxi |
Add Sunteenxi to Your Buddy List |
01-04-14, 05:35 AM | |||
|
I did find an issue with the options checkboxes, though.
__________________
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 |
01-03-14, 05:38 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 8
Uploads: 0
|
Hi Phanx
Auto mounting is working now. except the dismount is not working consistently. I put the debug code back in, but no messages. When the 2nd computer dismounts - my char did not dismount. it did work the other way around. So I removed the addon and cleared saved variables then re-installed. still not dismounting on main computer. dismount works on 2nd computer. *confused* Update: rebooted, removed and re-installed. I am unable to change any options either :S
Last edited by Sunteenxi : 01-03-14 at 05:57 AM.
|
|
Sunteenxi |
View Public Profile |
Send a private message to Sunteenxi |
Find More Posts by Sunteenxi |
Add Sunteenxi to Your Buddy List |
01-03-14, 05:05 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 1
Uploads: 0
|
Version 5.4.2.151 Quest
Hello everyone since this morning update to 5.4.2.151 the leader of my group of hunter can take a quest but the other two toons dont's automaticaly accept like they use to do for the past week.
Can someone tell if something change in the new version or am i doing something wrong somewhere. Thanks Wroak Beside this the best addon ever gg to the author
Last edited by Belgarath1968 : 01-03-14 at 05:06 AM.
|
|
Belgarath1968 |
View Public Profile |
Send a private message to Belgarath1968 |
Find More Posts by Belgarath1968 |
Add Belgarath1968 to Your Buddy List |