Item find barb leecher

[mayphilc]

Does anyone know if you can run a bo Horker with this to leech runs?

[DarkHorseDre]

sure. if you add the find item skill the bot will detect corpses and use it IIRC from last ladder. just watch it run tho, as it tends to be slow for some reason and can lag behind group..

[mayphilc]

sure. if you add the find item skill the bot will detect corpses and use it IIRC from last ladder. just watch it run tho, as it tends to be slow for some reason and can lag behind group..

good to know, how do i add the skill?

[DarkHorseDre]

I meant if you allocate a skill point to that skill, the bot will use it.

you also need to configure: Config.FindItem = true; :)

[mayphilc]

I meant if you allocate a skill point to that skill, the bot will use it.

you also need to configure: Config.FindItem = true; :)

ok so i got it all set up i think, but the barb just sits in town after BO and doesnt enter the leaders portals when the leader says "clearlevel"

is there something im supposed to do with the barbs config? I dont have any scripts set to true perhaps thats the issue, i just figured since i enabled team mf it would follow the leader

[DarkHorseDre]

what does the console say? he's probably running another script like mfhelper etc.

check the console to see which script its running (in yellow text)

[mayphilc]

what does the console say? he's probably running another script like mfhelper etc.

check the console to see which script its running (in yellow text)

im dumb i had bo setting on wait and it made him sit in town. So its working he follows my 2 sorcs through pit 2, andy, meph, chaos and baal. only issue i have is that he is so badly geared that i cant really have him getting all up in the mix yet id prefer he just stays back and buffs the party/ debuffs enemies and item finds.

I set his pickit range to a low value and the sorcs are at a high value and that stops him from wandering too much the sorcs can always jump around with tele and alot of fcr. item find is slow i see what you were talking about, im going to keep my eyes out for a fcr/frw circ, fcr amy and rings and see where else i can fit some more so he can cast find item and eventually tele faster hopefully that will help. until he has last wish and ebotd with enigma i dont really want him tanking too much

[DarkHorseDre]

cool. problem isnt fcr - if you play manually you can do it fast but kolton is slow. I only used it a bit but seems some interaction problem. when theres a lot of bodies, he'll be stuck there for ages and your team wont get BO. if you cant tweak it, then you may have to disable, unless you dont mind how he does it..

[mayphilc]

cool. problem isnt fcr - if you play manually you can do it fast but kolton is slow. I only used it a bit but seems some interaction problem. when theres a lot of bodies, he'll be stuck there for ages and your team wont get BO. if you cant tweak it, then you may have to disable, unless you dont mind how he does it..

im stabbing in the dark then but consider this possibility, something youd be better at figuring out than i would be but in the past ive noticed these bots are pieced together byy several different people and id venture to guess that whoever wrote the necro sumon spell script did not write the barb find item code because other than firing a pickit its the same concept really the spell should be cast on useable corpses within range of the caster. The necro scripting is perfect maybe "we" can compare how it handles the 2 spells and adopt something from the necro to fire item find more efficiently?

[DarkHorseDre]

haha yeah and then some! Kolton has a past I don't fully understand but suffice to say the sources vary (and are indicated in the code)

I think the problem is in the literal way the bot casts/fails in casting finditem. When I tried it the barb stood around most of the time not actually casting. god knows what he's doing. prolly searching for his wallet, idk.

watch your bot - that's my number 1 advice from my novice levels: observation tells you a lot.

that said, my code is old as updating/merging is painful, so there's a chance it has improved.

*if its slow, pause the bot, take over and cast find items - should be as you expect, meaning kolton has an issue

[mayphilc]

im pretty sure i just figured it out. the bot tries to cast find item on corspes that are within range for thhe bot to see but not for the spell to be cast. you have to ve closer to a corspe for this skill compared too corpse explosion that has a longer range.

