I self-modified RH for beastlords. Took out some of the un-necessary stuff. Pets automatically attack when you attack, and /pet hold when you stop attacking; also sets the pet focus to on when the macro is initialized. My BHtest.mac is my expirimentation macro which includes auto Spiritual ascendance casting when someone sends you a tell with the string "sa" or "SA" in it. It works with a few kinks. Can use normal RH.ini file, but I will include the one I use, I forget if I changed it at all. Was going to clean the code and other stuff cosmetically a little but lost interest.
bhtest.mac requires spell_routines.inc
http://www.base-2.net/~ajax/bh.mac
http://www.base-2.net/~ajax/bhtest.mac
http://www.base-2.net/~ajax/RHSettings.ini
BH, RH modded for beastlords
Moderator: MacroQuest Developers
-
Mr.Studmuffin
- decaying skeleton
- Posts: 2
- Joined: Wed Apr 27, 2005 10:44 pm
-
Mr.Studmuffin
- decaying skeleton
- Posts: 2
- Joined: Wed Apr 27, 2005 10:44 pm
Code
can just view it off the links above
Last edited by Mr.Studmuffin on Sat Apr 30, 2005 3:34 am, edited 1 time in total.
-
A_Druid_00
- Macro Maker Extraordinaire
- Posts: 2378
- Joined: Tue Jul 13, 2004 12:45 pm
- Location: Rolling on the Lawn Farting
Aren't there already like 5000 of these BL mods based off RH? Just seems kind of redundant.
Edit: Oh, and you're exceeding the post limist on the boards. I ran into the same issue when I did RaidDruid. I'd suggest breaking your main macro into a couple .inc files. Like move all the events to BHEvents.inc and just #include it in the main mac.
Edit: Oh, and you're exceeding the post limist on the boards. I ran into the same issue when I did RaidDruid. I'd suggest breaking your main macro into a couple .inc files. Like move all the events to BHEvents.inc and just #include it in the main mac.
[quote]<DigitalMocking> man, A_Druid_00 really does love those long ass if statements
<dont_know_at_all> i don't use his macro because i'm frightened of it[/quote]
[quote][12:45] <dont_know_at_all> never use a macro when you can really fuck up things with a plugin[/quote]
<dont_know_at_all> i don't use his macro because i'm frightened of it[/quote]
[quote][12:45] <dont_know_at_all> never use a macro when you can really fuck up things with a plugin[/quote]
Merlin wrote:seems to be a problem with these 2 lines
/if (${Ini[RHSettings.ini,General,DynamicCloseness].NotEqual[NULL]}) /varset dynclose ${Ini[RHSettings.ini,General,DynamicCloseness]}
/squelch /stick ${closeness}% mpause ${If[${Me.Swimming},uw,]}
You could have made things easier for those trying to help you and actually include what the error was exactly, but oh well! The error on the second line is due to the fact that they changed the name of one of the variables used in the new update.
skyler wrote:Merlin wrote:seems to be a problem with these 2 lines
/if (${Ini[RHSettings.ini,General,DynamicCloseness].NotEqual[NULL]}) /varset dynclose ${Ini[RHSettings.ini,General,DynamicCloseness]}
/squelch /stick ${closeness}% mpause ${If[${Me.Swimming},uw,]}
You could have made things easier for those trying to help you and actually include what the error was exactly, but oh well! The error on the second line is due to the fact that they changed the name of one of the variables used in the new update.
/varset failed, variable 'dynclose' not found
bh.mac@229(Main):/if (${Ini[RHSettings.ini,General,DynamicCloseness].NotEqual[NULL]}) /varset dynclose ${Ini[RHSettings.ini,General,DynamicCloseness]}
