It will always stay a simple companion. Though it will grow to have a helpfulness outside just emote and speech for druids. Suggestions always welcome. Hopefully those who download this will find some use for it with their wonderful druid =)

Please understand that this isn't the final product. It is a idea in progress. If its not to where you'd like yet. Please wait for a later release. Otherwise please download and give me feedback and suggestions. And if you can code feel free to bonk me on the head to fix something -heh- And most of all thank you =)

Quick Start:

Currently there are no slash commands or GUI. I will add these ASAP (More focused on cleaning up the current code.). For now you must edit the file 'core.lua' in the folder 'Druidia'.

Things you can change :

• BTA = 1

• BT ability announce 1-true 0-false (1-processes the ability through as Battle Text. 2-process the ability as chat emote)

• MSBT = 1

• 1-MSBT 0-Default (Battle Text processor. 1 uses the add-on MSBT. 0 uses the Blizzard default.)

Within the function Druidia:UPDATE_SHAPESHIFT_FORM() you can change the text displayed on form changes.

Known Issues:

• Changing form code affected the enter world form check. Even though I just pushed the same coding into a side function. That later gets called in Druidia:UPDATE_SHAPESHIFT_FORM(). I may be missing a simple fix to how to resolve the issue.

Druidia is a simple add-on that will support :

• Adjustable form timers & random speech selection

• A selectable GUI interface for customized form & ability reactions in emotes or speech.

• Sound database for simple actions for things such as purring (Wants to generate sound files as close to Blizzard's. So it will sound like it fits in the game.)

• Integration into other add-ons for form & ability reactions in emotes or speech, etc.

• It will also note data on reagent needs and purchase from npc's.

• It will also support reactions to the chosen spec's when abilities proc & set bonuses.

Side thoughts :

• Would DBM support some sort of hook to allow HoT display? Or would I have to create my own bars? -Thinks & will research- I do know that DBM supports the creation of DBM mods. However I want to create Druidia to pipe data straight to DBM to display. If it doesn't I'll have to code a simple DBM mod to bridge this gap.

• Creation of dynamic macros based on chosen forms highest heal or dps output. -If that's possible & how hard will that be-

Soon To Come :

• Lots to still code into Druidia. Main focus will be to complete the integration of noted useful abilities for all specs. I play a Bear and Tree. So not so sure what key abilities a good Kitty or Boomy uses. Help there would be appreciated for marking. Will look into what is needed to pipe the chat data to a few popular Combat Text Add-Ons, along with the Blizzard default.

• Could use someone who knows how to do nice sound recordings to record a few new sounds for Druidia. One's that seem to fit into the game. Not some internet hunt type sound file. Mainly to add to the sound database for : Cat, Bear

• Work on adding output for spec procs (will add set bonus/trinket procs at another date).

Progress To Next Release :

• Form speech : 100%
• Various customizable timers : 100%
• Battle Text option for speech : 100%
• Ability speech for all forms : 10%
• Form/Ability random speech : 0%
• Integration of timers beyond forms : 0%
• Proc speech/DBM Timers : 0%
• Add slash commands : 0%
• Database : 0%

Other Notes :

• Ace3 support (partially still have a lot to do there)
• Redid the structure to event calls to exist within a single function. Been hearing some say a function for each event is nice. Though after I see it. I think its messy =P.
• In combat form speech mute

In truth the next release will take me some time to do. Change structure to Ace3, cleaning up code, trying to figure out how to fix the errors at times with form speech. I will try and release it ASAP. However I am hoping this release will be the more "I like it so far" version. So that I can then go on to code the bar timers for DBM. And eventually structure will change there also. With lua's being for the different features along with a core.