line 202 in Barbarian.js reads: if (getDistance(me, corpse) > 30 || checkCollision(me, corpse, 0x1)) {

change that to:

if (getDistance(me, corpse) > 5 || checkCollision(me, corpse, 0x1)) {

now he runs u to corpses before he casts find item

test it out make sure im not missing something so far seems to be working

[mayphilc]

haha yeah and then some! Kolton has a past I don't fully understand but suffice to say the sources vary (and are indicated in the code)

I think the problem is in the literal way the bot casts/fails in casting finditem. When I tried it the barb stood around most of the time not actually casting. god knows what he's doing. prolly searching for his wallet, idk.

watch your bot - that's my number 1 advice from my novice levels: observation tells you a lot.

that said, my code is old as updating/merging is painful, so there's a chance it has improved.

*if its slow, pause the bot, take over and cast find items - should be as you expect, meaning kolton has an issue

ok yeah what i posted fixes it, the only thing i dont like is if a ghost dies over the river in chaos he will try to get to it for a bit before moving on, i cant find where to make him give up trying the corspe faster that must be another timer somewhere else

[DarkHorseDre]

nice, i'll give it a try when i get a chance.

uff I'm not sure of the code for inaccessible areas. I know theres a max attack count (300). check attack.js as i know it tries to skip those that are stray..

[knarglegarth]

im pretty sure i just figured it out. the bot tries to cast find item on corspes that are within range for thhe bot to see but not for the spell to be cast. you have to ve closer to a corspe for this skill compared too corpse explosion that has a longer range.

line 202 in Barbarian.js reads: if (getDistance(me, corpse) > 30 || checkCollision(me, corpse, 0x1)) {

change that to:

if (getDistance(me, corpse) > 5 || checkCollision(me, corpse, 0x1)) {

now he runs u to corpses before he casts find item

test it out make sure im not missing something so far seems to be working

my barbarian.js file doesn't have any of this info in it?

[DarkHorseDre]

@knarglegarth he means the barb attack file with same name

https://github.com/kolton/d2bot-with-kolbot/blob/master/d2bs/kolbot/libs/common/Attacks/Barbarian.js

[knarglegarth]

@knarglegarth he means the barb attack file with same name

https://github.com/kolton/d2bot-with-kolbot/blob/master/d2bs/kolbot/libs/common/Attacks/Barbarian.js

Found it! Thank you a ton. I was looking at barbarian.js under normal config folder.

[Mahazael]

im pretty sure i just figured it out. the bot tries to cast find item on corspes that are within range for thhe bot to see but not for the spell to be cast. you have to ve closer to a corspe for this skill compared too corpse explosion that has a longer range.

line 202 in Barbarian.js reads: if (getDistance(me, corpse) > 30 || checkCollision(me, corpse, 0x1)) {

change that to:

if (getDistance(me, corpse) > 5 || checkCollision(me, corpse, 0x1)) {

now he runs u to corpses before he casts find item

test it out make sure im not missing something so far seems to be working

+1 to this! Worked very good for me! I had an experience similar to your (bo barb leecher with find item :D ) and tried also another thing: I was using AutoBaal = true with support longRangeSupport = true... but the barb wasn't supporting at all! So I tried to look at the code of "longRangeSupport" and discovered there is a switch on classid with case 4 (barb right?) empty. So I tried to put there a "ClassAttack.findItem(100);" (line 79 on AutoBaal.js) The parameter (100) it seems a 'range'... and I'm trying to tweak that, maybe I also have to change the leeching position because it seems too far! If I move manually the character it seems to start finding corpse, but the main issue here is that he remains melee!! He doens't go back to the leeching position!! I hoped he was doing a "hork and run" 💃 Anyone else tried?

[ARkaine2]

Thanks a lot guys (and especialy mayphilc), you really saved my life.

[NipperDipper]

"if (getDistance(me, corpse) > 30 || checkCollision(me, corpse, 0x1)) {" Why is it that I cannot find this line of code anywhere in Attack.js? There is no "me, corpse" but there are several other "me, xx" lines. Am I missing something?

[NipperDipper]

Delete my last comment. Forgot there was a separate "Barbarian.js" file in "Attacks." My bad!