L2-Zur

If you follow the video properly and do everything correctly it should work. Havent seen a case where it hasnt worked yet. Sounds like your color maps are wrong, remake them according to the tutorial and it should work. The keyboard has to be set to english in the bot and in the game and it will work.

The launcher problems are now fixed. Sorry guys.

This will happen if the bot can get a target, but can not engage it, and this repeats 4 times. For example, if you have melee only attacks and you cant get to the target. Or if you have magic attacks and all targets nearby are not reachable. Simply, if you can get a target 4 times, but cant do any damage, stuck detection gets engaged for security reasons. Watch tutorial video 3. It explains what to do when the bot cant find your client in default settings.

You color-maps are badly configured. Rewatch the tutorial and reconfigure the color-maps properly, and it will all work.

I can safely say that it worked on Innova about half a year ago. Unless they did some major changes, it will still work. You are very probably not configuring it right. This is most probably due to badly configured color maps. Re-watch the tutorial video and reconfigure your colormaps. You have to have BOTH the game client and the bot set to the English keyboard. Then it will work.

For some reason I stopped getting email notifications for replies to this thread. Im sorry for not responding guys. I will go through most important stuff here: There was a problem server-side, which caused a problem client-side. This bot is free, but running the update servers and other stuff is not, so sometimes there is problems, since I have to use cheap, unreliable hosting services. The best way to avoid this in the future is donating. Just like it sais, you need to configure a self-target macro. Please watch the tutorial video on buffs. The bot will only work on x64 systems. Nope, this bot is for mobbing only.

Check if Heartbeat.exe is located in the Resources folder. If so, make sure none of the bot files are being blocked by your anti-virus or firewall.

Heal problems you are having are due to bad Color-Maps. So re-creating your color-maps in the bot is what you need to do. The bot takes pure colors from the windows screen buffer, so it doesnt matter what monitor calibration or color-enhancement you use. I would reccomend you re-watch the tutorial video and go over your config and color-maps again, that will fix the heal issues. It works for everyone else. About stuck: with any bot in any game, botting is always about location, location, location. Short for lvls 86-94, there is always an alternate location you can use that is pretty good for botting. Noone complained because of stuck issues yet, so you need to find a spot that works for you. The go to town is something I would like to implement myself, but its not easy, I might put some efford into it in the future, no promises tho. Range limits - impossible with this bot, because of the way this bot works, discussed before.

1) It is a pixel bot, but it is far from simple. 2) This is not meant to be as effective as walker. However, this is infinatelly more secure.

Yeah, im looking into it. I havent had much time the past few days, but I'll get to it as soon as I can.

Pot spamming is not going to happen. Implementing it to work with the current bot mechanics would require quite a bit of work. It would be ineffective, and foremost, you dont need it with a bot like this. Not to mention noone has requested it yet except you.

Yeah, that sounds like protection indeed. What server are you playing on? I know the bot works with GameGuard, Kasha, Frost, WS protections.

Does it close right away or after running for a few minutes? Do both the bot and L2 close, or just L2?

Your L2 client closes when you start the bot? Also, you cant get the device context error using the compatibility mode, since the compatibility mode doesnt use device context. Please let me know what you get when switched to compatibility mode.

And you got this value by running the bot and measuring with precise timer DLLs injected into my exe I take it? Oh right, no you didnt. Thanks for a free bump! Anyway, to get some actual data posted in here: On my PC the pixel detection for checking if a mob is targeted is ~1.28ms with Improved Mode and ~23ms with Compatibility mode.