Natural Beastlord Hunter v1.1.9 (Updated 2004-07-11)

wolf5 · Post by **wolf5** » Mon Jul 05, 2004 4:12 pm

Compiling with .Net

-Wolf5

lan · Post by **lan** » Mon Jul 05, 2004 4:31 pm

I'm using VC 6 sp 6

Could that be causing the differences in what works for you and not for me?

Terramantian · Post by **Terramantian** » Mon Jul 05, 2004 4:36 pm

I'm using v6 and it works fine for me

Terramantian · Post by **Terramantian** » Tue Jul 06, 2004 8:47 am

There's another problem I'm getting now that's new with 1.1.1 (for me anyway.) After the mob gets below the force_attack_etc %, whether the bst was attacking or not (letting pet tank), it will not follow the mob. It'll leave autoattack on, and sometimes it'll stay in one place, others it'll run the opposite direction. It's weird.. happens about as frequently as the not-attacking bug did (which I haven't seen again, thanks) but still not a big issue. Just thought I'd report it.

Kambic · Post by **Kambic** » Tue Jul 06, 2004 11:28 am

Got it working for me, had to remove the spell slot numbers from the buff section though (endless error loop).

Sometimes will not target the corpses for looting though, and if slow is resisted it does not recast.

Randomly the macro will end also.

wolf5 · Post by **wolf5** » Tue Jul 06, 2004 3:18 pm

SplitString fixed. You should prob be rid of the error loop u had now.

-Wolf5

Armastevs · Post by **Armastevs** » Tue Jul 06, 2004 4:28 pm

can anyone tell me how i can make this macro, so my bst will just stay in one place and pull mobs that pat to him with slow?

wolf5 · Post by **wolf5** » Tue Jul 06, 2004 4:35 pm

Look at:

Code: Select all

|-- Should we allways pull to the same spot? 
#define PULL_TO_HOMEPOINT True 
|-- What spell should we use to pull ? 
#define PULL_TO_HOME_SPELL_NAME "Blast of Frost" 
|-- What spellgem slot should we use? 
#define PULL_TO_HOME_SPELL_GEM 1 
|-- Should I tell pet to back off while running back. False for those who have /pet hold 
#define PULL_TO_HOME_PETBACKOFF True

Setting "PULL_TO_HOMEPOINT True" will make it pull to homepoint.
Define what spell you want to pull with. I'm currently using Sicken as it is short to cast.

Unless you got "/pet hold" let PULL_TO_HOME_PETBACKOFF be True, so you tell the pet to back off as you run back to it (in case u get hit by a spell or meleed)

-Wolf5

Konk · Post by **Konk** » Wed Jul 07, 2004 2:50 pm

hmmm, I'm in need of a little help, i still cant get it too work. I might have bitten over more than i can chew here

I have a lvl 52 bst.
My current spell setup is:
1) Frost shard
2) Sha's Lethargy
3) Spirit of wolf/Spiritual Radience
4) Healing
5)Aid of Khurenz
6) Yekan's Quickening
7) Spirit of Kashek
8)Spirit of Wind.

I've changed the spellnames in the first part of the code too the ones i have, and the beginning of sub main looks like this now:

Code: Select all

|----------------------------------------------------------------------------
|SUB: Main - Declarations and Initialization
|----------------------------------------------------------------------------
Sub Main
    |Buffs to be kept up on self (max 15) - "Buff" or "Buff|GemSlot"
    /echo Buffs
    /declare MyBuffs[1] string outer 
    /varset MyBuffs[1] "Spiritual Radiance" 
