Minion Beta! - Help us test our new AddOn updater. Get it now!
Download
(81 Kb)
Download
Updated: 10-16-14 06:28 AM
Pictures
File Info
Compatibility:
Warlords of Draenor Pre-Patch (6.0.2)
Siege of Orgrimmar (5.4)
Updated:10-16-14 06:28 AM
Created:07-29-10 06:15 PM
Downloads:4,108
Favorites:62
MD5:

Hydra - Multibox Leveling Helper

Version: 6.0.2.206
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.

Please DO NOT use comments to report specific problems or request specific features.
Comments are not searchable, bookmarkable, or centralized, and tend to get lost and forgotten quickly. Use the links below to submit a ticket to ensure that your problem or request does not get overlooked or buried.
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
First, 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, Deutsch, 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 6.0.2.206
  • Updated for WoW 6.0
  • Taxi sharing now works immediately for secondary characters who already have the taxi map open
  • Improved dismount detection for noobs who click off auras to dismount
  • Fixed junk selling profit report for stacked items
  • Added alchemy and engineering specialization quests to the ignore list

Version 5.4.8.187
  • Fixed textures overlapping on the "remove name" dropdown when there are no names to remove

Version 5.4.8.186
  • Fixed automatic re-follow after combat
  • Fixed automatic quest abandoning for characters with significant level differences
  • Fixed taxi sharing for characters with different known flight paths
  • More fixes for Blizzard's lazy API inconsistencies

Version 5.4.8.175
  • The dropdown menu for removing trusted names now scrolls when necessary to accomodate users with over 9000 alts
  • [Chat] Fixed the enable checkbox
  • [Group] Promotion requests are now targeted while in a group to avoid spam from non-leader characters
  • [Mount] Fixed a reversion causing comm messages to be incorrectly ignored under certain conditions

Version 5.4.7.169
  • Ambiguate names where necessary to work around annoyingly inconsistent API functions that break when realm names are passed
  • Clear abandoned quests from the accept/accepted lists to they can be automated again later
  • Block automation of the Allegiance to the Aldor/Scryers quests, and the Little Orphan quests in Dalaran

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
Archived Files (11)
File Name
Version
Size
Author
Date
5.4.8.187
88kB
Phanx
07-14-14 08:14 AM
5.4.8.186
87kB
Phanx
06-19-14 01:05 AM
5.4.8.175
87kB
Phanx
06-01-14 09:56 PM
5.4.7.169
83kB
Phanx
05-03-14 05:42 AM
5.4.7.162
80kB
Phanx
02-21-14 01:32 PM
5.4.2.151
72kB
Phanx
01-02-14 07:26 PM
5.4.2.139
71kB
Phanx
12-31-13 06:16 AM
5.4.2.136
71kB
Phanx
12-21-13 10:15 PM
5.4.1.132
71kB
Phanx
11-30-13 06:53 AM
5.2.0.119
71kB
Phanx
05-04-13 06:40 AM
5.1.0.103
68kB
Phanx
12-02-12 04:50 PM


Post A Reply Comment Options
Unread 02-22-14, 12:29 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 4576
File comments: 2094
Uploads: 42
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 12:30 PM.
Phanx is offline Report comment to moderator  
Reply With Quote
Unread 02-22-14, 09:12 AM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 230
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 12:23 PM.
kittykatmax is offline Report comment to moderator  
Reply With Quote
Unread 02-22-14, 08:46 AM  
Donnaterassi
An Aku'mai Servant

Forum posts: 36
File comments: 7
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 is offline Report comment to moderator  
Reply With Quote
Unread 02-21-14, 05:33 PM  
acapela
A Cobalt Mageweaver
AddOn Author - Click to view AddOns

Forum posts: 237
File comments: 1307
Uploads: 6
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
with changes from update1 below, and this change, mount functionality worked for me.

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)
mount functionality is still failing, deeper in Mount:ReceiveAddonMessage(), but that is all i have time for (raid getting ready to start).

Phanx/whoever, i am available to help test whatever you want to test. just let me know.

Originally Posted by Phanx
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...
my "Automation" options save correctly with this most recent version (5.4.7-162). if that changes, based on addon manifest, i will try to get the time to track down which addon(s) might be in conflict.

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.
__________________
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-21-14 at 11:40 PM.
acapela is offline Report comment to moderator  
Reply With Quote
Unread 02-21-14, 03:39 PM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 230
Uploads: 0
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.

Originally Posted by Phanx
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

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...
kittykatmax is offline Report comment to moderator  
Reply With Quote
Unread 02-21-14, 01:34 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 4576
File comments: 2094
Uploads: 42
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

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...
__________________
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
Unread 02-21-14, 01:21 PM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 230
Uploads: 0
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.

Originally Posted by acapela
Originally Posted by kittykatmax
function f:CHAT_MSG_ADDON(prefix, message, channel, sender)
if sender == myName or prefix ~= "Hydra" then return end
sender = Ambiguate(sender, "none")
You are a lifesaver! Don't think I could live without Hydra... hope Phanx gets a chance to look at these things soon.

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).
kittykatmax is offline Report comment to moderator  
Reply With Quote
Unread 02-20-14, 09:37 PM  
acapela
A Cobalt Mageweaver
AddOn Author - Click to view AddOns

