BattleCry is a set-up and leave mod that can be used for a variety of purposes. Its basic functionality is quite simple: Whenever an action is performed or an event takes place, it will automatically execute one of any number of "cries" that you have previously set up. These cries can be output to any of the standard grouping channels (say, yell, group, raid) as well as emoted.
Special thanks to Tarog and his creation of the mod WarCry, which inspired me to undertake this project.
BattleCry has two main components:
BattleCry_Core: The guts of the addon. This will execute cries based on the rules you've set up for them.
BattleCry_Editor: The editor used for setting up those rules.
For detailed instructions on creating cries and for the most recent test version of the mod, please visit: http://wow.levelonemagic.com
Almost all changes this time around are under the hood. BattleCry has been completely rewritten from scratch to make use of new scripting features recently made available and to decrease on memory used while running BC.
BC is now split into two addons: BC_Core and BC_Editor. BC_Core is required for BC_Editor, but BC_Core can stand alone without the editor (as long as you don't intend on making changes to cries).
This new version is NOT compatible with the old version with the exception of updating your data from the old to the new. To update from old to new, simply enable both old and new and enter the game. Type: "/battlecry update" and it will update your cries to the new version. Now camp and disable and uninstall the old version so that it will not conflict with the new version.
As always, if you encounter any errors don't hesitate to let me know.
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
- +2
- Thumbs Down
- Thumbs Up
Spite-nike saidIs it somehow possible to force the add-on to say one thing when you start a spell, and one when it goes of? Tried adding both, and also adding the on cast one as a exclusive and then put it in a chain but can't seem to get it to work ;_;
- +2
- Thumbs Down
- Thumbs Up
duskhorn saidI was about to ask you (Byterunner) about this feature as well.
I remember you saying that it was on your to-do list, as the "bug" was removed some patches ago. Some of us are really looking forward to such an update to BC.
On a sidenote, SCT added a great opition for its events regarding the number of charges on a buff. If you havn't already, I strongly suggest you have a look at it. If it's simple to re-produce it would surely make creating set-number-of-charges specific events a lot easier :J
Keep up the good work!
- +0
- Thumbs Down
- Thumbs Up
Mion saidIt's just me or all arguments can't be used anymore in our cry, such as $e4?
- +0
- Thumbs Down
- Thumbs Up
mook saidHiya!
*Awesome* AddOn - just wanted to mention that if you click the huge 'DOWNLOAD' button at the top of the page, Curse tries to download BattleCry 3.0 ... to get the latest version, 3.02, you have to click on 3.02 from the 'Downloads' section.
Not a huge deal but thought you'd want to know - it's interfering with some auto-updaters (I only noticed because jWowUpdater wanted to "update" my BattleCry 3.02 to 3.0).
- +0
- Thumbs Down
- Thumbs Up
MGDarkbleed saidOh another thing I noticed:
Using the string $pp on a female target says "hers" instead of "her." I tend to use this string a lot in the context of, "/e slips behind the unsuspecting $ct and slides her dagger quickly and deeply across $pp neck!" Now if the target is a dude, it comes out all right but if it is a female it reads, "Purloinia slips behind the unsuspecting Humanoid and slides her dagger quickly and deeply across hers neck!" Which looks silly. I know you can use $po to get "her," but then if the target happens to be a male, it would read "Purloinia slips behind the unsuspecting Humanoid and slides her dagger quickly and deeply across him neck!" which looks really dorky. Honestly, I've created at least twenty cries for all of my abilities and I've never run across a situation where I wanted a feminine possessive pronoun that says "hers" instead of "her." Just giving you my personal opinion in this area... I think in the majority of emotes you would want "her" instead of "hers."
Again, this is the greatest mod of its kind out there, and this was just an observation from an avid fan.
- +0
- Thumbs Down
- Thumbs Up
MGDarkbleed saidOUTSTANDING mod, Byterunner. I've used several different types of mods over the years for adding flavor speech and emotes to combat and this one is by far the best. Just wanted to make a couple of observations and ask a question. First, I had the crash issue as well, and as previously mentioned it was likely caused by still having data from a previous version loaded. Simply deleting the old mod apparently isn't enough - I had to wipe my WTF folder to fix the crash issue. If anyone else is having crashes they suspect are being caused by Battlecry, I'd recommend doing this as it worked great for me.
The variables are outstanding! The major problem other mods have is that you can't make your character say something different for different enemies. My rogue, for example, will emote something to the effect of making a grab for a wallet while simultaneously stabbing the %t in the back! when using Ambush on a humanoid, and when using it on a beast she will emote grabbing the hapless %t by the hide and begins skinning it before it is even dead! So simple to do, just add in "Target $ct = Beast" or "Target $ct = Humanoid"
The chains are incredible, as well. I've created some incredibly complex little RP exchanges between my warlock and his minions that can trigger and I know exactly what to do next in combat to make the rest of the story happen. For example, if my succubus is out and a particular shadowbolt cry procs, (with the condition "Pet $nm = Kal'thun" so this one only procs when she is out), it sets off a whole chain of comical interactions between my warlock and the succubus, with the chain ending when I cast demonic sacrifice and kill her for being insolent and then her promising to behave this time when I resummon her. As you can see, the possibilities are nearly limitless with this mod, and fr that reason it is clearly the best flavor speech/emote mod out there.
I'm running into one problem: I'm trying to make a cry that executes when humanoid targets who are below 20% health are fired at with a ranged weapon. The cry is basically one that says something to the effect of "Oh no you don't!" as they attempt to run away out of melee range. I'm unable to get the variable to be understood, even though by all appearances it ought to work! I've set the cry to exclusive and to fire at 100%, and it simply doesn't cry at all when those conditions are met. However, it I shoot at a target that is at full health to pull it, it will go ahead and fire off one of the other cries I have for shoot that doesn't have the "Target $hp =< 20" condition enabled. Is this a known bug or am I not entering the condition properly?
- +0
- Thumbs Down
- Thumbs Up
Mion saidCan the old Slay Hostile could work again with UNIT_DIED combined with PARTY_KILL ?
- +0
- Thumbs Down
- Thumbs Up
cocchettino saidGreat addon!! But I've 2 questions:
-Is there a way to put the name of the spell casted in the cry? Basically, I want to say "PLAYER NAME/CLASS is now buffed with SPELL NAME"
-When I'm ressing someone who has released the spirit, the variable $nm gives me "unknown". Is there a way to avoid that?
- +0
- Thumbs Down
- Thumbs Up
MGDarkbleed saidSince cries are set specific to abilities, you don't need a variable to determine the spell name. Simply write the spell name into the cry. You wouldn't need to worry about the wrong one popping up because a Blessing of Wisdom cry will only do the cries listed under that ability, and a Blessing of Might cry will only do the cries listed under that ability.
A possible work-around for your rezzing issue would be to use %t instead of $nm, and be sure that the person you are rezzing is also your current target.
- +0
- Thumbs Down
- Thumbs Up
noblesteel saidMy suggestion is you add "Role Play" to the search tag. It took me a while to stumble across this one, and it looks like a great replacement for RPHelper.
- +0
- Thumbs Down
- Thumbs Up
Aur saidFull Edit: Seems if you enter /bc off just once, it doesn't always shut off, but entering it twice, seems to make sure it is off. :)
- +0
- Thumbs Down
- Thumbs Up
kasumifm saidByte this is a very good mod, but I got to tell you, the hit/crit melee scripts are incorrect. I've been trying to solve this on any rp proc mod I could find, everyone I've come across since 2.4 does not have the correct wording to match the combat log:
'Kasumi's melee swing hits Forest Spider for 832 Physical. (Critical)'
I was able to get the event with your watcher, but it has 14 arguments, and I have no clue where/what are the important ones.
I doubt it's me because RPHELPER also has the same issue, 2.4 just broke melee/crit strikes, because the wording in the combat logged was changed.
If memory serves the old method was 'your melee crit rabbit for 832. (physical)'
'your melee hit rabbit for 832. (physical).
http://forums.worldofwarcraft.com/thread.html?topicId=6286800779&sid=1
I have started a discussion in the wow forums trying to come to some conclusion. Honestly I like battlecry already better , just looking it over because of the cooldown option you have in there, but I'm having the same results as cross38.
- +0
- Thumbs Down
- Thumbs Up
Byterunner saidI've noticed some strange behavior as I've looked in to this issue more. If you have more than one event watch for the COMBAT_LOG_EVENT_UNFILTERED, there is a good chance that your cry will not execute. I'm trying to figure out why exactly this is, but I've found that deleting the "You Hit (Melee)" event watch causes my crit events to trigger properly. I'll keep you informed for a fix for this.
- +1
- Thumbs Down
- Thumbs Up
Mion saidFor now a normal melee will triggera cry, even if it's a critical, so I propose to put a amount variable for exemple >= 2000 (depending for how much you crit usually) and you'll have a "working" critical cry, at least it work for me. So far everything except critical and on kill (the Slay Hostile of old version) work for me. Only attempt that actually worked a bit was on player_honor_change or so-called condition, was firing my cry 3 time in a row for each honor kill I got :'(. Byterunner did an amazing work thought! I took a look at the API and was near to clueless, seem many addon got screwed with the new COMBAT_LOG_EVENT so it might take some time and alot of effort to make addons work again, let's help Byterunner on the project! I personally started to read the new API trying to learn how to code a bit ( http://www.wowwiki.com/API_COMBAT_LOG_EVENT and http://www.wowwiki.com/Events_C_(Cancel,_Character,_Chat,_Cinematic,_Clear,_Close,_Confirm,_Corpse,_Craft,_Current,_Cursor,_CVar) ), mainly cause I want to fix SoundTrack addon myself if Morricone dosnt continu the project, everything seem linked to the COMBAT_LOG_EVENT anyway. so if I find something that could help I'll surely post it!
- +1
- Thumbs Down
- Thumbs Up
Byterunner saidThanks for the kind words, Mion. You're right, 2.4 broke a lot of stuff. If we were wise, us mod authors would make better use of the PTR to have mods ready when the patches hit. But nobody said we were wise, only addicted...
Anyway, it looks like the issue I'm trying to sort out right now is that you can only have one event per Prefix/Suffix combination. If it looks at the first watch for a combo and it fails, it skips all the rest of the watches for that combo, which is why You Hit (Melee) and You Crit (Melee) don't work together. :( I'm trying to figure out the best way around this now.
I've also adjusted the UI slightly on several of the elements so that you can choose between true or false (for things like critical) rather than having to type in specific numbers and the like. This seems to be working alright, but I haven't had a tremendous amount of time to test it. Once I'm satisfied that it is stable I'll post a new version.
- +0
- Thumbs Down
- Thumbs Up
kasumifm saidthanks for your effort on this mod byte, your temp fix worked great. The main reason I want crys on crit's are because they are less frequent, and makes it look less like spam. I tend to apply the % pretty low, and the cooldown feature helps also.
Good idea about the true and false conditions.
- +1
- Thumbs Down
- Thumbs Up
Mion saidNo worry! Of course we love to have ours mods working at every patchs but mods authors give thier freetime and knowledge for others players and you must have our respect for that, reguardless of the outcome. Also understandable to not be ready while testing on a PTR, sicne it's a "beta" version of WoW, even if it's rare, some stuffs can be change without much notice and bam! All the work must be one again. I was thinking about the true/false and it's a wonderful idea! Somes abilities in WoW are triggered by criticals (Vengeance for paladins, a trinket that "store" uncritical util you land a critical, etc) and thought there is a way to "detect" what trigger it, might be useful for that cry. Most macros since 2,0 work with "true/false" so it's logical to look that way. For exemple a /cast [stance:2,equipped:shield]Shield Bash;[stance:3]Pummel would be kinda of: if Stance:2 and Equipped shield true then CastSpellByName Sield Bash else if stance:3 CastSpellByName Pummel. Ok isnt the exact macro but you catch my drift; if the 1st condition is true it'll execute, if it's false it'll do the next in line. I feel kinda bad, I want to help or contribute, even a little but once again I feel clueless on how it would work. Macros is one thing, coding is another.
- +0
- Thumbs Down
- Thumbs Up
Fanty saidI absolutely love this addon.
However I had trouble with several things even in 2.3 times.
Hit, crit and kill didnt work for me (German client) in the 2.3 Version of WOW aswell. But I found a way to make them work with the eventwatcher.
Now in 2.4, I still cannot make things like hit, crit or kill work at all.
And I am confused with the eventwatcher now.
Also, I used to have cries for events like the effect that critical firespells make the target start to burn, giving it a DOT. (in 2.3 I found out how to do this with the eventfinder) now in 2.4 I seem too stupid to make it work. :(
I also had comments special for damage caused by falling. I cannot get this to work aswell now.
I would like some kind of workshops fpr these kind of things. ^__^D
By fanty at 2006-07-04
- +0
- Thumbs Down
- Thumbs Up
Cross38 saidI downloaded it fine, and put in what I thought was the right text for doing physical crits, hit test and it worked fine, went up to a mob, got a crit... and nothing. I got frequency up to 100% and its still not working.
I am using the following script..
/run s={"Oh thats gotta hurt!"};SendChatMessage(s[math.random(getn(s))],"SAY")
Is that the right script if I want to have something say when I crit someone/something?
- +0
- Thumbs Down
- Thumbs Up
Byterunner saidYou don't need to put scripts in to BattleCry. Just put "Oh that's gotta hurt!" into a cry and save it.
Here's how to get exactly what you've described above:
Step 1: Download and install version 3.02 if you haven't already. If you open BattleCry and it doesn't say 3.02 at the top of the editor you don't have the most recent version.
This first part is already done for you in a pre-made Event Watch called "You Crit (Melee)" if you have 3.02 and follow the instructions for resetting your event watches in a post below...
Go to Events tab.
Select Available Event: COMBAT_LOG_EVENT_UNFILTERED
Select Prefix: Swing
Select Suffix: Damage
Click "sourceName" in the list under prefix/suffix.
Choose test: ==
Enter your character's name in the value box.
Click Save next to the value box.
Click "critical" in the list under prefix/suffix.
Choose test: ==
Enter 1 in the value box.
Click Save next to the value box.
Enter a name for this event watch in the Watch Name box.
Click Save under the Watch Name box.
From here is how you set up your cry to execute on the event just set up.
Click the Cries tab.
Choose the Category: Events
Choose the Action: You Crit (Melee) or whatever you named it just above.
Enter a Cry Name: "Hurt"
Enter a Cry Text: "Oh, that's gotta hurt!"
Slide the Frequency % slider to 100.
Click Save in the bottom-right.
This works exactly right every time for me.
If you want to say more than just that one line, just save them under different names. BattleCry will automatically pick one at random. To put a random choice in your cry itself is double the work since it's already doing a random to pick that one (not to mention a whole bunch more typing!).