L2-Zur

I have the problem with windows finding.. I downloaded window handles, did all that You said in video, but still- "The game client window was still not found ,exiting."

I'v got win 7 x64.. trying bot on L2 end of ages server...  halp! :D

If you follow the video properly and do everything correctly it should work. Havent seen a case where it hasnt worked yet.

btw on win 7 x64 not work. I tried both methods (improved, compatibility ) - no one work.

 

but on game nothing happen.

 

ru off server

Sounds like your color maps are wrong, remake them according to the tutorial and it should work.

does the job done  :not bad:

only problem is with targeting listed mobs. Instead of the "/" char, it give me "7" when it has to send the target command. I have an Italian keyboard btw. Any help is appreciated :)

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.

Working, thanks for making and sharing it, but i am always having a problem after some 4/5min, game is closed and i get this error:

 

What you advise me to do, to prevent this problem?

 

Once again thanks for making this, its great to have a bot that works in any server(i believe it, since my server have huge bot protection and no1 could use l2walker on it for example), just having this stuck problem, wich is not a real "problem" because on your post you say that it can happen, can you just giveme the tricks to prevent this?? Thanks!

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.

When I try running the launcher they tell me

ERROR

The client is not running, or its window not found.Exit the bot?

 

Press YES to exit, or NO to set your own window name

Watch tutorial video 3. It explains what to do when the bot cant find your client in default settings.

it seems like the program has problem with targeting monsters, it just tries to use skills without a target, even when there are monsters around...

You color-maps are badly configured.

Rewatch the tutorial and reconfigure the color-maps properly, and it will all work.

Doesnt work in Core server of Lineage2.eu by Innova .

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.

Im having some troubles with the bot. Lets say it targets the mobs in the list but doesnt attack them. Just targets them over and over.

 

Hopefully you can give me some advice.

 

Thanks for the bot and keep up the good work :D

This is most probably due to badly configured color maps. Re-watch the tutorial video and reconfigure your colormaps.

Hello,

 

I can't get the moblist to work, it keeps typing "7target [mobname]" in my chat! is there anything I can do to make it a "/" instead?

 

And for those who can't target monsters with moblist, try to write the whole name, and not only a part of it as this is just a addon on the newer clients.

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:

When i start a "Launcher.exe" i write something and it says me "Object referenced outside a "with" statement.

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.

I only have one problem with this bot, cant use "buffs" section.

 

"KEYS ARE NOt CONFIGURE PROPERLY:SELF MACRO KEY IS MISSING:"

Just like it sais, you need to configure a self-target macro.

Please watch the tutorial video on buffs.

i get this error The version of this file not compatible with the version of windows  you're running... I have wind 7 x86... WHi dont worck ? It's only for xp or wht ?

The bot will only work on x64 systems.

Hello! Can you autocraft with it?

Nope, this bot is for mobbing only.

i get a window shouting 'problem lanuching heartbeat process'

what am i supposed to do???

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.

long post

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.

next generation of walkers, man its just simple pixel bot, it works but it will be never as effective as l2walker

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.

Have you had the time to check my PM?

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.

add cp pots spam too xD

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.

the entire process:

1) Start L2 session

2) Log in

3) Start L2 Zur

4) Configure L2 zur

5) Start L2 zur

6) Delay 2-5 sec

7) L2 closes

8) L2 zur continues to run

 

I believe is some kind of server protection

Yeah, that sounds like protection indeed. What server are you playing on?

I know the bot works with GameGuard, Kasha, Frost, WS protections.

when I switch to compatibility mode I siomply get my L2 session closed.

 

Can it be some kind of server protection?

Does it close right away or after running for a few minutes?

Do both the bot and L2 close, or just L2?

I've got the same problem, and when it is displayed, the L2 session closes. I've tried on both capturing modes and it ocures at the same time: When I start the bot :)

 

ERROR: An error occured getting the client window's device context handle.

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.

No doubt, with a 20sec response delay.

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.

A pixel bot?

Good luck trying to run that for 2h+ straight.

Actually, it runs for 8+ hours straight if you set it up correctly.

But thanks for your useless post anyway.

You could make a guide of good bot leveling zones.

 

I dont know if I´m making something wrong, but when there is no targeteable mob in range, y starts writting ingame 7target "mobname".

It is like if the bot cant send /, and sends 7. Maybe if you change the bot to send the "/" character instead of "Shitf+7" would help.

Read the FAQ, this is covered. The bot doesnt send Shift+7, it sends a direct keystroke to the L2 window handle, but keyboard settings do come info effect.

Ok, I see now :)

 

Thanks for answering. I'll test it soon. Keep up the good work!!

np!

also,

New version out:

Added an After-Combat ability, that is executed after killing a target. Usefull for spoil/sweep combo for example.

Few pages in the back I noticed that somebody asked if you will be able to create a buff option (most likely he/she refered at dualboxing).

 

From what I've read (did not test it yet, still busy with some projects) it works on only 1 client opened at a time.

 

Temporary sollution:

You could instal a Virtual Machine and on that to run the buffer, setting a macro with buffs and a delay for it, dunno... 18 mins.

On the main window (the dd/nuker) set the fighting shortcuts. Imo it should work pretty fine :)

 

Kind regards,

In the FAQ the question whether it works with multiple L2 clients is answered.

You can run as many clients and as many instances of the bot on a single PC as you like. Configure the buffs for your buffer, and as self-target macro, make a macro that targets your main instad of your buffer.

It can do what you want it to do on a single PC without a problem, with both windows running in the background even.

i dont know, can the reuse time and cooldown time be a problem? cause i put cooldown 1000 and reuse 3000 or something like that

No, the error you are receiving has nothing to do with any timers.

There is a new version out now that allows you to choose which pixel capture method to use. Use the "Pixel Capture" tab in the configuration to change the modes.

Please let me know if everything works using the "Compatibility Mode"

windows 7 64bit.

Try running the bot multiple times, and see if the error occurs at the same time on every try. I will make a switch for the picture capture techniques in a patch today.

But running Win 7 64bit SP1 here, everything works fine on a 4-hour run.

API ERROR: an error occured getting window device context.

please help, it killed 1 mob and then closed the game and gave me this error.

I've had a few reports of these errors after the latest update, which introduced a new DLL for pixel capture in order to enable full background mode functionality.

What OS and what Service Pack are you running? I will look more into this tommorow, and make a GUI switch to switch between old and new pixel capture methods.

The volume in your tutorial videos is low.

I know, I need a new mic. Just pull up your speakers ;)

Hi!

 

It is a fantastic job you are making! Any estimate on when will this be available on 32bit? Or have you got any other bot-like stuff, that could be used on 32 bit?

Thanks and much appreciated.

No estimates on 32bit support, from what I've been testing so far, it is far away. Currently, every dll the bot uses is native 64bit and sadly its not as simple as compiling it all in 32bit.

Also, there is an issue of time and priorities. I've spent over 100 development hours on this bot already. It is free, so I can not keep putting insane hours into it constantly. I work on it when I can, so sorry, but I cant give any solid estimates on 32bit support.

New version released today.

Background mode is now fully supported without any limitations. The only requirement is that the game client window is not minimized.

If someone can check if this works on Vista I would be thankful, since I tested on Win 7 only.