|    /varset MyBuffs[2] "Chloroplast|6" 
|    /varset MyBuffs[3] "Deftness|4" 
|    /varset MyBuffs[4] "Furious Strength|4" 
|    /varset MyBuffs[5] "Spiritual Radiance|3" 
|    /varset MyBuffs[6] "Frenzy|6" 

    |Critical buffs to be kept up on self (max 15) - cast during fight
    /echo Critical buffs
    /declare CritBuffs[1]   string outer 
    /varset CritBuffs[1] "Spirit of Radiance" 

    |Buffs to be kept up on petf (max 15) - "Buff" or "Buff|GemSlot"
    /declare PetBuffs[2] string outer 
    /varset PetBuffs[1] "Yekan's Quickening" 
    /varset PetBuffs[2] "Spirit of Wind" 
|    /varset PetBuffs[3] "Spirit of the Storm|6" 
|    /varset PetBuffs[4] "Deftness|4"

I've just commented out what i didnt want, and changed the lenght of the arrays accordingly. Added the ecco lines too see if the buffing was part of the loop, but those lined dont show more than once.

I still just get the "Target loop 1, Returning too top after downtimework" loop.

What have i done wrong/missed?

I'd apprechiate any help

wolf5 · Post by **wolf5** » Wed Jul 07, 2004 3:21 pm

What version you using? The latest(1.1.4)? Because I added extra debug code there to maybe find exactly that bug you get.

I have experienced the bug once, but did not have the debug code. I have also experienced the bug after a while of non-buggy macroing. I'm pretty sure it has something do to with some /if lines in the downtime subs. Maybe a NULL check that went wrong.

You should now get something like this:

"NewTarget loop"
"1. Critical Buffs Checked"
"2. Mana Checked"
...
"Returning to top after Downtimework"

or

"NewTarget loop"
"Infinity loop? Echoing debug data..."
..some data... ("NULL spellname NULL"?)
...
"Returning to top after Downtimework"

Had some extra debug in the critical buffs section as in case it was the faulty part. Allways after a buff, the code will return to the top to see if there has been change in the status (pet in attack mode), so we can abort buffing and help.

Workaround: Check the "Sub DowntimeWork". Go into each SUB it calls and comment out the lines containing "/return 0".

That will essentially mean you will keep on buffing yourself up even if you get attacked while doing it.

-Wolf5

Konk · Post by **Konk** » Wed Jul 07, 2004 3:34 pm

I was using 1.1.1. Tried 1.1.4 now, worked like a charm. Thank you for a great marcro wolf. Nice work.

Kambic · Post by **Kambic** » Thu Jul 08, 2004 3:16 am

Request:

Could the MQ window echo how many of each looted item has been looted since the macro began? I'd personally like to be able to keep track.

My macro coding abilities don't yet cover item / UI, so would not know where to begin.

wolf5 · Post by **wolf5** » Thu Jul 08, 2004 4:59 am

Shouldn't be to hard to make. Just declare a new integer outer variable each time a new kind of item is looted. Variable name would be Loot_Item_name (where spaces would be removed).

Then increase the counter the next time the same item was found. But then you would need an array to keep track of the variables.

I'll look into it when I have time.

-Wolf5

wolf5 · Post by **wolf5** » Thu Jul 08, 2004 1:45 pm

Thanks to dman for noticing a /return line to much in the code. That is probably why the macro ended prematurely.

Version 1.1.6 is available for download.

-Wolf5

Terramantian · Post by **Terramantian** » Thu Jul 08, 2004 2:30 pm

Looks good... running very well now and very few bugs. there's one more thing I'd like to see. About looting...

Code: Select all

   /if ((!${Cursor.Lore}) && (!${Cursor.NoDrop}) && (${Cursor.Value} >= 1500) && (${Cursor.Stackable})) {
      /autoinv
   } else /if ((${Cursor.Value} >= 7000)  && (!${Cursor.NoDrop})) {
      /autoinv
   }

This is code from an old macro of mine, and it doesn't seem to work anymore. Is there any way you could integrate this idea to your loot sub? Probably replacing the numbers with vars, but you see the idea. Dunno why it's not working, I'll experiment a bit, just wanted to throw this out there.