- Registered User
Member for 14 years, 8 months, and 24 days
Last active Fri, Oct, 4 2013 14:29:42
- 0 Followers
- 241 Total Posts
- 0 Thanks
Oct 4, 2006Some time ago I wrote Q it! for things like that. I have great plans for it (in-game scripting for conditions, better interface, and so on, converting to Ace2) but haven't found the time to do this yet, as this would require a major rework, actually, a complete rewrite.Posted in: Addon Ideas
Oct 2, 2006Posted in: Addon IdeasQuote from wobin »
Would the ManyBag camp mind clicking on a intermediary screen to determine which categories to open? While the OneBag camp need only specify that all are open at once?
Maybe via a dropdown, yes. Or the design from Indy's screenshot.
Oct 1, 2006Maybe I'm particular stingy about UI space, but one reason I don't like the "One Big Bag" idea is that I am forced to bring up an obstructive big window when I just want to check on my supply on health potions. I rather like to have my herbalism bag open while farming, so I don't need any fancy addon to track the amount of dreamfoil I have gathered so far. Get it?Posted in: Addon Ideas
I think it would be best if the addon leaves the choice to the user. By simply allowing her/him to set the size of each bag (it'd be terrific if there was some "automatic" size like ABP). So everyone can customize it to fit personal flavors.
Oct 1, 2006I am currently using "Advanced Bags Plus" to organize my inventory. I would really like to see something similar, but with less impact on performance. Using preset categories (consumables, cloth armor, leatherworking, etc) combined with easy-to-setup custom filters by simply shift-dragging onto bags is heavenly. The downside is - I have to have about a dozen bag icons on the screen. A tabbed design with one single bagbutton to bring the window up would be much better.Posted in: Addon Ideas
- Filter setup similar to Advanced Bags Plus, i.e. using Periodic Table for predefined filters for consumables, trade skill items, armor, etc
- One single button to bring up the inventory. Nameable tabs to define additional "virtual bags". Size (rows*columns) customizable (one big window for OneBag fans, several small virtual bags for the Advanced Bags Plus fans)
- FuBar plugin to even get rid of this single button :-)
That's what I think. In the end, it's you who has to decide which way to go. Choose the design you think is best (or easiest to code) and go for it. When the first version works, there will still be time to implement alternative designs along with options to switch.
Sep 22, 2006I have never used backdrops without a background file and a tilesize specified. Are you sure the edge will display if there is no background? Also, calling "Show" on this particular frame won't do anything. By specifying "hidden='false'", it should show up right on UI loading time.Posted in: Lua Code Discussion
Sep 22, 2006Have a look atPosted in: Lua Code Discussion
If there is something like "Could not parse HealAssist.xml", then you have a syntax error in the xml file. Can't see any though.
Next you should try printing something into the chat window in your HealAssist_OnLoad function so you can see if HealAssist_OnLoad is actually called.
Last... are you using Ace1 or Ace2? If Ace2, try HealAssist:OnLoad instead of the underscore.
Sep 15, 2006Posted in: General ChatQuote from bonedancer-sin »
I'm not a 'published' developer but a few in my guild and I tear things apart figure out how they work and make our own stuff... isnt that how many get started? With the closed SVN that whole process feels slower not to mention it limits WHAT you can get at.
For looking at other addon's source code, you don't need full access to the SVN. After all, you can still download the latest revisions from http://svn.wowace.com/files/ . Clad already mentioned he tries to give non-developers access to the branches, and once he manages this, your access is not limited anymore. And actually, it's faster because updating via Tort (or similar) is slower than downloading the zips.
Sep 12, 2006I am really tempted to try and create some kind of "Generosis" with plugins for the classes. But at the moment, I am busy elsewhere (Druidcom, some other addon and next semester is coming soon). When I feel like diving into this and nobody has taken over by then, I will let you know.Posted in: Addon Ideas
Sep 12, 2006Please use the Druidcom Wiki Talkpage for further discussionPosted in: General AddOns
Sep 10, 2006@Target discussion:Posted in: Libraries
I'm not sure about this, but don't have all spells which require a target a range? I mean, spells that can only be cast on the player don't have a range in their tooltip. Even those spells with seemingly unlimited range like mind vision do have a line in the tooltip saying "50000y range" (not sure about warlocks and their porting spell though). If this is true, why not scan the tooltip for a range, and if it's not there, it is a self-targetting spell.
If I'm wrong, just forget what I wrote.
Sep 8, 2006OK, folks, I reworked the code until I myself didn't recognize it. It's more generic now, meaning it should be little effort to adapt it to other classes abilities (think of taunt rotation for warriors). It's also more robust, at least I hope so. But this rework also means I probably broke some things that worked before. The good news is that there was so little that worked before that I probably did'nt break something at all. ;-)Posted in: General AddOns
Another thing I made major changes to are the cooldown timers. Although there are three timers per druid now (instead of one global timer and one per druid), they should be much more efficient now as they 'tick' less frequently.
I recommend deleting the Druidcom folder and you should probably remove the file
Druidcom.lua.bakin the same directory prior to installing the new version.
Now, I really need your help. I don't have a druid character myself and most of my druid friends don't have much time to help me testing. So I have to rely on you to find everything that doesn't work yet. I will check this thread and the Flyspray bugtracker several times a day (I've got plenty of time these days, yay to semester break!). I want the current version to do it's job before starting to implement features on the Todo-list, so do everything I don't expect of the user. Make requests like mad, let a druid leave the raid, try to break the addon in every way you can imagine. When you discovered something, please post it here or in Flyspray with a description as detailled as possible:
- When did the error occur (when you did something, after something happened, etc)?
- If there was an error message, please include it in the post (screenshot or by simply typing it)
- If there was no error message, what happened (snycing didn't work, druid list wasn't updated) and especially, did the error go away after reloading the UI ("/console reloadui")?
- Which revision were you using? If you downloaded it via the "plain download" link, look into your addon folder for a file named "changelog-Druidcom.txt". The revision number I would like to know is the first number "r1XXXXX"
Thanks in advance!
Sep 6, 2006Glad to hear you like it. :-)Posted in: General AddOns
At the moment, there is no "Druidcom leader" (yet). Everyone with an 'A' or 'L' in the raid has the same rights. This also includes the automatic updates. I don't know which revision you were using, but there should be a slider for the Update Interval in the config dropdown. Set it to '0' for everyone but one person and you should be fine. I recognize this is inconvenient, so I will try and implement some kind of automatic mechanism to determine one person who broadcasts update requests regularly.
As for the mana threshold, I noticed that too. I replaced the "<" with a "<=" in some revision, don't remember which one. This should enable you to select people with 100% mana when the threshold is at 100%.
Scaling is another thing that will take some time to figure out. But I know just too well that healers sometimes wish to be able to use two screens, so it's scheduled right after the bugfixes and polishing.
Again, thanks for the feedback :-D
Sep 5, 2006Thanks for the support. I was busy bugsquashing this evening and most of the functionality should work.Posted in: General AddOns
EDIT: Bug- and Todolist moved to first post
Sep 5, 2006The leader of the druids in our raid needed an addon to have an overview over the Innervate and Rebirth cooldowns of the druids in the raid and wasn't quite content with the existing ones. So I made him one.Posted in: General AddOns
The Druidcom Interface lists all druids in the raid, coloring the names and subgroupnumbers according to their status
- Green: Everything ok
- Yellow: Out of range
- Red: Dead
- Blue: No Druidcom found
- Gray: Offline
Next to the name of each druid are two buttons. One for Innervate, one for Rebirth. If the druid has already sent his cooldown status, the buttons will display these cooldowns. If nothing was received yet, they will show a "?".
If you are leader of the raid or promoted, right-clicking one of the buttons will bring up a dropdown menu to select other players in the raid, sorted by class. You may customize which classes you want to see (warriors and rogues can only be shown in the Rebirth menu). In the Innervate dropdown, only people with mana below a customizable threshold are displayed, in the Rebirth dropdown, only dead people are displayed. Clicking one of these names will send a request to the druid the button belongs to, to innervate / resurrect the respective player.
On receiving a request, a dialog will pop up to choose whether the request shall be fulfilled immediately (clicking the OK Button will innervate / resurrect the player the dialog refers to, while keeping the current target) or recline it. If the requested target is innervated / resurrected, the button in Druidcom will flash green for every druid using Druidcom. If (within 20 seconds) a different target is innervated / resurrected, the button will flash yellow. If nothing is done (reclined or ignored the request), the button will flash red.
For the cooldown information to be as reliable as possible, every leader/promoted has a "Refresh" button. Upon clicking it, alle Druidcom users will send an update about their cooldowns. Optionally, an automatic update will be requested every 10 Seconds (interval customizable).
Druidcom may be obtained via the SVN or plain download
Please report bugs either here or (preferably) in the Trac Bugtracker
What doesn't work yet:
- Updates not yet "automatic enough" (raid leaving / quitting, no update immediately after casting, etc)
On the Todo-List:
- Cutting down chat traffic by determination of one single druid leader
- Scaling of window
- Mouseover-Tooltips for exact cooldowns in mm:ss format
- French localization (help greatly appreciated!)
PS: Screenshots will follow, don't worry
- To post a comment, please login or register a new account.