[Window Positions]Quote:
Your problem seems to be that the bot doesnt even reckognize that its engaged the mob properly. I would guess the problem is with your SkillWatch pixel locations. Post your config from the settings.ini as well please.
Read the Important notes and FAQ sections.Quote:
Smth wrong with bot. It says arget mob name not /target what i did wrong ?
Both your attack1 and attack2 cast-time and cooldwons are 100ms. This will not work...Quote:
settings.ini here
thank you l2-zur!!!
Fixed cooldown and cast time, even with 1 only skill when mobs are killed the bot doesnt change target...Quote:
Read the Important notes and FAQ sections.
Both your attack1 and attack2 cast-time and cooldwons are 100ms. This will not work...
It seems you have a [space] in one of your attack keys as the attack key. I still think your problem is with the SkillWatch pixels during the ColorMap creation.Quote:
Fixed cooldown and cast time, even with 1 only skill when mobs are killed the bot doesnt change target...
10:51:52 - Engaging mob - {F2} sent
10:51:53 - Engaging mob - {} sent
10:51:54 - Engaging mob - {F2} sent
10:51:55 - Engaging mob - {} sent
10:51:56 - Engaging mob - {F2} sent
and why {} skill ?
You can configure healing either for the summon or for yourself using the heal menu. However heals for both yourself and your summon are not implemented, so you can either have a heal set-up for yourself, or your summon, not both.Quote:
Ok that problem and my keyboard is EN.
And how to do that heal my summon when hes hp drops to 70% ?
[Only registered and activated users can see links. Click Here To Register...]
1) I personally dont experience this problem. I can be botting with the client in the background and play a different game at the same time and it works fine for me personally. Problems like this are hard to trouble-shoot, because of course, everyone computer is setup differently.Quote:
Yeah I have trouble with getting stuck alot too. This bot does help in auto if u have alot of macro attacks, it's pretty sweet.
However I have noticed some odd things.
1) When I run multiple clients all with decrease background performace off as per the tutorial, If I pause one of the clients or go to another application and start typing sometimes the shift key gets stuck. Its very odd. like I'll have to go into each client and hold shift then press ctrl to unlock the char. Sometimes its the left shift key, sometimes the right. This problem makes doing anything else on comp pretty useless.
After reading some recent posts I wonder if this is what people are experiencing. Its almost as if the char has enabled stationary attack, i don't know how to explain, like an archer/mage would do if he didn't want to run move when casting a spell.
2) Not in tutorial, but somewhere in previous post it was said that you could have multiple windows as long as they weren't minimized. Does that mean you can stack a bunch of windows on top of each other?
When I try this it keeps thinking the bot needs healing because it can't see hp bar or something. Also some of the skills don't work because it acts like it's not done refreshing,because it can't see the skill I guess?
So for clarification can the window be on top or do all skills/hp bars need to be visible at all times?
Again this is a neat tool. Requires alot of babysitting, but i'd rather be reading a mag or something that pressing the same 5 buttons all day.
Thanks again!
None of that really should matter.Quote:
Hmm. well does it matter what detail lvl I have the game set to? i have it set to lowest resolution 16-bit, gpu animation on, lower detail on. other than that, everything is generic.
Try with the "Compatible mode" Pixel Capture. Background mode will not work, but it doesnt use Device Contexts, so the bot will work.Quote:
after engaging, it kills mob (or just wright away) and :
API error
"An error occurred getting the client window's Device Context handle"
client is closed.
PS: same message on: XP proff x64 and Win 7 Enterprise x64