Blizzhackers

I have a +3 holy shield cta on my paladin but he casts holy shield with the other weapons slot, is there a way to change this? I'd like him to cast his BC,BO,Holy shield then swap weapons.

Okay quick question i run windows 7. Bot works perfectly but when it get to character selection it won't click on character i got to manually click on him for him to start botting and fix's or idea's on how to fix this?

press home, see if there is an error, like "character not found" its most likely you typed your character name incorrectly in d2bot #
also make sure you are using d2botlead, follow, or channel, not blank

Thanks D3STROY3R worked perfectly learned something new today

I'll take that as a no? Lol.

I'm wondering what script(s) would be most recommended for leveling up a wiz...I turned on dodge, and that seems to work well, but the bot seems to guzzle pots like mad...I am 22, and turned on ancient tunnels, but I seem to have to buy too many pots...and also tried Radamant, with the same result. Then tried same on Andariel, with similar results.

Is my gear just horrible, or am I doing something wrong?

EDIT: Played around with settings a bit...Turning off dodge healed quite a bit...I seem to at least be coming closer to breaking even, on runs. the bot spends around 2k each run, over what it picks up. Not sure why it tends to drop gear, rather than sell it, after id'ing the gear with cain...I also added lower level pots to the pickit, so I don't have to buy them quite as much. I'm running around the ancient(?) tunnels, atm.

Nice bot!

id with cain is to save time, if you want to sell don't use id with cain (set it to false in char config)
if you id with cain then sell to npc then iding with cain was pointless to begin with

Yeah, I agree. But it drops whether I ID, or not. I can't figure out how to get it to sell instead of drop, so far...

EDIT: Actually, I need to check that...It may be selling (if cain is turned off) and I just don't realize it...I'll watch ot for several cycles...

it does not drop at npc

first of all: thanks you guys for developing such a great bot!

i've been testing it for a while and now i'm converting my classic team cs script (based on koltons initial release of teamd) to d2bs code.

so here are some problems i found or suggestions i would like to give:

Attack.js (Attack.kill):
encountering a monster that is immune to magicdamage specified in charconfig will lead to a "throw error" and thus ending the current script. i'd REALLY like to have this error be replaced by putting this:

or simply make it switchable with another argument. this was the only thing i had to change in the bot-core so far to get the cs team running well.

game statistics:
is there a way to have multilined outputs (mouseover) in d2bot#? i'd also appreciate adding of game duration and approx time to level up (based on: game duration + game create threshold + x * runs left to level up) to the built in exp-log. i've written a really neat (multilined) output for d2nt, so just tell me if u like to have the code.

color glitches in the D2Bot# log
sometimes the color of a line will swap over to the timestamp of the next line. i think this happens while scrolling through the log.

hammerdin attack routine:
hammerdin seems to attack even dumber than in old teamd since it doesn't change position according to monster.x monster.y after several attacks. will this get improved soon or do i have to write an own function?

FileTools.readText permission denied:
i'm using teamd-style teamcommands via textfile. it is working so far, but rarely produces a permission denied and therefor ending the script. i think this happens if write + read happens at exact the same time. any suggestions towards this problem?

Pickit.pickItems() & MiniShopBot producing hiccups/lag
sometimes (not every time) a pickit-call or vendor visit produces a short break of 1-3 seconds. is this caused by a big pickit file? (mine is 573 lines, 62227 chars atm)

Summoner.js
i'd like to disable the cleararea and just kill summoner. teleporting right in front of summoner also speeds it up since he is dead in a blink.



more to come...

Attack.js (Attack.kill):
all thrown errors can be wrapped in try/catch

try { somefunc() } catch (error) { };

game statistics: not currently
color glitches in the D2Bot# log: i noticed that when copy/pasting text from the log too. we need D3STROY3R's input on this
hammerdin attack routine: the routine is still being tweaked. it worked in every shape and form for me tho. you might want to look into writing your own as well
FileTools.readText permission denied: don't use txt files. from my experience it leads only to trouble. either use chat events or copydata events (those are silent)
Pickit.pickItems() & MiniShopBot producing hiccups/lag: haven't noticed that at all. try a smaller pickit and see if there's differences

thx for fast reply!

i'll check out the try/catch thing. but honestly it's making more sense to just return true if encountering an immune monster, since everything is doing fine.

i actually already fixed the color problems, ill upload it at some point
and regarding tooltip for Console... ill look into it

hello again

more suggestions:

D2Bot#:

Scheduler:
it would be cool to have a global checkbox to temporarily disable all set schedules.

Crashes:
D2Bot# will go mad and crash if it can't find the game.exe anymore (maybe if u moved the kolbot folder to another pc or renamed the diablo 2 folder). i think this happens if schedules are set and running.


D2BS:
my diablo 2 windows always get resized to 640*480 instead of staying at 800*600. i think this is intended, but i'd like to know a way of disabling this if there is one.


Kolbot:

Follow/Channel Entry Points:
there should be an option to disable rejoins into the same game.

MaxGameTime:
if a game ends due to maxgametime, there should be a message in the D2Bot# log.

Scheduler: all i can think of is select all profiles, right click and disable scheduler
Crashes: we'll need D3STROY3R's input here
D2BS: this is actually a part of d2bot's minimized d2 window start. if you compare it to other managers or bots, you'll see that they have to bring up d2 window briefly and then minimize it, which is annoying. I don't know if it's possible to change it
Follow/Channel Entry Points: they already have a check not to join the same game. the only time they'd do it is if they crash while the leader is still in game.
MaxGameTime: I'm using me.maxgametime which is entirely in the core and the core doesn't communicate with d2bot# directly.
I might change it to a different method, but it's more trouble than it's worth (me.maxgametime can be accessed across multiple thread while any script-side solution wouldn't be, at least not easily)