Forum posts: 237
File comments: 1307
Uploads: 6
Re: Fix!!!

Originally Posted by kittykatmax
function f:CHAT_MSG_ADDON(prefix, message, channel, sender)
if sender == myName or prefix ~= "Hydra" then return end
sender = Ambiguate(sender, "none")
You are a lifesaver! Don't think I could live without Hydra... hope Phanx gets a chance to look at these things soon.

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).
__________________
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
Unread 02-20-14, 11:56 AM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 230
Uploads: 0
Fix!!!

Use something with a line editor (I like Notepad ++, free), and look for the following in the core.lua file (lines 232 and 233):

function f:CHAT_MSG_ADDON(prefix, message, channel, sender)
if sender == myName or prefix ~= "Hydra" then return end


Insert a line after that so that it reads:

function f:CHAT_MSG_ADDON(prefix, message, channel, sender)
if sender == myName or prefix ~= "Hydra" then return end
sender = Ambiguate(sender, "none")


that new line, "sender = Ambiguate(sender, "none")" will be line 234

The lines after function are/should be indented in the actual file - don't change that!

I tested it and Hydra is working again in terms of following/mounting, etc.. I'm still having issues getting any changes to settings to save, but haven't tried wiping out my saved variables and starting from scratch, which I will try to do later today.
kittykatmax is offline Report comment to moderator  
Reply With Quote
Unread 02-19-14, 04:40 PM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 230
Uploads: 0
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 is offline Report comment to moderator  
Reply With Quote
Unread 02-18-14, 06:46 PM  
kittykatmax
A Deviate Faerie Dragon
 
kittykatmax's Avatar

Forum posts: 16
File comments: 230
Uploads: 0
Since the patch, nothing seems to work. Settings don't save, even though follow was already enabled, my toons don't follow. Mounting doesn't work either. My other multi-box addon I use, Useful Extras (can use with people not in party) is also broken so Blizz presumably changed some code. /sigh
kittykatmax is offline Report comment to moderator  
Reply With Quote
Unread 02-18-14, 04:39 PM  
Pocahuntess
A Kobold Labourer

Forum posts: 0
File comments: 10
Uploads: 0
Settings not being saved...

I too am having an issue with settings not saving for follow enable, refollow after combat, and any of the automation settings.
Pocahuntess is offline Report comment to moderator  
Reply With Quote
Unread 02-11-14, 08:26 PM  
Phanx
A Pyroguard Emberseer
 
Phanx's Avatar
AddOn Author - Click to view AddOns

Forum posts: 4576
File comments: 2094
Uploads: 42
Re: Re: Re: Re: Re: Bug: Quest Module Broken in .151 Release

Originally Posted by Sunteenxi
I am still having a problem changing the automation options on my main computer. i have tried re-installing etc with no difference. I have just changed the lua saved variable file outside the game to change some options.
I just tested every single checkbox in the Automation panel. Changes are saved after switching to another panel and back to Automation, and after closing the Interface Options and reopening it, and after reloading the UI, and after logging out and back in, and after exiting the game and restarting it.

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.

Originally Posted by levelzerozilch
Edit: Looks like after restarting the client, it doesn't function again. I run the settings-reload-command and it works again.
Same goes for you... I simply cannot reproduce this problem. Accepting, turning in, and sharing quests works perfectly on every one of my characters, and for a friend who I had install the addon to test with me remotely. I can disable and enable each feature, or the whole module, in the options panel, and my settings are saved between sessions and apply to the addon's behavior, all exactly as expected.

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.)
__________________
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
Unread 02-11-14, 02:00 AM  
Sunteenxi
A Kobold Labourer

Forum posts: 0
File comments: 7
Uploads: 0
Options not changing

Hi

I am still having a problem changing the automation options on my main computer. i have tried re-installing etc with no difference. I have just changed the lua saved variable file outside the game to change some options.

help?

Regards
Sunteenxi is offline Report comment to moderator  
Reply With Quote
Unread 01-21-14, 05:04 PM  
levelzerozilch
A Kobold Labourer

Forum posts: 0
File comments: 3
Uploads: 0
Re: Re: Re: Re: Bug: Quest Module Broken in .151 Release

Does the problem still happen if you reset your Hydra settings to default? (Fastest way: enter "/run HydraSettings = nil ReloadUI()" in the chat box and hit Enter)
I reset both accounts' settings and the Quest module started functioning again. Sharing, accepting, etc. Seems the 'hard reset' (as it were) kicked out whatever was causing the bug. Maybe a conflict in settings migrating from .139 to .151?

Thanks for the help -- glad it wasn't a complicated fix.

Edit: Looks like after restarting the client, it doesn't function again. I run the settings-reload-command and it works again.
Last edited by levelzerozilch : 01-26-14 at 05:21 AM.
levelzerozilch is offline Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: